Microsoft AZ-700 Practice Test 65
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.
Question 641
At Pinecrest Energy, a subnet should reach only approved Storage accounts via service endpoints. The observed problem is: Enabling Microsoft.Storage alone does not restrict which accounts can be reached. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect subnet service endpoint policies and permitted storage resource IDs
- Inspect private endpoint connection state and blob privatelink DNS records
- Check Microsoft.Sql service endpoint and SQL virtual network rule configuration
- Inspect DNS zone group association and current private endpoint IP record
Explanation
Correct Answer
A:
Enabling Microsoft.Storage alone does not restrict which accounts can be reached. Inspect subnet service endpoint policies and permitted storage resource IDs.
Incorrect Answers
B:
“Inspect private endpoint connection state and blob privatelink DNS records” concerns The app still resolves its storage hostname to a public endpoint, not the actual network issue: Enabling Microsoft.Storage alone does not restrict which accounts can be reached. Inspect subnet service endpoint policies and permitted storage resource IDs.
C:
“Check Microsoft.Sql service endpoint and SQL virtual network rule configuration” concerns Only a server-level IP firewall allowlist currently controls clients, not the actual network issue: Enabling Microsoft.Storage alone does not restrict which accounts can be reached. Inspect subnet service endpoint policies and permitted storage resource IDs.
D:
“Inspect DNS zone group association and current private endpoint IP record” concerns The endpoint IP changes after redeployment and name resolution fails, not the actual network issue: Enabling Microsoft.Storage alone does not restrict which accounts can be reached. Inspect subnet service endpoint policies and permitted storage resource IDs.
Question 642
At Bluebell Insurance, a remote-access network must validate VPN users against existing RADIUS servers. The observed problem is: The team cannot migrate sign-in to Microsoft Entra ID for this rollout. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Compare downloaded VPN client configuration with the current gateway P2S settings
- Inspect P2S server authentication mode and RADIUS reachability
- Inspect user VPN gateway association and P2S configuration in the virtual hub
- Inspect BFD support and BGP sessions on the peering devices
Explanation
Correct Answer
B:
The team cannot migrate sign-in to Microsoft Entra ID for this rollout. Inspect P2S server authentication mode and RADIUS reachability.
Incorrect Answers
A:
“Compare downloaded VPN client configuration with the current gateway P2S settings” concerns Administrators changed P2S authentication and clients retain old profiles, not the actual network issue: The team cannot migrate sign-in to Microsoft Entra ID for this rollout. Inspect P2S server authentication mode and RADIUS reachability.
C:
“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: The team cannot migrate sign-in to Microsoft Entra ID for this rollout. Inspect P2S server authentication mode and RADIUS reachability.
D:
“Inspect BFD support and BGP sessions on the peering devices” concerns BGP failure detection after a silent link fault is too slow, not the actual network issue: The team cannot migrate sign-in to Microsoft Entra ID for this rollout. Inspect P2S server authentication mode and RADIUS reachability.
Question 643
At Horizon Education, a VPN peer rejects security association negotiation although public endpoints are reachable. The networking change intended to correct this problem has been applied: The peer requires agreed encryption, integrity, DH, and PFS parameters. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm the campus receives the exact Azure subnet prefix and can connect
- Verify a newly advertised subnet appears in Azure effective routes
- Confirm phase-1 and phase-2 negotiation succeeds with the agreed parameters
- Confirm requested branch and circuit connection types are configurable
Explanation
Correct Answer
C:
The peer requires agreed encryption, integrity, DH, and PFS parameters. Confirm phase-1 and phase-2 negotiation succeeds with the agreed parameters.
Incorrect Answers
A:
“Confirm the campus receives the exact Azure subnet prefix and can connect” concerns The expected VNet prefix is not present in the received BGP route table, not the actual network issue: The peer requires agreed encryption, integrity, DH, and PFS parameters. Confirm phase-1 and phase-2 negotiation succeeds with the agreed parameters.
B:
“Verify a newly advertised subnet appears in Azure effective routes” concerns A static-only tunnel requires manual route updates for each new branch CIDR, not the actual network issue: The peer requires agreed encryption, integrity, DH, and PFS parameters. Confirm phase-1 and phase-2 negotiation succeeds with the agreed parameters.
D:
“Confirm requested branch and circuit connection types are configurable” concerns The planned Virtual WAN Basic tier lacks required advanced connectivity features, not the actual network issue: The peer requires agreed encryption, integrity, DH, and PFS parameters. Confirm phase-1 and phase-2 negotiation succeeds with the agreed parameters.
Question 644
At Foxglove Travel, the platform team must deploy consistent hub-spoke connections to many VNets. The team has addressed this networking issue: Manual peering has left several newly created spokes disconnected. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor BGP peer state and unexpected prefix changes
- Monitor private endpoint connection state and subnet address utilization
- Monitor Bastion connection diagnostics and subnet resource compliance
- Detect noncompliant network-group membership and configuration deployment status
Explanation
Correct Answer
D:
Manual peering has left several newly created spokes disconnected. Detect noncompliant network-group membership and configuration deployment status.
Incorrect Answers
A:
“Monitor BGP peer state and unexpected prefix changes” concerns Manual static routes to changing remote networks go stale, not the actual network issue: Manual peering has left several newly created spokes disconnected. Detect noncompliant network-group membership and configuration deployment status.
B:
“Monitor private endpoint connection state and subnet address utilization” concerns The engineer confused the private endpoint subnet with the target storage service subnet, not the actual network issue: Manual peering has left several newly created spokes disconnected. Detect noncompliant network-group membership and configuration deployment status.
C:
“Monitor Bastion connection diagnostics and subnet resource compliance” concerns The VNet contains no AzureBastionSubnet of a supported size, not the actual network issue: Manual peering has left several newly created spokes disconnected. Detect noncompliant network-group membership and configuration deployment status.
Question 645
At Winterfield Group, a Front Door origin is shown unhealthy despite serving site content. The observed problem is: Origin expects a specific Host header on the configured probe endpoint. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect origin host header and origin-group health probe protocol/path
- Inspect backend HTTP settings and session-affinity behavior
- Inspect whether Gateway Load Balancer chaining is configured on the intended frontend
- Inspect custom-domain validation and HTTPS certificate status
Explanation
Correct Answer
A:
Origin expects a specific Host header on the configured probe endpoint. Inspect origin host header and origin-group health probe protocol/path.
Incorrect Answers
B:
“Inspect backend HTTP settings and session-affinity behavior” concerns The current gateway sends sequential sessions to different healthy backends, not the actual network issue: Origin expects a specific Host header on the configured probe endpoint. Inspect origin host header and origin-group health probe protocol/path.
C:
“Inspect whether Gateway Load Balancer chaining is configured on the intended frontend” concerns The current public frontend does not route traffic through inspection appliances, not the actual network issue: Origin expects a specific Host header on the configured probe endpoint. Inspect origin host header and origin-group health probe protocol/path.
D:
“Inspect custom-domain validation and HTTPS certificate status” concerns Custom domain ownership and managed TLS are not yet fully provisioned, not the actual network issue: Origin expects a specific Host header on the configured probe endpoint. Inspect origin host header and origin-group health probe protocol/path.
Question 646
At Millstone Gaming, remote administrators use Azure Bastion to reach private VMs. The networking change intended to correct this problem has been applied: The target VM NSG blocks traffic from AzureBastionSubnet. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify outbound flow reaches firewall and policy denies unauthorized domains
- Open a Bastion session and confirm target VM login without public VM IP
- Verify the required tuple is allowed by both subnet and NIC NSGs
- Confirm database flow passes and a different unauthorized port is denied
Explanation
Correct Answer
B:
The target VM NSG blocks traffic from AzureBastionSubnet. Open a Bastion session and confirm target VM login without public VM IP.
Incorrect Answers
A:
“Verify outbound flow reaches firewall and policy denies unauthorized domains” concerns Subnet effective route still uses Internet next hop, not the actual network issue: The target VM NSG blocks traffic from AzureBastionSubnet. Open a Bastion session and confirm target VM login without public VM IP.
C:
“Verify the required tuple is allowed by both subnet and NIC NSGs” concerns An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic, not the actual network issue: The target VM NSG blocks traffic from AzureBastionSubnet. Open a Bastion session and confirm target VM login without public VM IP.
D:
“Confirm database flow passes and a different unauthorized port is denied” concerns Using an HTTP application rule cannot match this raw TCP database flow, not the actual network issue: The target VM NSG blocks traffic from AzureBastionSubnet. Open a Bastion session and confirm target VM login without public VM IP.
Question 647
At Meridian Media, hub workloads need to preserve source private IP toward an on-premises inspection appliance. The networking change intended to correct this problem has been applied: Firewall unexpectedly translates flows because destination was treated as public. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Test against a controlled indicator procedure and verify block event is logged
- Confirm an approved SQL-injection test pattern is detected while normal traffic succeeds
- Capture the on-prem destination flow and confirm expected original private source
- Run IP flow verify and confirm approval only for the management subnet source
Explanation
Correct Answer
C:
Firewall unexpectedly translates flows because destination was treated as public. Capture the on-prem destination flow and confirm expected original private source.
Incorrect Answers
A:
“Test against a controlled indicator procedure and verify block event is logged” concerns Current policy leaves threat-intelligence action in alert-only mode, not the actual network issue: Firewall unexpectedly translates flows because destination was treated as public. Capture the on-prem destination flow and confirm expected original private source.
B:
“Confirm an approved SQL-injection test pattern is detected while normal traffic succeeds” concerns The gateway only has manual IP restrictions rather than web-attack inspection, not the actual network issue: Firewall unexpectedly translates flows because destination was treated as public. Capture the on-prem destination flow and confirm expected original private source.
D:
“Run IP flow verify and confirm approval only for the management subnet source” concerns One NSG rule denies TCP 3389 from the approved source, not the actual network issue: Firewall unexpectedly translates flows because destination was treated as public. Capture the on-prem destination flow and confirm expected original private source.
Question 648
At Pinecrest Energy, an internet service uses two regional HTTPS endpoints and needs DNS-level failover. The design must resolve this constraint: Secondary endpoint should receive traffic only when primary monitoring reports failure. Which architecture or control choice most directly meets that requirement?
- Use route-domain and path matching to bind hostnames to intended origin groups
- Plan explicit outbound rules and adequate frontend IP/SNAT port allocation
- Use a validated Front Door custom domain with managed HTTPS certificate when supported
- Choose Priority routing with primary and secondary endpoints in Traffic Manager
Explanation
Correct Answer
D:
Secondary endpoint should receive traffic only when primary monitoring reports failure. Choose Priority routing with primary and secondary endpoints in Traffic Manager.
Incorrect Answers
A:
“Use route-domain and path matching to bind hostnames to intended origin groups” concerns Both domains were accidentally attached to the same catchall route, not the actual network issue: Secondary endpoint should receive traffic only when primary monitoring reports failure. Choose Priority routing with primary and secondary endpoints in Traffic Manager.
B:
“Plan explicit outbound rules and adequate frontend IP/SNAT port allocation” concerns The default outbound configuration has insufficient SNAT capacity, not the actual network issue: Secondary endpoint should receive traffic only when primary monitoring reports failure. Choose Priority routing with primary and secondary endpoints in Traffic Manager.
C:
“Use a validated Front Door custom domain with managed HTTPS certificate when supported” concerns Custom domain ownership and managed TLS are not yet fully provisioned, not the actual network issue: Secondary endpoint should receive traffic only when primary monitoring reports failure. Choose Priority routing with primary and secondary endpoints in Traffic Manager.
Question 649
At Westwind Medical, a VM NIC and its subnet each have NSGs. The approved change is intended to address: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Which configuration action best implements the solution?
- Update the relevant subnet NSG to permit only the authorized flow
- Enable DNS proxy on firewall and direct approved client DNS requests to its private IP
- Set the targeted deny rule at a smaller priority number than the broad allow
- Configure Premium TLS inspection policy and deploy trusted inspection CA to clients
Explanation
Correct Answer
A:
An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Update the relevant subnet NSG to permit only the authorized flow.
Incorrect Answers
B:
“Enable DNS proxy on firewall and direct approved client DNS requests to its private IP” concerns Inconsistent DNS decisions lead to intermittent destination rule mismatch, not the actual network issue: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Update the relevant subnet NSG to permit only the authorized flow.
C:
“Set the targeted deny rule at a smaller priority number than the broad allow” concerns Operators assumed lower number means lower precedence, not the actual network issue: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Update the relevant subnet NSG to permit only the authorized flow.
D:
“Configure Premium TLS inspection policy and deploy trusted inspection CA to clients” concerns Standard network-rule matching cannot inspect HTTPS content, not the actual network issue: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Update the relevant subnet NSG to permit only the authorized flow.
Question 650
At Highland Research, a sensitive storage account has a working private endpoint. The observed problem is: The public endpoint remains accessible to unapproved sources. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect whether a service endpoint policy is attached to the workload subnet
- Inspect storage networking public access and private endpoint policies
- Identify which source subnets and VNet rules currently authorize access
- Trace conditional forwarding from on-prem DNS to Azure private zone resolution
Explanation
Correct Answer
B:
The public endpoint remains accessible to unapproved sources. Inspect storage networking public access and private endpoint policies.
Incorrect Answers
A:
“Inspect whether a service endpoint policy is attached to the workload subnet” 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. Inspect storage networking public access and private endpoint policies.
C:
“Identify which source subnets and VNet rules currently authorize access” concerns The current storage VNet rule grants access to the entire shared subnet, not the actual network issue: The public endpoint remains accessible to unapproved sources. Inspect storage networking public access and private endpoint policies.
D:
“Trace conditional forwarding from on-prem DNS to Azure private zone resolution” 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. Inspect storage networking public access and private endpoint policies.