100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 980
A team wants Azure Front Door WAF attached to only one sensitive hostname. During acceptance testing, the sensitive hostname has no WAF protection. Which underlying configuration problem best explains the symptom?
- Its firewall or child policy is not associated with the parent policy
- Its domain was not included in security policy association
- The central security admin configuration is not deployed or scoped
- The regional firewall has not been linked to updated policy
Explanation
Correct Answer
B:Its domain was not included in security policy association explains the observed failure: the sensitive hostname has no WAF protection. Correct the design by using scope the WAF security policy to designated Front Door domains, implemented through associate the policy with the intended domain/path patterns.
Incorrect Answers
A:Its firewall or child policy is not associated with the parent policy. This concerns shared firewall policy inheritance and administration. Here, its domain was not included in security policy association.
C:The central security admin configuration is not deployed or scoped. This concerns enforcing consistent baseline security controls across many vnets. Here, its domain was not included in security policy association.
D:The regional firewall has not been linked to updated policy. This concerns updating firewall rule collections across many regional deployments. Here, its domain was not included in security policy association.
Question 981
A regional WAF blocks legitimate POST requests because request body parsing is too strict. Which Azure networking design most directly satisfies this requirement?
- Review WAF request body inspection and size settings within supported limits
- Associate an Azure Application Gateway WAF policy with a supported gateway SKU
- Use an appropriate Azure service tag in NSG rules where supported
- Create the required AzureFirewallSubnet with supported dimensions
Explanation
Correct Answer
A:Review WAF request body inspection and size settings within supported limits addresses the topology, access or delivery requirement in the scenario. Apply it by configure relevant WAF policy request body rules and precise exclusions; confirm by test representative POST payloads and malicious input.
Incorrect Answers
B:Associate an Azure Application Gateway WAF policy with a supported gateway SKU. This concerns protection against OWASP web exploits. Instead, review WAF request body inspection and size settings within supported limits.
C:Use an appropriate Azure service tag in NSG rules where supported. This concerns allowing outbound calls to an Azure PaaS service without maintaining IP address lists. Instead, review WAF request body inspection and size settings within supported limits.
D:Create the required AzureFirewallSubnet with supported dimensions. This concerns Azure Firewall deployment fails because the hub lacks its reserved platform subnet. Instead, review WAF request body inspection and size settings within supported limits.
Question 982
A regional WAF blocks legitimate POST requests because request body parsing is too strict. The architecture uses this design: Review WAF request body inspection and size settings within supported limits. Which configuration should the engineer apply to implement it?
- Set WAF policy mode to Detection and enable diagnostics
- Configure relevant WAF policy request body rules and precise exclusions
- Associate each VM NIC with an ASG and reference ASGs in NSG rules
- Assign NIC IP configurations to the ASG and create NSG rules targeting that ASG
Explanation
Correct Answer
B:Configure relevant WAF policy request body rules and precise exclusions is the operational configuration for review waf request body inspection and size settings within supported limits. The acceptance test is to test representative POST payloads and malicious input.
Incorrect Answers
A:Set WAF policy mode to Detection and enable diagnostics is a concrete step for use waf detection mode during tuning. Here the selected design is review waf request body inspection and size settings within supported limits, which instead requires configure relevant waf policy request body rules and precise exclusions.
C:Associate each VM NIC with an ASG and reference ASGs in NSG rules is a concrete step for use azure application security groups for logical vm grouping. Here the selected design is review waf request body inspection and size settings within supported limits, which instead requires configure relevant waf policy request body rules and precise exclusions.
D:Assign NIC IP configurations to the ASG and create NSG rules targeting that ASG is a concrete step for reference an application security group in network security rules. Here the selected design is review waf request body inspection and size settings within supported limits, which instead requires configure relevant waf policy request body rules and precise exclusions.
Question 983
A regional WAF blocks legitimate POST requests because request body parsing is too strict. After the team applies this change—configure relevant WAF policy request body rules and precise exclusions—which validation best proves the intended result?
- Test representative POST payloads and malicious input
- Test a trusted client and inspect successful decrypted threat evaluation
- Test desired east-west flows and blocked unauthorized connections
- Send a permitted request and controlled malicious pattern; inspect WAF logs
Explanation
Correct Answer
A:Test representative POST payloads and malicious input directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether request body limits or exclusions do not match the workload.
Incorrect Answers
B:Test a trusted client and inspect successful decrypted threat evaluation. This concerns inspection of application-layer content inside TLS at the central hub. Instead, test representative POST payloads and malicious input.
C:Test desired east-west flows and blocked unauthorized connections. This concerns occur inside an azure VNet. Instead, test representative POST payloads and malicious input.
D:Send a permitted request and controlled malicious pattern; inspect WAF logs. This concerns protection against owasp web exploits. Instead, test representative POST payloads and malicious input.
Question 984
A regional WAF blocks legitimate POST requests because request body parsing is too strict. During acceptance testing, large expected payloads are denied. Which underlying configuration problem best explains the symptom?
- Request body limits or exclusions do not match the workload
- Broad default or custom outbound allowance remains effective
- Rule priority or type evaluation order permits it first
- A higher-priority deny rule matches first
Explanation
Correct Answer
A:Request body limits or exclusions do not match the workload explains the observed failure: large expected payloads are denied. Correct the design by using review WAF request body inspection and size settings within supported limits, implemented through configure relevant WAF policy request body rules and precise exclusions.
Incorrect Answers
B:Broad default or custom outbound allowance remains effective. This concerns not connect to arbitrary destinations. Here, request body limits or exclusions do not match the workload.
C:Rule priority or type evaluation order permits it first. This concerns denying one destination even though a broader allow exists. Here, request body limits or exclusions do not match the workload.
D:A higher-priority deny rule matches first. This concerns a network administrator adds an allow rule but packets are still blocked by a subnet NSG. Here, request body limits or exclusions do not match the workload.
Question 985
An operator wants to distinguish a WAF block from an Application Gateway backend 502. Which TWO listed choices identify the suitable Azure design and the concrete configuration required to implement it? (Choose TWO.)
- Enable diagnostic logs to Log Analytics and query matching rule activity
- Configure firewall DNS servers and optionally enable DNS proxy for clients
- Use WAF diagnostics alongside gateway access and backend health logs
- Enable WAF and access logs then correlate request IDs and response codes
- Associate an Azure Application Gateway WAF policy with a supported gateway SKU
Explanation
Correct Answers
C:Use WAF diagnostics alongside gateway access and backend health logs addresses the topology, access or delivery requirement in the scenario. Apply it by enable WAF and access logs then correlate request IDs and response codes; confirm by match a blocked request to WAF action versus an unhealthy backend response.
D:Enable WAF and access logs then correlate request IDs and response codes is the operational configuration for use waf diagnostics alongside gateway access and backend health logs. The acceptance test is to match a blocked request to WAF action versus an unhealthy backend response.
Incorrect Answers
A:Enable diagnostic logs to Log Analytics and query matching rule activity. This concerns seeing whether Azure Firewall dropped a specific connection. Instead, use WAF diagnostics alongside gateway access and backend health logs.
B:Configure firewall DNS servers and optionally enable DNS proxy for clients is a concrete step for use supported azure firewall dns settings and dns proxy where required. Here the selected design is use waf diagnostics alongside gateway access and backend health logs, which instead requires enable waf and access logs then correlate request ids and response codes.
E:Associate an Azure Application Gateway WAF policy with a supported gateway SKU. This concerns protection against OWASP web exploits. Instead, use WAF diagnostics alongside gateway access and backend health logs.
Question 986
An operator wants to distinguish a WAF block from an Application Gateway backend 502. The architecture uses this design: Use WAF diagnostics alongside gateway access and backend health logs. Which configuration should the engineer apply to implement it?
- Enable WAF and access logs then correlate request IDs and response codes
- Set WAF policy mode to Detection and enable diagnostics
- Configure firewall DNS servers and optionally enable DNS proxy for clients
- Correlate source and destination addresses, ports, direction and recorded flow status with the test traffic
Explanation
Correct Answer
A:Enable WAF and access logs then correlate request IDs and response codes is the operational configuration for use waf diagnostics alongside gateway access and backend health logs. The acceptance test is to match a blocked request to WAF action versus an unhealthy backend response.
Incorrect Answers
B:Set WAF policy mode to Detection and enable diagnostics is a concrete step for use waf detection mode during tuning. Here the selected design is use waf diagnostics alongside gateway access and backend health logs, which instead requires enable waf and access logs then correlate request ids and response codes.
C:Configure firewall DNS servers and optionally enable DNS proxy for clients is a concrete step for use supported azure firewall dns settings and dns proxy where required. Here the selected design is use waf diagnostics alongside gateway access and backend health logs, which instead requires enable waf and access logs then correlate request ids and response codes.
D:Correlate source and destination addresses, ports, direction and recorded flow status with the test traffic is a concrete step for interpret virtual network flow logs using the recorded network tuple and decision. Here the selected design is use waf diagnostics alongside gateway access and backend health logs, which instead requires enable waf and access logs then correlate request ids and response codes.
Question 987
An operator wants to distinguish a WAF block from an Application Gateway backend 502. After the team applies this change—enable WAF and access logs then correlate request IDs and response codes—which validation best proves the intended result?
- Match a blocked request to WAF action versus an unhealthy backend response
- Confirm malicious test requests are logged but not blocked
- Test allowed website access and a blocked unlisted FQDN
- Search logs for the source, destination and rule action
Explanation
Correct Answer
A:Match a blocked request to WAF action versus an unhealthy backend response directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether wAF events were not correlated with backend health data.
Incorrect Answers
B:Confirm malicious test requests are logged but not blocked. This concerns log would-be blocks without disrupting customer traffic. Here, match a blocked request to WAF action versus an unhealthy backend response.
C:Test allowed website access and a blocked unlisted FQDN. This concerns application-aware fqdn filtering for outbound http and HTTPS. Here, match a blocked request to WAF action versus an unhealthy backend response.
D:Search logs for the source, destination and rule action. This concerns seeing whether azure firewall dropped a specific connection. Here, match a blocked request to WAF action versus an unhealthy backend response.
Question 988
An operator wants to distinguish a WAF block from an Application Gateway backend 502. During acceptance testing, engineers blame WAF when the gateway's backend probe is unhealthy. Which underlying configuration problem best explains the symptom?
- WAF events were not correlated with backend health data
- Its firewall or child policy is not associated with the parent policy
- Static IP allowlists were used instead of service tags
- Only HTTP-oriented application rules were configured
Explanation
Correct Answer
A:WAF events were not correlated with backend health data explains the observed failure: engineers blame WAF when the gateway's backend probe is unhealthy. Correct the design by using use WAF diagnostics alongside gateway access and backend health logs, implemented through enable WAF and access logs then correlate request IDs and response codes.
Incorrect Answers
B:Its firewall or child policy is not associated with the parent policy. This concerns shared firewall policy inheritance and administration. The relevant SQL or system operation is WAF events were not correlated with backend health data.
C:Static IP allowlists were used instead of service tags. This concerns allowing outbound calls to an azure paas service without maintaining ip address lists. The relevant SQL or system operation is WAF events were not correlated with backend health data.
D:Only HTTP-oriented application rules were configured. This concerns filtering non-http tcp traffic by ip, protocol and destination port. The relevant SQL or system operation is WAF events were not correlated with backend health data.
Question 989
An application gateway uses WAF policy but test requests never trigger expected custom rules. Which Azure networking design most directly satisfies this requirement?
- Associate an Azure Application Gateway WAF policy with a supported gateway SKU
- Set rule collection group and collection priorities in the correct evaluation order
- Understand that lower NSG priority numbers are evaluated first
- Check policy association and custom rule priority conditions
Explanation
Correct Answer
D:Check policy association and custom rule priority conditions addresses the topology, access or delivery requirement in the scenario. Apply it by attach policy at the appropriate scope and set correct match conditions; confirm by inspect WAF log entries and confirm expected custom rule ID.
Incorrect Answers
A:Associate an Azure Application Gateway WAF policy with a supported gateway SKU. This concerns protection against OWASP web exploits. Instead, check policy association and custom rule priority conditions.
B:Set rule collection group and collection priorities in the correct evaluation order. This concerns denying one destination even though a broader allow exists. Instead, check policy association and custom rule priority conditions.
C:Understand that lower NSG priority numbers are evaluated first. This is relevant when a new NSG rule has a larger numerical priority and unexpectedly loses to another rule. Instead, check policy association and custom rule priority conditions.
Question 990
An application gateway uses WAF policy but test requests never trigger expected custom rules. The architecture uses this design: Check policy association and custom rule priority conditions. Which configuration should the engineer apply to implement it?
- Attach policy at the appropriate scope and set correct match conditions
- Configure inspection CA/trust and premium TLS inspection policy where supported
- Select appropriate threat intelligence alert or alert-and-deny mode
- Associate the policy with the intended domain/path patterns
Explanation
Correct Answer
A:Attach policy at the appropriate scope and set correct match conditions is the operational configuration for check policy association and custom rule priority conditions. The acceptance test is to inspect WAF log entries and confirm expected custom rule ID.
Incorrect Answers
B:Configure inspection CA/trust and premium TLS inspection policy where supported is a concrete step for use azure firewall premium tls inspection with appropriate certificates. Here the selected design is check policy association and custom rule priority conditions, which instead requires attach policy at the appropriate scope and set correct match conditions.
C:Select appropriate threat intelligence alert or alert-and-deny mode is a concrete step for configure azure firewall threat intelligence filtering settings. Here the selected design is check policy association and custom rule priority conditions, which instead requires attach policy at the appropriate scope and set correct match conditions.
D:Associate the policy with the intended domain/path patterns is a concrete step for scope the waf security policy to designated front door domains. Here the selected design is check policy association and custom rule priority conditions, which instead requires attach policy at the appropriate scope and set correct match conditions.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests