100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
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.
Question 991
An application gateway uses WAF policy but test requests never trigger expected custom rules. After the team applies this change—attach policy at the appropriate scope and set correct match conditions—which validation best proves the intended result?
- Inspect effective security rules and verify enforced org-wide policy
- Test a trusted client and inspect successful decrypted threat evaluation
- Send a permitted request and controlled malicious pattern; inspect WAF logs
- Inspect WAF log entries and confirm expected custom rule ID
Explanation
Correct Answer
D:Inspect WAF log entries and confirm expected custom rule ID directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the WAF policy attachment or rule scope is incorrect.
Incorrect Answers
A:Inspect effective security rules and verify enforced org-wide policy. This concerns enforcing consistent baseline security controls across many vnets. Instead, inspect WAF log entries and confirm expected custom rule ID.
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, inspect WAF log entries and confirm expected custom rule ID.
C:Send a permitted request and controlled malicious pattern; inspect WAF logs. This concerns protection against owasp web exploits. Instead, inspect WAF log entries and confirm expected custom rule ID.
Question 992
An application gateway uses WAF policy but test requests never trigger expected custom rules. During acceptance testing, traffic is evaluated by a different policy than intended. Which underlying configuration problem best explains the symptom?
- An overly broad higher-priority NSG allow rule takes precedence
- Rule priority or type evaluation order permits it first
- An overly broad wildcard or allow-all application rule exists
- The WAF policy attachment or rule scope is incorrect
Explanation
Correct Answer
D:The WAF policy attachment or rule scope is incorrect explains the observed failure: traffic is evaluated by a different policy than intended. Correct the design by using check policy association and custom rule priority conditions, implemented through attach policy at the appropriate scope and set correct match conditions.
Incorrect Answers
A:An overly broad higher-priority NSG allow rule takes precedence. This concerns denying inbound ssh from the internet while permitting approved private management. Here, the WAF policy attachment or rule scope is incorrect.
B:Rule priority or type evaluation order permits it first. This concerns denying one destination even though a broader allow exists. Here, the WAF policy attachment or rule scope is incorrect.
C:An overly broad wildcard or allow-all application rule exists. This concerns allowing *.example.org without opening all internet domains. Here, the WAF policy attachment or rule scope is incorrect.
Question 993
A global security team needs WAF logs centralized for incident review. Which Azure networking design most directly satisfies this requirement?
- Use Azure Firewall Manager policies with parent-child structure
- Associate an Azure Application Gateway WAF policy with a supported gateway SKU
- Enable diagnostic export for Azure Front Door WAF
- Use Azure Firewall network rules rather than HTTP application rules
Explanation
Correct Answer
C:Enable diagnostic export for Azure Front Door WAF addresses the topology, access or delivery requirement in the scenario. Apply it by route Front Door WAF log categories to Log Analytics or storage; confirm by query blocked request events by endpoint and rule ID.
Incorrect Answers
A:Use Azure Firewall Manager policies with parent-child structure. This concerns shared firewall policy inheritance and administration. Instead, enable diagnostic export for Azure Front Door WAF.
B:Associate an Azure Application Gateway WAF policy with a supported gateway SKU. This concerns protection against OWASP web exploits. Instead, enable diagnostic export for Azure Front Door WAF.
D:Use Azure Firewall network rules rather than HTTP application rules. This concerns filtering non-HTTP TCP traffic by IP, protocol and destination port. Instead, enable diagnostic export for Azure Front Door WAF.
Question 994
A global security team needs WAF logs centralized for incident review. The architecture uses this design: Enable diagnostic export for Azure Front Door WAF. Which configuration should the engineer apply to implement it?
- Route Front Door WAF log categories to Log Analytics or storage
- Configure diagnostic categories and resource-specific tables as applicable
- Create rate-limit match conditions and thresholds for the login route
- Inspect effective security rules from NIC and subnet and adjust both scopes as needed
Explanation
Correct Answer
A:Route Front Door WAF log categories to Log Analytics or storage is the operational configuration for enable diagnostic export for azure front door waf. The acceptance test is to query blocked request events by endpoint and rule ID.
Incorrect Answers
B:Configure diagnostic categories and resource-specific tables as applicable is a concrete step for send azure firewall diagnostics to an approved log analytics workspace. Here the selected design is enable diagnostic export for azure front door waf, which instead requires route front door waf log categories to log analytics or storage.
C:Create rate-limit match conditions and thresholds for the login route is a concrete step for use waf rate limiting custom rules where available. Here the selected design is enable diagnostic export for azure front door waf, which instead requires route front door waf log categories to log analytics or storage.
D:Inspect effective security rules from NIC and subnet and adjust both scopes as needed is a concrete step for evaluate both nsg associations rather than assuming one overrides the other. Here the selected design is enable diagnostic export for azure front door waf, which instead requires route front door waf log categories to log analytics or storage.
Question 995
A global security team needs WAF logs centralized for incident review. After the team applies this change—route Front Door WAF log categories to Log Analytics or storage—which validation best proves the intended result?
- Test desired east-west flows and blocked unauthorized connections
- Query blocked request events by endpoint and rule ID
- Compare effective policy IDs and sample rule decisions across regions
- Send a permitted request and controlled malicious pattern; inspect WAF logs
Explanation
Correct Answer
B:Query blocked request events by endpoint and rule ID directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether wAF diagnostic settings were never configured.
Incorrect Answers
A:Test desired east-west flows and blocked unauthorized connections. This concerns occur inside an azure VNet. Instead, query blocked request events by endpoint and rule ID.
C:Compare effective policy IDs and sample rule decisions across regions. This concerns updating firewall rule collections across many regional deployments. Instead, query blocked request events by endpoint and rule ID.
D:Send a permitted request and controlled malicious pattern; inspect WAF logs. This concerns protection against owasp web exploits. Instead, query blocked request events by endpoint and rule ID.
Question 996
A global security team needs WAF logs centralized for incident review. During acceptance testing, an active WAF policy produces no retained investigation events. Which underlying configuration problem best explains the symptom?
- Static IP allowlists were used instead of service tags
- Their NICs were not associated with the correct ASG
- Flow direction or traffic disposition fields were interpreted incorrectly
- WAF diagnostic settings were never configured
Explanation
Correct Answer
D:WAF diagnostic settings were never configured explains the observed failure: an active WAF policy produces no retained investigation events. Correct the design by using enable diagnostic export for Azure Front Door WAF, implemented through route Front Door WAF log categories to Log Analytics or storage.
Incorrect Answers
A: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 diagnostic settings were never configured.
B:Their NICs were not associated with the correct ASG. This concerns being referenced by application role rather than static ip lists in NSG rules. The relevant SQL or system operation is WAF diagnostic settings were never configured.
C:Flow direction or traffic disposition fields were interpreted incorrectly. This concerns identifying which connection was rejected. The relevant SQL or system operation is WAF diagnostic settings were never configured.
Question 997
A public application relies on Front Door WAF and must reject suspicious request paths before origin processing. Which Azure networking design most directly satisfies this requirement?
- Create the required AzureFirewallSubnet with supported dimensions
- Use WAF rate limiting custom rules where available
- Set rule collection group and collection priorities in the correct evaluation order
- Create a Front Door custom WAF match rule on URL path
Explanation
Correct Answer
D:Create a Front Door custom WAF match rule on URL path addresses the topology, access or delivery requirement in the scenario. Apply it by configure supported request URI conditions with Block action in prevention mode; confirm by send a controlled matching path and validate edge denial.
Incorrect Answers
A:Create the required AzureFirewallSubnet with supported dimensions. This concerns Azure Firewall deployment fails because the hub lacks its reserved platform subnet. Instead, create a Front Door custom WAF match rule on URL path.
B:Use WAF rate limiting custom rules where available. This concerns an emergency rule to reduce high request rate from a single source. Instead, create a Front Door custom WAF match rule on URL path.
C:Set rule collection group and collection priorities in the correct evaluation order. This concerns denying one destination even though a broader allow exists. Instead, create a Front Door custom WAF match rule on URL path.
Question 998
A public application relies on Front Door WAF and must reject suspicious request paths before origin processing. The architecture uses this design: Create a Front Door custom WAF match rule on URL path. Which configuration should the engineer apply to implement it?
- Set WAF policy mode to Detection and enable diagnostics
- Associate each VM NIC with an ASG and reference ASGs in NSG rules
- Create AzureFirewallSubnet, deploy Firewall and configure a default UDR next hop
- Configure supported request URI conditions with Block action in prevention mode
Explanation
Correct Answer
D:Configure supported request URI conditions with Block action in prevention mode is the operational configuration for create a front door custom waf match rule on url path. The acceptance test is to send a controlled matching path and validate edge denial.
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 create a front door custom waf match rule on url path, which instead requires configure supported request uri conditions with block action in prevention mode.
B: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 create a front door custom waf match rule on url path, which instead requires configure supported request uri conditions with block action in prevention mode.
C:Create AzureFirewallSubnet, deploy Firewall and configure a default UDR next hop is a concrete step for deploy azure firewall in the hub and route spokes through it. Here the selected design is create a front door custom waf match rule on url path, which instead requires configure supported request uri conditions with block action in prevention mode.
Question 999
A public application relies on Front Door WAF and must reject suspicious request paths before origin processing. After the team applies this change—configure supported request URI conditions with Block action in prevention mode—which validation best proves the intended result?
- Read the matching rule name and Allow or Deny verdict
- Generate a controlled burst and confirm rate-limit decisions
- Run IP flow verify and check the first matching security rule
- Send a controlled matching path and validate edge denial
Explanation
Correct Answer
D:Send a controlled matching path and validate edge denial directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the custom path-match rule is missing or not enabled.
Incorrect Answers
A:Read the matching rule name and Allow or Deny verdict. This concerns determine which NSG rule blocks a specific vm's outgoing flow. Instead, send a controlled matching path and validate edge denial.
B:Generate a controlled burst and confirm rate-limit decisions. This concerns an emergency rule to reduce high request rate from a single source. Instead, send a controlled matching path and validate edge denial.
C:Run IP flow verify and check the first matching security rule. This is relevant when a new NSG rule has a larger numerical priority and unexpectedly loses to another rule. Instead, send a controlled matching path and validate edge denial.
Question 1000
A public application relies on Front Door WAF and must reject suspicious request paths before origin processing. During acceptance testing, malformed paths still reach the origin. Which underlying configuration problem best explains the symptom?
- An overly broad higher-priority NSG allow rule takes precedence
- A network security rule or private endpoint network policy blocks the flow
- Return traffic takes a different route from the inspection path
- The custom path-match rule is missing or not enabled
Explanation
Correct Answer
D:The custom path-match rule is missing or not enabled explains the observed failure: malformed paths still reach the origin. Correct the design by using create a Front Door custom WAF match rule on URL path, implemented through configure supported request URI conditions with Block action in prevention mode.
Incorrect Answers
A:An overly broad higher-priority NSG allow rule takes precedence. This concerns denying inbound ssh from the internet while permitting approved private management. Here, the custom path-match rule is missing or not enabled.
B:A network security rule or private endpoint network policy blocks the flow. This is relevant when a team investigates why a vm cannot reach an azure storage private endpoint over port 443. Here, the custom path-match rule is missing or not enabled.
C:Return traffic takes a different route from the inspection path. This concerns a hub-and-spoke architecture demands symmetric packet routing through azure firewall. Here, the custom path-match rule is missing or not enabled.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests