100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 960
A mature WAF policy should actively stop known malicious requests. During acceptance testing, malicious patterns generate logs but remain allowed. Which underlying configuration problem best explains the symptom?
- Threat intelligence mode remains Alert instead of Alert and deny
- WAF policy is still in Detection mode
- A network security rule or private endpoint network policy blocks the flow
- The regional firewall has not been linked to updated policy
Explanation
Correct Answer
B:WAF policy is still in Detection mode explains the observed failure: malicious patterns generate logs but remain allowed. Correct the design by using use WAF Prevention mode with reviewed managed rules, implemented through set policy mode to Prevention and tune required exclusions.
Incorrect Answers
A:Threat intelligence mode remains Alert instead of Alert and deny. This concerns mitigate high-risk traffic based on microsoft's current intelligence feeds. The relevant SQL or system operation is WAF policy is still in Detection mode.
C: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. The relevant SQL or system operation is WAF policy is still in Detection mode.
D:The regional firewall has not been linked to updated policy. This concerns updating firewall rule collections across many regional deployments. The relevant SQL or system operation is WAF policy is still in Detection mode.
Question 961
A business application requires an exception for a particular legitimate JSON field flagged by WAF. Which TWO listed choices identify the suitable Azure design and the concrete configuration required to implement it? (Choose TWO.)
- Configure a narrowly scoped WAF exclusion for the matching field
- Review WAF logs and tune only the specific triggered rule/exclusion
- Set exclusion scope and match variables on relevant managed rules
- Enable diagnostic logs to Log Analytics and query matching rule activity
- Assign NIC IP configurations to the ASG and create NSG rules targeting that ASG
Explanation
Correct Answers
A:Configure a narrowly scoped WAF exclusion for the matching field addresses the topology, access or delivery requirement in the scenario. Apply it by set exclusion scope and match variables on relevant managed rules; confirm by test benign JSON accepted and unrelated malicious probes still blocked.
C:Set exclusion scope and match variables on relevant managed rules is the operational configuration for configure a narrowly scoped waf exclusion for the matching field. The acceptance test is to test benign JSON accepted and unrelated malicious probes still blocked.
Incorrect Answers
B:Review WAF logs and tune only the specific triggered rule/exclusion. This concerns a WAF managed-rule update causes false positives on trusted API inputs. Instead, configure a narrowly scoped WAF exclusion for the matching field.
D:Enable diagnostic logs to Log Analytics and query matching rule activity. This concerns seeing whether Azure Firewall dropped a specific connection. Instead, configure a narrowly scoped WAF exclusion for the matching field.
E: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 configure a narrowly scoped waf exclusion for the matching field, which instead requires set exclusion scope and match variables on relevant managed rules.
Question 962
A business application requires an exception for a particular legitimate JSON field flagged by WAF. The architecture uses this design: Configure a narrowly scoped WAF exclusion for the matching field. Which configuration should the engineer apply to implement it?
- Set exclusion scope and match variables on relevant managed rules
- Deploy Application Gateway WAF_v2 and attach a managed-rule WAF policy
- Assign NIC IP configurations to the ASG and create NSG rules targeting that ASG
- Associate each VM NIC with an ASG and reference ASGs in NSG rules
Explanation
Correct Answer
A:Set exclusion scope and match variables on relevant managed rules is the operational configuration for configure a narrowly scoped waf exclusion for the matching field. The acceptance test is to test benign JSON accepted and unrelated malicious probes still blocked.
Incorrect Answers
B:Deploy Application Gateway WAF_v2 and attach a managed-rule WAF policy is a concrete step for associate an azure application gateway waf policy with a supported gateway sku. Here the selected design is configure a narrowly scoped waf exclusion for the matching field, which instead requires set exclusion scope and match variables on relevant managed rules.
C: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 configure a narrowly scoped waf exclusion for the matching field, which instead requires set exclusion scope and match variables on relevant managed rules.
D: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 configure a narrowly scoped waf exclusion for the matching field, which instead requires set exclusion scope and match variables on relevant managed rules.
Question 963
A business application requires an exception for a particular legitimate JSON field flagged by WAF. After the team applies this change—set exclusion scope and match variables on relevant managed rules—which validation best proves the intended result?
- Query blocked request events by endpoint and rule ID
- Run a prohibited traffic test and inspect matched rule
- Test benign JSON accepted and unrelated malicious probes still blocked
- Test one approved update target and one disallowed destination
Explanation
Correct Answer
C:Test benign JSON accepted and unrelated malicious probes still blocked directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether an exclusion was too broad rather than targeted.
Incorrect Answers
A:Query blocked request events by endpoint and rule ID. This concerns waf logs centralized for incident review. Instead, test benign JSON accepted and unrelated malicious probes still blocked.
B:Run a prohibited traffic test and inspect matched rule. This concerns denying one destination even though a broader allow exists. Instead, test benign JSON accepted and unrelated malicious probes still blocked.
D:Test one approved update target and one disallowed destination. This concerns not connect to arbitrary destinations. Instead, test benign JSON accepted and unrelated malicious probes still blocked.
Question 964
A business application requires an exception for a particular legitimate JSON field flagged by WAF. During acceptance testing, turning off an entire managed-rule set causes new attack gaps. Which underlying configuration problem best explains the symptom?
- Broad default or custom outbound allowance remains effective
- An exclusion was too broad rather than targeted
- An overly broad wildcard or allow-all application rule exists
- An overly broad higher-priority NSG allow rule takes precedence
Explanation
Correct Answer
B:An exclusion was too broad rather than targeted explains the observed failure: turning off an entire managed-rule set causes new attack gaps. Correct the design by using configure a narrowly scoped WAF exclusion for the matching field, implemented through set exclusion scope and match variables on relevant managed rules.
Incorrect Answers
A:Broad default or custom outbound allowance remains effective. This concerns not connect to arbitrary destinations. Here, an exclusion was too broad rather than targeted.
C:An overly broad wildcard or allow-all application rule exists. This concerns allowing *.example.org without opening all internet domains. Here, an exclusion was too broad rather than targeted.
D:An overly broad higher-priority NSG allow rule takes precedence. This concerns denying inbound ssh from the internet while permitting approved private management. Here, an exclusion was too broad rather than targeted.
Question 965
A global API is experiencing repeated unwanted requests from one country. Which Azure networking design most directly satisfies this requirement?
- Set rule collection group and collection priorities in the correct evaluation order
- Apply an appropriate Front Door WAF geo-match custom rule
- Use WAF rate limiting custom rules where available
- Use Azure Firewall Premium TLS inspection with appropriate certificates
Explanation
Correct Answer
B:Apply an appropriate Front Door WAF geo-match custom rule addresses the topology, access or delivery requirement in the scenario. Apply it by create a geo-filter custom rule associated with the API security policy; confirm by compare requests from approved and disallowed geographies.
Incorrect Answers
A:Set rule collection group and collection priorities in the correct evaluation order. This concerns denying one destination even though a broader allow exists. Instead, apply an appropriate Front Door WAF geo-match custom rule.
C:Use WAF rate limiting custom rules where available. This concerns an emergency rule to reduce high request rate from a single source. Instead, apply an appropriate Front Door WAF geo-match custom rule.
D:Use Azure Firewall Premium TLS inspection with appropriate certificates. This concerns inspection of application-layer content inside TLS at the central hub. Instead, apply an appropriate Front Door WAF geo-match custom rule.
Question 966
A global API is experiencing repeated unwanted requests from one country. The architecture uses this design: Apply an appropriate Front Door WAF geo-match custom rule. Which configuration should the engineer apply to implement it?
- Assign NIC IP configurations to the ASG and create NSG rules targeting that ASG
- Create a geo-filter custom rule associated with the API security policy
- Associate each VM NIC with an ASG and reference ASGs in NSG rules
- Identify the rule ID and add a scoped exception after analysis
Explanation
Correct Answer
B:Create a geo-filter custom rule associated with the API security policy is the operational configuration for apply an appropriate front door waf geo-match custom rule. The acceptance test is to compare requests from approved and disallowed geographies.
Incorrect Answers
A: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 apply an appropriate front door waf geo-match custom rule, which instead requires create a geo-filter custom rule associated with the api security policy.
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 apply an appropriate front door waf geo-match custom rule, which instead requires create a geo-filter custom rule associated with the api security policy.
D:Identify the rule ID and add a scoped exception after analysis is a concrete step for review waf logs and tune only the specific triggered rule/exclusion. Here the selected design is apply an appropriate front door waf geo-match custom rule, which instead requires create a geo-filter custom rule associated with the api security policy.
Question 967
A global API is experiencing repeated unwanted requests from one country. After the team applies this change—create a geo-filter custom rule associated with the API security policy—which validation best proves the intended result?
- Compare effective policy IDs and sample rule decisions across regions
- Compare requests from approved and disallowed geographies
- Send test requests to protected and excluded hostnames
- Test public SSH denial and approved management access via private network
Explanation
Correct Answer
B:Compare requests from approved and disallowed geographies directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether geo-match rule or security policy association is missing.
Incorrect Answers
A:Compare effective policy IDs and sample rule decisions across regions. This concerns updating firewall rule collections across many regional deployments. Instead, compare requests from approved and disallowed geographies.
C:Send test requests to protected and excluded hostnames. This concerns azure front door waf attached to only one sensitive hostname. Instead, compare requests from approved and disallowed geographies.
D:Test public SSH denial and approved management access via private network. This concerns denying inbound ssh from the internet while permitting approved private management. Instead, compare requests from approved and disallowed geographies.
Question 968
A global API is experiencing repeated unwanted requests from one country. During acceptance testing, requests from blocked countries reach the origin. Which underlying configuration problem best explains the symptom?
- Geo-match rule or security policy association is missing
- The broad ANY-source port 3389 rule remains enabled
- An overly broad higher-priority NSG allow rule takes precedence
- An overly broad wildcard or allow-all application rule exists
Explanation
Correct Answer
A:Geo-match rule or security policy association is missing explains the observed failure: requests from blocked countries reach the origin. Correct the design by using apply an appropriate Front Door WAF geo-match custom rule, implemented through create a geo-filter custom rule associated with the API security policy.
Incorrect Answers
B:The broad ANY-source port 3389 rule remains enabled. This concerns a shared management NSG allows 3389 inbound from every internet address. Here, geo-match rule or security policy association is missing.
C:An overly broad higher-priority NSG allow rule takes precedence. This concerns denying inbound ssh from the internet while permitting approved private management. Here, geo-match rule or security policy association is missing.
D:An overly broad wildcard or allow-all application rule exists. This concerns allowing *.example.org without opening all internet domains. Here, geo-match rule or security policy association is missing.
Question 969
A login page needs an emergency rule to reduce high request rate from a single source. Which Azure networking design most directly satisfies this requirement?
- Use WAF rate limiting custom rules where available
- Check policy association and custom rule priority conditions
- Use Azure Firewall network rules rather than HTTP application rules
- Inspect effective NSG rules on both NIC and subnet with rule priorities
Explanation
Correct Answer
A:Use WAF rate limiting custom rules where available addresses the topology, access or delivery requirement in the scenario. Apply it by create rate-limit match conditions and thresholds for the login route; confirm by generate a controlled burst and confirm rate-limit decisions.
Incorrect Answers
B:Check policy association and custom rule priority conditions. This is relevant when an application gateway uses WAF policy but test requests never trigger expected custom rules. Instead, use WAF rate limiting custom rules where available.
C:Use Azure Firewall network rules rather than HTTP application rules. This concerns filtering non-HTTP TCP traffic by IP, protocol and destination port. Instead, use WAF rate limiting custom rules where available.
D:Inspect effective NSG rules on both NIC and subnet with rule priorities. This concerns a network administrator adds an allow rule but packets are still blocked by a subnet NSG. Instead, use WAF rate limiting custom rules where available.
Question 970
A login page needs an emergency rule to reduce high request rate from a single source. The architecture uses this design: Use WAF rate limiting custom rules where available. Which configuration should the engineer apply to implement it?
- Create rate-limit match conditions and thresholds for the login route
- Assign NIC IP configurations to the ASG and create NSG rules targeting that ASG
- Route Front Door WAF log categories to Log Analytics or storage
- Create AzureFirewallSubnet, deploy Firewall and configure a default UDR next hop
Explanation
Correct Answer
A:Create rate-limit match conditions and thresholds for the login route is the operational configuration for use waf rate limiting custom rules where available. The acceptance test is to generate a controlled burst and confirm rate-limit decisions.
Incorrect Answers
B: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 use waf rate limiting custom rules where available, which instead requires create rate-limit match conditions and thresholds for the login route.
C:Route Front Door WAF log categories to Log Analytics or storage is a concrete step for enable diagnostic export for azure front door waf. Here the selected design is use waf rate limiting custom rules where available, which instead requires create rate-limit match conditions and thresholds for the login route.
D: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 use waf rate limiting custom rules where available, which instead requires create rate-limit match conditions and thresholds for the login route.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests