Microsoft AZ-700 Practice Test 25
Question 240
At Winterfield Group, an ExpressRoute connection is up but a newly created Azure subnet is unreachable from a campus. The networking change intended to correct this problem has been applied: The expected VNet prefix is not present in the received BGP route table. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm phase-1 and phase-2 negotiation succeeds with the agreed parameters
- Confirm an approved Entra identity can establish the P2S VPN session
- Verify MACsec session is established on the physical circuit
- Confirm the campus receives the exact Azure subnet prefix and can connect
Explanation
Correct Answer
D:
The expected VNet prefix is not present in the received BGP route table. Confirm the campus receives the exact Azure subnet prefix and can connect.
Incorrect Answers
A:
“Confirm phase-1 and phase-2 negotiation succeeds with the agreed parameters” concerns The peer requires agreed encryption, integrity, DH, and PFS parameters, not the actual network issue: The expected VNet prefix is not present in the received BGP route table. Confirm the campus receives the exact Azure subnet prefix and can connect.
B:
“Confirm an approved Entra identity can establish the P2S VPN session” concerns The planned gateway uses a tunnel method incompatible with the chosen identity flow, not the actual network issue: The expected VNet prefix is not present in the received BGP route table. Confirm the campus receives the exact Azure subnet prefix and can connect.
C:
“Verify MACsec session is established on the physical circuit” concerns The current direct port link is not configured for MACsec, not the actual network issue: The expected VNet prefix is not present in the received BGP route table. Confirm the campus receives the exact Azure subnet prefix and can connect.
Question 241
At Winterfield Group, operations wants Azure Firewall to block network destinations found in Microsoft threat-intelligence feeds. The design must resolve this constraint: Current policy leaves threat-intelligence action in alert-only mode. Which architecture or control choice most directly meets that requirement?
- Select threat-intelligence Deny for the approved blocking posture
- Place specific traffic decisions ahead of broad rules using lower numeric priorities
- Associate a baseline NSG at the subnet for consistent subnet-wide controls
- Use a DNAT rule translating intended firewall public destination to private host/port
Explanation
Correct Answer
A:
Current policy leaves threat-intelligence action in alert-only mode. Select threat-intelligence Deny for the approved blocking posture.
Incorrect Answers
B:
“Place specific traffic decisions ahead of broad rules using lower numeric priorities” concerns Operators assumed lower number means lower precedence, not the actual network issue: Current policy leaves threat-intelligence action in alert-only mode. Select threat-intelligence Deny for the approved blocking posture.
C:
“Associate a baseline NSG at the subnet for consistent subnet-wide controls” concerns The current design configures only individual NIC NSGs, not the actual network issue: Current policy leaves threat-intelligence action in alert-only mode. Select threat-intelligence Deny for the approved blocking posture.
D:
“Use a DNAT rule translating intended firewall public destination to private host/port” concerns Inbound packets arrive at Azure Firewall public IP but have no translation, not the actual network issue: Current policy leaves threat-intelligence action in alert-only mode. Select threat-intelligence Deny for the approved blocking posture.
Question 242
At Cedar Ridge Health, security needs deeper inspection for selected outbound encrypted web traffic. The approved change is intended to address: Standard network-rule matching cannot inspect HTTPS content. Which configuration action best implements the solution?
- Create allow for the intended source/port before default DenyAllInBound
- Configure Premium TLS inspection policy and deploy trusted inspection CA to clients
- Associate eligible NICs to ASGs and reference them in the NSG rule
- Create a network rule for the approved private destination and TCP 1433
Explanation
Correct Answer
B:
Standard network-rule matching cannot inspect HTTPS content. Configure Premium TLS inspection policy and deploy trusted inspection CA to clients.
Incorrect Answers
A:
“Create allow for the intended source/port before default DenyAllInBound” concerns A proposal removes all default deny rules rather than adding an exception, not the actual network issue: Standard network-rule matching cannot inspect HTTPS content. Configure Premium TLS inspection policy and deploy trusted inspection CA to clients.
C:
“Associate eligible NICs to ASGs and reference them in the NSG rule” concerns Source IP-based NSG rules are brittle as instances scale, not the actual network issue: Standard network-rule matching cannot inspect HTTPS content. Configure Premium TLS inspection policy and deploy trusted inspection CA to clients.
D:
“Create a network rule for the approved private destination and TCP 1433” concerns Using an HTTP application rule cannot match this raw TCP database flow, not the actual network issue: Standard network-rule matching cannot inspect HTTPS content. Configure Premium TLS inspection policy and deploy trusted inspection CA to clients.
Question 243
At Meridian Media, an enterprise requires centralized traffic inspection in a Virtual WAN hub. The design must resolve this constraint: VNet connections can currently route around the intended inspection point. Which architecture or control choice most directly meets that requirement?
- Plan route-table association and propagation so branch connections learn authorized spoke prefixes
- Use ExpressRoute Azure private peering with an ExpressRoute gateway for connected VNets
- Use a secured Virtual WAN hub with Azure Firewall and appropriate routing intent
- Choose Microsoft peering where the desired supported Microsoft public service requires it
Explanation
Correct Answer
C:
Use a secured Virtual WAN hub with Azure Firewall and appropriate routing intent. A secured Virtual WAN hub does not ensure inspection unless routing intent and the relevant associations direct flows through the hub firewall rather than bypass routes.
Incorrect Answers
A:
“Plan route-table association and propagation so branch connections learn authorized spoke prefixes” concerns Spoke address prefixes are not propagated into the branch's associated route table, not the actual network issue: VNet connections can currently route around the intended inspection point. Use a secured Virtual WAN hub with Azure Firewall and appropriate routing intent. A secured Virtual WAN hub does not ensure inspection unless routing intent and the relevant associations direct flows through the hub firewall rather than bypass routes.
B:
“Use ExpressRoute Azure private peering with an ExpressRoute gateway for connected VNets” concerns The planned circuit has no private peering for VNet prefixes, not the actual network issue: VNet connections can currently route around the intended inspection point. Use a secured Virtual WAN hub with Azure Firewall and appropriate routing intent. A secured Virtual WAN hub does not ensure inspection unless routing intent and the relevant associations direct flows through the hub firewall rather than bypass routes.
D:
“Choose Microsoft peering where the desired supported Microsoft public service requires it” concerns Engineers assume Azure private peering automatically covers all Microsoft public endpoints, not the actual network issue: VNet connections can currently route around the intended inspection point. Use a secured Virtual WAN hub with Azure Firewall and appropriate routing intent. A secured Virtual WAN hub does not ensure inspection unless routing intent and the relevant associations direct flows through the hub firewall rather than bypass routes.
Question 244
At Winterfield Group, a newly deployed VM reaches the VNet but not a connected branch prefix. The approved change is intended to address: The branch route may be overridden by a UDR or missing BGP propagation. Which configuration action best implements the solution?
- Complete the supported Custom IP Prefix validation and provisioning workflow
- Correct the relevant UDR or advertised route identified by the next-hop result
- Set Allow gateway transit on hub peering and Use remote gateways on spoke peering
- Correct the route table or gateway propagation configuration matching observed missing prefix
Explanation
Correct Answer
D:
The branch route may be overridden by a UDR or missing BGP propagation. Correct the route table or gateway propagation configuration matching observed missing prefix.
Incorrect Answers
A:
“Complete the supported Custom IP Prefix validation and provisioning workflow” concerns Its registered public address allocation is not yet onboarded to Azure, not the actual network issue: The branch route may be overridden by a UDR or missing BGP propagation. Correct the route table or gateway propagation configuration matching observed missing prefix.
B:
“Correct the relevant UDR or advertised route identified by the next-hop result” concerns The active next hop is uncertain after route table changes, not the actual network issue: The branch route may be overridden by a UDR or missing BGP propagation. Correct the route table or gateway propagation configuration matching observed missing prefix.
C:
“Set Allow gateway transit on hub peering and Use remote gateways on spoke peering” concerns The spoke can reach hub VMs but not on-premises networks, not the actual network issue: The branch route may be overridden by a UDR or missing BGP propagation. Correct the route table or gateway propagation configuration matching observed missing prefix.
Question 245
At Clearwater Civic, a compliance team needs link-layer encryption on an ExpressRoute Direct physical connection. The approved change is intended to address: The current direct port link is not configured for MACsec. Which configuration action best implements the solution?
- Configure MACsec settings and shared connectivity association credentials on supported ports
- Enable FastPath on a supported ExpressRoute connection after validating limits
- Provision the hub ExpressRoute gateway and create the circuit connection
- Create reciprocal VNet-to-VNet gateway connections and matching shared keys
Explanation
Correct Answer
A:
The current direct port link is not configured for MACsec. Configure MACsec settings and shared connectivity association credentials on supported ports.
Incorrect Answers
B:
“Enable FastPath on a supported ExpressRoute connection after validating limits” concerns The proposed gateway-only data path adds a throughput constraint, not the actual network issue: The current direct port link is not configured for MACsec. Configure MACsec settings and shared connectivity association credentials on supported ports.
C:
“Provision the hub ExpressRoute gateway and create the circuit connection” concerns The ExpressRoute circuit is active but not attached to the virtual hub, not the actual network issue: The current direct port link is not configured for MACsec. Configure MACsec settings and shared connectivity association credentials on supported ports.
D:
“Create reciprocal VNet-to-VNet gateway connections and matching shared keys” concerns The proposal relies only on creating VPN gateways without connecting them, not the actual network issue: The current direct port link is not configured for MACsec. Configure MACsec settings and shared connectivity association credentials on supported ports.
Question 246
At Horizon Education, a regulated organization must announce its own public IPv4 block through Azure. The networking change intended to correct this problem has been applied: Its registered public address allocation is not yet onboarded to Azure. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm a supported VM record appears after VM creation and tracks the private IP
- Confirm approved owned ranges are provisioned and Azure public IPs derive from that prefix
- Test application access over IPv4 and IPv6 separately
- Confirm on-premises prefixes appear and traffic flows via the hub gateway
Explanation
Correct Answer
B:
Its registered public address allocation is not yet onboarded to Azure. Confirm approved owned ranges are provisioned and Azure public IPs derive from that prefix.
Incorrect Answers
A:
“Confirm a supported VM record appears after VM creation and tracks the private IP” concerns VM addresses change but the zone only has manually entered records, not the actual network issue: Its registered public address allocation is not yet onboarded to Azure. Confirm approved owned ranges are provisioned and Azure public IPs derive from that prefix.
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: Its registered public address allocation is not yet onboarded to Azure. Confirm approved owned ranges are provisioned and Azure public IPs derive from that prefix.
D:
“Confirm on-premises prefixes appear and traffic flows via the hub gateway” concerns The spoke can reach hub VMs but not on-premises networks, not the actual network issue: Its registered public address allocation is not yet onboarded to Azure. Confirm approved owned ranges are provisioned and Azure public IPs derive from that prefix.
Question 247
At Bluebell Insurance, finance and test workloads share one subnet, but only finance should have storage account VNet access. The approved change is intended to address: The current storage VNet rule grants access to the entire shared subnet. Which configuration action best implements the solution?
- Set subnet private endpoint network policies for required NSG support and apply least-privilege rules
- Create a private endpoint and its DNS integration when private IP reachability is mandatory
- Move approved finance workloads to the subnet and grant only that subnet in storage VNet rules
- Create approved blob private endpoint and link privatelink.blob.core.windows.net DNS zone
Explanation
Correct Answer
C:
The current storage VNet rule grants access to the entire shared subnet. Move approved finance workloads to the subnet and grant only that subnet in storage VNet rules.
Incorrect Answers
A:
“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 current storage VNet rule grants access to the entire shared subnet. Move approved finance workloads to the subnet and grant only that subnet in storage VNet rules.
B:
A private endpoint changes the access model but does not fix an existing Storage VNet rule that trusts an entire mixed finance/test subnet. Separate approved finance workloads into their own subnet and scope the account network rule to that subnet, rather than assuming a subnet rule can distinguish applications within one subnet.
D:
“Create approved blob private endpoint and link privatelink.blob.core.windows.net DNS zone” concerns The app still resolves its storage hostname to a public endpoint, not the actual network issue: The current storage VNet rule grants access to the entire shared subnet. Move approved finance workloads to the subnet and grant only that subnet in storage VNet rules.
Question 248
At Aurora Procurement, a subnet has a broad route to an NVA and a specific route for a sensitive /24. The approved change is intended to address: Traffic to the sensitive /24 unexpectedly selects a different path. Which configuration action best implements the solution?
- Complete the supported Custom IP Prefix validation and provisioning workflow
- Configure the required direct peering or hub transit routes and forwarding controls
- Adjust the targeted NSG priority/source/port rule after reviewing the matched rule
- Add a suitable specific UDR to the source subnet route table
Explanation
Correct Answer
D:
Traffic to the sensitive /24 unexpectedly selects a different path. Add a suitable specific UDR to the source subnet route table.
Incorrect Answers
A:
“Complete the supported Custom IP Prefix validation and provisioning workflow” concerns Its registered public address allocation is not yet onboarded to Azure, not the actual network issue: Traffic to the sensitive /24 unexpectedly selects a different path. Add a suitable specific UDR to the source subnet route table.
B:
“Configure the required direct peering or hub transit routes and forwarding controls” concerns Architects assumed hub peering alone permits spoke-to-spoke communication, not the actual network issue: Traffic to the sensitive /24 unexpectedly selects a different path. Add a suitable specific UDR to the source subnet route table.
C:
“Adjust the targeted NSG priority/source/port rule after reviewing the matched rule” concerns An NSG deny may be taking precedence over an allow, not the actual network issue: Traffic to the sensitive /24 unexpectedly selects a different path. Add a suitable specific UDR to the source subnet route table.
Question 249
At Millstone Gaming, an older web application depends on session persistence to the same backend instance. The team has addressed this networking issue: The current gateway sends sequential sessions to different healthy backends. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor affinity-related application errors while planning longer-term stateless design
- Monitor listener certificates and per-host error rates
- Monitor cache hit ratio and unintended caching of dynamic/private content
- Monitor endpoint health and unexpected shifts in observed DNS answers
Explanation
Correct Answer
A:
The current gateway sends sequential sessions to different healthy backends. Monitor affinity-related application errors while planning longer-term stateless design.
Incorrect Answers
B:
“Monitor listener certificates and per-host error rates” concerns Requests need routing by HTTP host name rather than port alone, not the actual network issue: The current gateway sends sequential sessions to different healthy backends. Monitor affinity-related application errors while planning longer-term stateless design.
C:
“Monitor cache hit ratio and unintended caching of dynamic/private content” concerns Every image request unnecessarily reaches the origin, not the actual network issue: The current gateway sends sequential sessions to different healthy backends. Monitor affinity-related application errors while planning longer-term stateless design.
D:
“Monitor endpoint health and unexpected shifts in observed DNS answers” concerns DNS routing should reflect configured weights rather than client source geography, not the actual network issue: The current gateway sends sequential sessions to different healthy backends. Monitor affinity-related application errors while planning longer-term stateless design.
Question 250
At Brookline Manufacturing, an external partner needs private access to a shared Azure PaaS service. The networking change intended to correct this problem has been applied: The provider requires explicit authorization for each external endpoint connection. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Connect from approved subnet and reject a nonlisted public network
- Confirm only the approved partner endpoint establishes a private connection
- Verify storage access from replacement subnet while other subnets remain blocked
- Approve a consumer endpoint and test private TCP access across provider/consumer VNets
Explanation
Correct Answer
B:
The provider requires explicit authorization for each external endpoint connection. Confirm only the approved partner endpoint establishes a private connection.
Incorrect Answers
A:
“Connect from approved subnet and reject a nonlisted public network” concerns Only a server-level IP firewall allowlist currently controls clients, not the actual network issue: The provider requires explicit authorization for each external endpoint connection. Confirm only the approved partner endpoint establishes a private connection.
C:
“Verify storage access from replacement subnet while other subnets remain blocked” concerns Connections still fail after moving the application into a replacement subnet, not the actual network issue: The provider requires explicit authorization for each external endpoint connection. Confirm only the approved partner endpoint establishes a private connection.
D:
“Approve a consumer endpoint and test private TCP access across provider/consumer VNets” concerns Other Azure customers need approved private access without public exposure, not the actual network issue: The provider requires explicit authorization for each external endpoint connection. Confirm only the approved partner endpoint establishes a private connection.