Microsoft AZ-700 Practice Test 64
Question 630
At Westwind Medical, windows-managed remote devices must connect to Azure hybrid resources with automated VPN. The observed problem is: A standard user-launched connection workflow does not satisfy auto-connect requirements. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Compare P2S pool against VNet and on-prem address plans
- Inspect the target Windows VPN client profile and Azure gateway authentication/tunnel support
- Inspect circuit authorization and ExpressRoute gateway in the hub
- Inspect user VPN gateway association and P2S configuration in the virtual hub
Explanation
Correct Answer
B:
Inspect the target Windows VPN client profile and Azure gateway authentication/tunnel support. Always On VPN requires an appropriate client device or user profile, compatible authentication and a supported VPN gateway design; normal manually initiated P2S is not equivalent.
Incorrect Answers
A:
“Compare P2S pool against VNet and on-prem address plans” concerns The allocated P2S client address range overlaps an on-premises routed LAN, not the actual network issue: A standard user-launched connection workflow does not satisfy auto-connect requirements. Inspect the target Windows VPN client profile and Azure gateway authentication/tunnel support. Always On VPN requires an appropriate client device or user profile, compatible authentication and a supported VPN gateway design; normal manually initiated P2S is not equivalent.
C:
“Inspect circuit authorization and ExpressRoute gateway in the hub” concerns The ExpressRoute circuit is active but not attached to the virtual hub, not the actual network issue: A standard user-launched connection workflow does not satisfy auto-connect requirements. Inspect the target Windows VPN client profile and Azure gateway authentication/tunnel support. Always On VPN requires an appropriate client device or user profile, compatible authentication and a supported VPN gateway design; normal manually initiated P2S is not equivalent.
D:
“Inspect user VPN gateway association and P2S configuration in the virtual hub” concerns The virtual hub does not yet contain a user VPN gateway, not the actual network issue: A standard user-launched connection workflow does not satisfy auto-connect requirements. Inspect the target Windows VPN client profile and Azure gateway authentication/tunnel support. Always On VPN requires an appropriate client device or user profile, compatible authentication and a supported VPN gateway design; normal manually initiated P2S is not equivalent.
Question 631
At Highland Research, a sensitive storage account has a working private endpoint. The networking change intended to correct this problem has been applied: The public endpoint remains accessible to unapproved sources. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Resolve SQL FQDN from an on-prem host to the approved private endpoint IP
- Test permitted accounts are reachable and an unrelated account is denied
- Test a private approved client succeeds and public-only client fails
- Attempt access to allowed and disallowed Storage accounts from the subnet
Explanation
Correct Answer
C:
The public endpoint remains accessible to unapproved sources. Test a private approved client succeeds and public-only client fails.
Incorrect Answers
A:
“Resolve SQL FQDN from an on-prem host to the approved private endpoint IP” concerns Their resolver still returns the public address for the Azure SQL FQDN, not the actual network issue: The public endpoint remains accessible to unapproved sources. Test a private approved client succeeds and public-only client fails.
B:
“Test permitted accounts are reachable and an unrelated account is denied” concerns The team attempted to use NSG service tags as a per-account allowlist, not the actual network issue: The public endpoint remains accessible to unapproved sources. Test a private approved client succeeds and public-only client fails.
D:
“Attempt access to allowed and disallowed Storage accounts from the subnet” concerns Enabling Microsoft.Storage alone does not restrict which accounts can be reached, not the actual network issue: The public endpoint remains accessible to unapproved sources. Test a private approved client succeeds and public-only client fails.
Question 632
At Clearwater Civic, a public partner service must be forwarded to an approved private VM listener. The design must resolve this constraint: Inbound packets arrive at Azure Firewall public IP but have no translation. Which architecture or control choice most directly meets that requirement?
- Use an appropriate service tag in a scoped NSG egress rule
- Design coordinated allow rules at both required scopes without overriding security policy
- Select threat-intelligence Deny for the approved blocking posture
- Use a DNAT rule translating intended firewall public destination to private host/port
Explanation
Correct Answer
D:
Inbound packets arrive at Azure Firewall public IP but have no translation. Use a DNAT rule translating intended firewall public destination to private host/port.
Incorrect Answers
A:
“Use an appropriate service tag in a scoped NSG egress rule” concerns Manually copied internet address lists are fragile, not the actual network issue: Inbound packets arrive at Azure Firewall public IP but have no translation. Use a DNAT rule translating intended firewall public destination to private host/port.
B:
“Design coordinated allow rules at both required scopes without overriding security policy” concerns An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic, not the actual network issue: Inbound packets arrive at Azure Firewall public IP but have no translation. Use a DNAT rule translating intended firewall public destination to private host/port.
C:
“Select threat-intelligence Deny for the approved blocking posture” concerns Current policy leaves threat-intelligence action in alert-only mode, not the actual network issue: Inbound packets arrive at Azure Firewall public IP but have no translation. Use a DNAT rule translating intended firewall public destination to private host/port.
Question 633
At Evergreen Services, a global application has private endpoints in separate Azure regions for a regional service architecture. The approved change is intended to address: One region's private endpoint becomes unavailable during failover. Which configuration action best implements the solution?
- Provision endpoints in each consumer region and maintain tested regional DNS answers
- Set subnet private endpoint network policies for required NSG support and apply least-privilege rules
- Associate a policy listing permitted Storage accounts with the subnet
- Create and associate an endpoint policy with the approved Storage account resources
Explanation
Correct Answer
A:
One region's private endpoint becomes unavailable during failover. Provision endpoints in each consumer region and maintain tested regional DNS answers.
Incorrect Answers
B:
“Set subnet private endpoint network policies for required NSG support and apply least-privilege rules” concerns An NSG rule appears ineffective because endpoint network policies are disabled, not the actual network issue: One region's private endpoint becomes unavailable during failover. Provision endpoints in each consumer region and maintain tested regional DNS answers.
C:
“Associate a policy listing permitted Storage accounts with the subnet” concerns The team attempted to use NSG service tags as a per-account allowlist, not the actual network issue: One region's private endpoint becomes unavailable during failover. Provision endpoints in each consumer region and maintain tested regional DNS answers.
D:
“Create and associate an endpoint policy with the approved Storage account resources” concerns Enabling Microsoft.Storage alone does not restrict which accounts can be reached, not the actual network issue: One region's private endpoint becomes unavailable during failover. Provision endpoints in each consumer region and maintain tested regional DNS answers.
Question 634
At Oakbridge Logistics, a VM NIC cannot accept an expected TCP connection. The team has addressed this networking issue: An NSG deny may be taking precedence over an allow. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Alert on test failure percentage and latency trend
- Monitor denied flows and effective security rule changes
- Monitor route-advertisement and route-table drift for branch destinations
- Monitor availability and address assignment separately for each IP family
Explanation
Correct Answer
B:
An NSG deny may be taking precedence over an allow. Monitor denied flows and effective security rule changes.
Incorrect Answers
A:
“Alert on test failure percentage and latency trend” concerns One-time ping tests do not reveal recurring connectivity degradation, not the actual network issue: An NSG deny may be taking precedence over an allow. Monitor denied flows and effective security rule changes.
C:
“Monitor route-advertisement and route-table drift for branch destinations” concerns The branch route may be overridden by a UDR or missing BGP propagation, not the actual network issue: An NSG deny may be taking precedence over an allow. Monitor denied flows and effective security rule changes.
D:
“Monitor availability and address assignment separately for each IP family” concerns The workload has only IPv4 private addressing and an IPv4 frontend, not the actual network issue: An NSG deny may be taking precedence over an allow. Monitor denied flows and effective security rule changes.
Question 635
At Evergreen Services, vMs behind a regional public Load Balancer intermittently fail outbound connections. The networking change intended to correct this problem has been applied: The default outbound configuration has insufficient SNAT capacity. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Request both hostnames and verify each resolves to its intended origin
- Confirm backend shows healthy and routing resumes without masking application errors
- Load-test external connections and verify successful source translation
- Confirm VNet clients connect while unsolicited internet clients cannot reach the API
Explanation
Correct Answer
C:
The default outbound configuration has insufficient SNAT capacity. Load-test external connections and verify successful source translation.
Incorrect Answers
A:
“Request both hostnames and verify each resolves to its intended origin” concerns Both domains were accidentally attached to the same catchall route, not the actual network issue: The default outbound configuration has insufficient SNAT capacity. Load-test external connections and verify successful source translation.
B:
“Confirm backend shows healthy and routing resumes without masking application errors” concerns The app only returns HTTP 200 for the correct Host header and /health path, not the actual network issue: The default outbound configuration has insufficient SNAT capacity. Load-test external connections and verify successful source translation.
D:
“Confirm VNet clients connect while unsolicited internet clients cannot reach the API” concerns Its frontend currently uses a public Standard Load Balancer IP, not the actual network issue: The default outbound configuration has insufficient SNAT capacity. Load-test external connections and verify successful source translation.
Question 636
At Highland Research, an application team deploys a regional HTTP reverse proxy. The networking change intended to correct this problem has been applied: The proposed Application Gateway subnet already hosts unrelated virtual machines. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify resolved findings no longer appear after assessment refresh
- Verify new outbound connections are translated to the configured NAT public IP
- Compare assigned NICs plus free addresses against the usable capacity of the subnet
- Verify the gateway provisions and handles traffic to its registered backends
Explanation
Correct Answer
D:
The proposed Application Gateway subnet already hosts unrelated virtual machines. Verify the gateway provisions and handles traffic to its registered backends.
Incorrect Answers
A:
“Verify resolved findings no longer appear after assessment refresh” concerns A weekly spreadsheet misses new attack paths and insecure exposure changes, not the actual network issue: The proposed Application Gateway subnet already hosts unrelated virtual machines. Verify the gateway provisions and handles traffic to its registered backends.
B:
“Verify new outbound connections are translated to the configured NAT public IP” concerns VM egress uses default outbound access and source addresses cannot be allowlisted, not the actual network issue: The proposed Application Gateway subnet already hosts unrelated virtual machines. Verify the gateway provisions and handles traffic to its registered backends.
C:
“Compare assigned NICs plus free addresses against the usable capacity of the subnet” concerns The planner counted every address in a /27 as assignable to VMs, not the actual network issue: The proposed Application Gateway subnet already hosts unrelated virtual machines. Verify the gateway provisions and handles traffic to its registered backends.
Question 637
At Highland Research, an application team deploys a regional HTTP reverse proxy. The team has addressed this networking issue: The proposed Application Gateway subnet already hosts unrelated virtual machines. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Detect unauthorized resource placements in the gateway subnet
- Detect missing or stale auto-registered VM records
- Monitor inbound endpoint reachability and forwarded-query failures
- Monitor gateway resource health and GatewaySubnet changes
Explanation
Correct Answer
A:
The proposed Application Gateway subnet already hosts unrelated virtual machines. Detect unauthorized resource placements in the gateway subnet.
Incorrect Answers
B:
“Detect missing or stale auto-registered VM records” concerns VM addresses change but the zone only has manually entered records, not the actual network issue: The proposed Application Gateway subnet already hosts unrelated virtual machines. Detect unauthorized resource placements in the gateway subnet.
C:
“Monitor inbound endpoint reachability and forwarded-query failures” concerns On-premises queries cannot use Azure's VNet-scoped resolver directly, not the actual network issue: The proposed Application Gateway subnet already hosts unrelated virtual machines. Detect unauthorized resource placements in the gateway subnet.
D:
“Monitor gateway resource health and GatewaySubnet changes” concerns Gateway deployment is blocked because the gateway subnet is missing, not the actual network issue: The proposed Application Gateway subnet already hosts unrelated virtual machines. Detect unauthorized resource placements in the gateway subnet.
Question 638
At Granite Bay Retail, a team sizes a subnet for a fixed fleet of private-addressed virtual machines. The design must resolve this constraint: The planner counted every address in a /27 as assignable to VMs. Which architecture or control choice most directly meets that requirement?
- Use virtual network flow logs for newly configured network traffic collection
- Choose a subnet CIDR with sufficient usable private addresses after reservations and growth
- Use a Custom IP Prefix (BYOIP) instead of treating owned public space as an Azure-owned prefix
- Link the private DNS zone to the consumer VNet for native Azure resolution
Explanation
Correct Answer
B:
The planner counted every address in a /27 as assignable to VMs. Choose a subnet CIDR with sufficient usable private addresses after reservations and growth.
Incorrect Answers
A:
“Use virtual network flow logs for newly configured network traffic collection” concerns A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs, not the actual network issue: The planner counted every address in a /27 as assignable to VMs. Choose a subnet CIDR with sufficient usable private addresses after reservations and growth.
C:
“Use a Custom IP Prefix (BYOIP) instead of treating owned public space as an Azure-owned prefix” concerns Its registered public address allocation is not yet onboarded to Azure, not the actual network issue: The planner counted every address in a /27 as assignable to VMs. Choose a subnet CIDR with sufficient usable private addresses after reservations and growth.
D:
“Link the private DNS zone to the consumer VNet for native Azure resolution” concerns The zone exists but has no virtual network link to the spoke, not the actual network issue: The planner counted every address in a /27 as assignable to VMs. Choose a subnet CIDR with sufficient usable private addresses after reservations and growth.
Question 639
At Silverline Commerce, a storage account has a VNet firewall rule for the application subnet. The design must resolve this constraint: Connections still fail after moving the application into a replacement subnet. Which architecture or control choice most directly meets that requirement?
- Place finance workloads in a dedicated subnet for service-endpoint-based storage restriction
- Use Private Link connection approval workflow for partner endpoints
- Enable the correct service endpoint on the new source subnet before relying on the rule
- Use a private endpoint DNS zone group to integrate supported privatelink records
Explanation
Correct Answer
C:
Connections still fail after moving the application into a replacement subnet. Enable the correct service endpoint on the new source subnet before relying on the rule.
Incorrect Answers
A:
“Place finance workloads in a dedicated subnet for service-endpoint-based storage restriction” concerns The current storage VNet rule grants access to the entire shared subnet, not the actual network issue: Connections still fail after moving the application into a replacement subnet. Enable the correct service endpoint on the new source subnet before relying on the rule.
B:
“Use Private Link connection approval workflow for partner endpoints” concerns The provider requires explicit authorization for each external endpoint connection, not the actual network issue: Connections still fail after moving the application into a replacement subnet. Enable the correct service endpoint on the new source subnet before relying on the rule.
D:
“Use a private endpoint DNS zone group to integrate supported privatelink records” concerns The endpoint IP changes after redeployment and name resolution fails, not the actual network issue: Connections still fail after moving the application into a replacement subnet. Enable the correct service endpoint on the new source subnet before relying on the rule.
Question 640
At Evergreen Services, a zone-spanning regional service requires a resilient public frontend IP. The networking change intended to correct this problem has been applied: A zone-pinned frontend address undermines the intended multi-zone design. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Trace a public egress test through firewall logs and verify no direct route
- Observe scheduled test results and latency when a controlled path issue occurs
- Test application access over IPv4 and IPv6 separately
- Validate the frontend retains reachability during a planned zone-failure exercise
Explanation
Correct Answer
D:
A zone-pinned frontend address undermines the intended multi-zone design. Validate the frontend retains reachability during a planned zone-failure exercise.
Incorrect Answers
A:
“Trace a public egress test through firewall logs and verify no direct route” concerns An existing route table sends 0.0.0.0/0 to Internet, not the actual network issue: A zone-pinned frontend address undermines the intended multi-zone design. Validate the frontend retains reachability during a planned zone-failure exercise.
B:
“Observe scheduled test results and latency when a controlled path issue occurs” concerns One-time ping tests do not reveal recurring connectivity degradation, not the actual network issue: A zone-pinned frontend address undermines the intended multi-zone design. Validate the frontend retains reachability during a planned zone-failure exercise.
C:
“Test application access over IPv4 and IPv6 separately” concerns The workload has only IPv4 private addressing and an IPv4 frontend, not the actual network issue: A zone-pinned frontend address undermines the intended multi-zone design. Validate the frontend retains reachability during a planned zone-failure exercise.