Microsoft AZ-700 Practice Test 35
Question 340
At Ironwood Consulting, two on-premises campuses are each connected to Azure via separate ExpressRoute circuits. The design must resolve this constraint: The campuses need direct private WAN transit through the Microsoft backbone. Which architecture or control choice most directly meets that requirement?
- Use supported BGP routing across the route-based VPN gateway and on-premises peer
- Select OpenVPN-based point-to-site access with supported Microsoft Entra ID authentication
- Resolve missing Azure prefix advertisement before changing application security policies
- Use ExpressRoute Global Reach to link supported ExpressRoute circuits for on-premises site-to-site connectivity
Explanation
Correct Answer
D:
The campuses need direct private WAN transit through the Microsoft backbone. Use ExpressRoute Global Reach to link supported ExpressRoute circuits for on-premises site-to-site connectivity.
Incorrect Answers
A:
“Use supported BGP routing across the route-based VPN gateway and on-premises peer” concerns A static-only tunnel requires manual route updates for each new branch CIDR, not the actual network issue: The campuses need direct private WAN transit through the Microsoft backbone. Use ExpressRoute Global Reach to link supported ExpressRoute circuits for on-premises site-to-site connectivity.
B:
“Select OpenVPN-based point-to-site access with supported Microsoft Entra ID authentication” concerns The planned gateway uses a tunnel method incompatible with the chosen identity flow, not the actual network issue: The campuses need direct private WAN transit through the Microsoft backbone. Use ExpressRoute Global Reach to link supported ExpressRoute circuits for on-premises site-to-site connectivity.
C:
“Resolve missing Azure prefix advertisement before changing application security policies” concerns The expected VNet prefix is not present in the received BGP route table, not the actual network issue: The campuses need direct private WAN transit through the Microsoft backbone. Use ExpressRoute Global Reach to link supported ExpressRoute circuits for on-premises site-to-site connectivity.
Question 341
At Clearwater Civic, a compliance team needs link-layer encryption on an ExpressRoute Direct physical connection. The observed problem is: The current direct port link is not configured for MACsec. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect ExpressRoute Direct port encryption capabilities and key prerequisites
- Inspect VPN BGP session and whether advertised branch prefixes are received
- Inspect the gateway mode, public IP configuration, and branch tunnel support
- Inspect circuit locations, provider paths, and route preferences
Explanation
Correct Answer
A:
The current direct port link is not configured for MACsec. Inspect ExpressRoute Direct port encryption capabilities and key prerequisites.
Incorrect Answers
B:
“Inspect VPN BGP session and whether advertised branch prefixes are received” concerns A static-only tunnel requires manual route updates for each new branch CIDR, not the actual network issue: The current direct port link is not configured for MACsec. Inspect ExpressRoute Direct port encryption capabilities and key prerequisites.
C:
“Inspect the gateway mode, public IP configuration, and branch tunnel support” concerns The current deployment terminates the tunnel on one active gateway instance, not the actual network issue: The current direct port link is not configured for MACsec. Inspect ExpressRoute Direct port encryption capabilities and key prerequisites.
D:
“Inspect circuit locations, provider paths, and route preferences” concerns All traffic currently depends on one circuit at one peering location, not the actual network issue: The current direct port link is not configured for MACsec. Inspect ExpressRoute Direct port encryption capabilities and key prerequisites.
Question 342
At Ironwood Consulting, a globally distributed site needs anycast edge entry and dynamic acceleration to origins. The observed problem is: Regional-only ingress increases end-user latency outside the deployment region. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect HTTP listeners, path maps, and rule associations
- Inspect current user geography and existing origin routing
- Inspect route caching settings and cache headers for immutable static content
- Inspect existing rewrite rule sets and HTTP response headers
Explanation
Correct Answer
B:
Regional-only ingress increases end-user latency outside the deployment region. Inspect current user geography and existing origin routing.
Incorrect Answers
A:
“Inspect HTTP listeners, path maps, and rule associations” concerns Both URL paths currently reach the same legacy backend, not the actual network issue: Regional-only ingress increases end-user latency outside the deployment region. Inspect current user geography and existing origin routing.
C:
“Inspect route caching settings and cache headers for immutable static content” concerns Every image request unnecessarily reaches the origin, not the actual network issue: Regional-only ingress increases end-user latency outside the deployment region. Inspect current user geography and existing origin routing.
D:
“Inspect existing rewrite rule sets and HTTP response headers” concerns Developers cannot deploy identical header updates across many backend applications, not the actual network issue: Regional-only ingress increases end-user latency outside the deployment region. Inspect current user geography and existing origin routing.
Question 343
At Harborview Legal, remote staff require centrally managed sign-in to a point-to-site VPN from supported clients. The design must resolve this constraint: The planned gateway uses a tunnel method incompatible with the chosen identity flow. Which architecture or control choice most directly meets that requirement?
- Use supported BGP routing across the route-based VPN gateway and on-premises peer
- Choose an explicitly supported route-based gateway policy-based traffic selector interoperability design or replace the legacy peer
- Select OpenVPN-based point-to-site access with supported Microsoft Entra ID authentication
- Choose a P2S client address pool that does not overlap connected networks
Explanation
Correct Answer
C:
The planned gateway uses a tunnel method incompatible with the chosen identity flow. Select OpenVPN-based point-to-site access with supported Microsoft Entra ID authentication.
Incorrect Answers
A:
“Use supported BGP routing across the route-based VPN gateway and on-premises peer” concerns A static-only tunnel requires manual route updates for each new branch CIDR, not the actual network issue: The planned gateway uses a tunnel method incompatible with the chosen identity flow. Select OpenVPN-based point-to-site access with supported Microsoft Entra ID authentication.
B:
“Choose an explicitly supported route-based gateway policy-based traffic selector interoperability design or replace the legacy peer” concerns An engineer assumed all VPN gateway setups interoperate with any remote IKE parameters, not the actual network issue: The planned gateway uses a tunnel method incompatible with the chosen identity flow. Select OpenVPN-based point-to-site access with supported Microsoft Entra ID authentication.
D:
“Choose a P2S client address pool that does not overlap connected networks” concerns The allocated P2S client address range overlaps an on-premises routed LAN, not the actual network issue: The planned gateway uses a tunnel method incompatible with the chosen identity flow. Select OpenVPN-based point-to-site access with supported Microsoft Entra ID authentication.
Question 344
At Redwood Transit, a web host serves /orders and /inventory using different backend pools. The observed problem is: Both URL paths currently reach the same legacy backend. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect frontend IP configuration and reachable ingress paths
- Review gateway SKU and observed traffic/capacity metrics
- Inspect origin group health probes and origin priority values
- Inspect HTTP listeners, path maps, and rule associations
Explanation
Correct Answer
D:
Both URL paths currently reach the same legacy backend. Inspect HTTP listeners, path maps, and rule associations.
Incorrect Answers
A:
“Inspect frontend IP configuration and reachable ingress paths” concerns Its frontend currently uses a public Standard Load Balancer IP, not the actual network issue: Both URL paths currently reach the same legacy backend. Inspect HTTP listeners, path maps, and rule associations.
B:
“Review gateway SKU and observed traffic/capacity metrics” concerns Gateway throughput requirements vary sharply through the day, not the actual network issue: Both URL paths currently reach the same legacy backend. Inspect HTTP listeners, path maps, and rule associations.
C:
“Inspect origin group health probes and origin priority values” concerns Primary origin outages should divert traffic to the healthy secondary, not the actual network issue: Both URL paths currently reach the same legacy backend. Inspect HTTP listeners, path maps, and rule associations.
Question 345
At Meridian Media, hub workloads need to preserve source private IP toward an on-premises inspection appliance. The design must resolve this constraint: Firewall unexpectedly translates flows because destination was treated as public. Which architecture or control choice most directly meets that requirement?
- Configure private IP ranges so expected private destinations avoid unwanted SNAT where supported
- Select threat-intelligence Deny for the approved blocking posture
- Switch to WAF Prevention mode to enforce enabled blocking rules
- Use an appropriate service tag in a scoped NSG egress rule
Explanation
Correct Answer
A:
Firewall unexpectedly translates flows because destination was treated as public. Configure private IP ranges so expected private destinations avoid unwanted SNAT where supported.
Incorrect Answers
B:
“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: Firewall unexpectedly translates flows because destination was treated as public. Configure private IP ranges so expected private destinations avoid unwanted SNAT where supported.
C:
“Switch to WAF Prevention mode to enforce enabled blocking rules” concerns The policy is still in Detection mode so matches are only logged, not the actual network issue: Firewall unexpectedly translates flows because destination was treated as public. Configure private IP ranges so expected private destinations avoid unwanted SNAT where supported.
D:
“Use an appropriate service tag in a scoped NSG egress rule” concerns Manually copied internet address lists are fragile, not the actual network issue: Firewall unexpectedly translates flows because destination was treated as public. Configure private IP ranges so expected private destinations avoid unwanted SNAT where supported.
Question 346
At Highland Research, a sensitive storage account has a working private endpoint. The approved change is intended to address: The public endpoint remains accessible to unapproved sources. Which configuration action best implements the solution?
- Move approved finance workloads to the subnet and grant only that subnet in storage VNet rules
- Set storage public network access to Disabled while retaining approved private endpoint
- Enable Microsoft.Sql on the subnet and create an appropriate SQL server VNet rule
- Set subnet private endpoint network policies for required NSG support and apply least-privilege rules
Explanation
Correct Answer
B:
The public endpoint remains accessible to unapproved sources. Set storage public network access to Disabled while retaining approved private endpoint.
Incorrect Answers
A:
“Move approved finance workloads to the subnet and grant only that subnet in storage VNet rules” 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. Set storage public network access to Disabled while retaining approved private endpoint.
C:
“Enable Microsoft.Sql on the subnet and create an appropriate SQL server VNet rule” concerns Only a server-level IP firewall allowlist currently controls clients, not the actual network issue: The public endpoint remains accessible to unapproved sources. Set storage public network access to Disabled while retaining approved private endpoint.
D:
“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: The public endpoint remains accessible to unapproved sources. Set storage public network access to Disabled while retaining approved private endpoint.
Question 347
At Falcon Works, a new internet-facing VM must permit one known application port but reject unrelated inbound traffic. The observed problem is: A proposal removes all default deny rules rather than adding an exception. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect firewall application rule logs for destination FQDN and protocol
- Inspect DNAT rule collection and public-to-private port mappings
- Inspect effective default inbound NSG rules and approved listener ports
- Check Network Watcher IP flow verify for source IP, destination NIC, TCP 3389
Explanation
Correct Answer
C:
A proposal removes all default deny rules rather than adding an exception. Inspect effective default inbound NSG rules and approved listener ports.
Incorrect Answers
A:
“Inspect firewall application rule logs for destination FQDN and protocol” concerns Security policy forbids unrestricted internet egress, not the actual network issue: A proposal removes all default deny rules rather than adding an exception. Inspect effective default inbound NSG rules and approved listener ports.
B:
“Inspect DNAT rule collection and public-to-private port mappings” concerns Inbound packets arrive at Azure Firewall public IP but have no translation, not the actual network issue: A proposal removes all default deny rules rather than adding an exception. Inspect effective default inbound NSG rules and approved listener ports.
D:
“Check Network Watcher IP flow verify for source IP, destination NIC, TCP 3389” concerns One NSG rule denies TCP 3389 from the approved source, not the actual network issue: A proposal removes all default deny rules rather than adding an exception. Inspect effective default inbound NSG rules and approved listener ports.
Question 348
At Cobalt Analytics, a partner needs a stable small range of Azure public egress addresses for allowlisting. The observed problem is: Unrelated ad hoc public IPs cause repeated partner firewall changes. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Check current logging scope and whether flow logs exist on each required VNet
- Identify which VNet subnet will hold the private endpoint's NIC
- Compare the VNet DNS settings and each VM's current resolver configuration
- Inventory current public IPs and the partner's accepted prefix sizes
Explanation
Correct Answer
D:
Unrelated ad hoc public IPs cause repeated partner firewall changes. Inventory current public IPs and the partner's accepted prefix sizes.
Incorrect Answers
A:
“Check current logging scope and whether flow logs exist on each required VNet” concerns A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs, not the actual network issue: Unrelated ad hoc public IPs cause repeated partner firewall changes. Inventory current public IPs and the partner's accepted prefix sizes.
B:
“Identify which VNet subnet will hold the private endpoint's NIC” concerns The engineer confused the private endpoint subnet with the target storage service subnet, not the actual network issue: Unrelated ad hoc public IPs cause repeated partner firewall changes. Inventory current public IPs and the partner's accepted prefix sizes.
C:
“Compare the VNet DNS settings and each VM's current resolver configuration” concerns Existing VMs still query the previous DNS configuration, not the actual network issue: Unrelated ad hoc public IPs cause repeated partner firewall changes. Inventory current public IPs and the partner's accepted prefix sizes.
Question 349
At Harborview Legal, remote staff require centrally managed sign-in to a point-to-site VPN from supported clients. The networking change intended to correct this problem has been applied: The planned gateway uses a tunnel method incompatible with the chosen identity flow. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm an approved Entra identity can establish the P2S VPN session
- Connect a client and verify unique address assignment and branch routes
- Confirm requested branch and circuit connection types are configurable
- Verify a remote VPN client obtains hub connectivity to authorized spokes
Explanation
Correct Answer
A:
The planned gateway uses a tunnel method incompatible with the chosen identity flow. Confirm an approved Entra identity can establish the P2S VPN session.
Incorrect Answers
B:
“Connect a client and verify unique address assignment and branch routes” concerns The allocated P2S client address range overlaps an on-premises routed LAN, not the actual network issue: The planned gateway uses a tunnel method incompatible with the chosen identity flow. Confirm an approved Entra identity can establish the P2S VPN session.
C:
“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 planned gateway uses a tunnel method incompatible with the chosen identity flow. Confirm an approved Entra identity can establish the P2S VPN session.
D:
“Verify a remote VPN client obtains hub connectivity to authorized spokes” concerns The virtual hub does not yet contain a user VPN gateway, not the actual network issue: The planned gateway uses a tunnel method incompatible with the chosen identity flow. Confirm an approved Entra identity can establish the P2S VPN session.
Question 350
At Aspen Ridge Software, a VM subnet has a broad allow at priority 300 and a targeted deny at priority 200. The design must resolve this constraint: Operators assumed lower number means lower precedence. Which architecture or control choice most directly meets that requirement?
- Switch to WAF Prevention mode to enforce enabled blocking rules
- Place specific traffic decisions ahead of broad rules using lower numeric priorities
- Define egress permission in an outbound NSG rule, not an inbound rule
- Use Azure Firewall DNS proxy for consistent FQDN resolution in applicable network-rule scenarios
Explanation
Correct Answer
B:
Operators assumed lower number means lower precedence. Place specific traffic decisions ahead of broad rules using lower numeric priorities.
Incorrect Answers
A:
“Switch to WAF Prevention mode to enforce enabled blocking rules” concerns The policy is still in Detection mode so matches are only logged, not the actual network issue: Operators assumed lower number means lower precedence. Place specific traffic decisions ahead of broad rules using lower numeric priorities.
C:
“Define egress permission in an outbound NSG rule, not an inbound rule” concerns The operator added an inbound allow rule but nothing changed, not the actual network issue: Operators assumed lower number means lower precedence. Place specific traffic decisions ahead of broad rules using lower numeric priorities.
D:
“Use Azure Firewall DNS proxy for consistent FQDN resolution in applicable network-rule scenarios” concerns Inconsistent DNS decisions lead to intermittent destination rule mismatch, not the actual network issue: Operators assumed lower number means lower precedence. Place specific traffic decisions ahead of broad rules using lower numeric priorities.