Microsoft AZ-700 Practice Test 17
Question 160
At Westwind Medical, a VM NIC and its subnet each have NSGs. The networking change intended to correct this problem has been applied: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm app connectivity to platform endpoint without broad internet allow
- Test against a controlled indicator procedure and verify block event is logged
- Send a controlled rule-triggering test request and confirm it is logged rather than blocked
- Verify the required tuple is allowed by both subnet and NIC NSGs
Explanation
Correct Answer
D:
An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Verify the required tuple is allowed by both subnet and NIC NSGs.
Incorrect Answers
A:
“Confirm app connectivity to platform endpoint without broad internet allow” concerns Manually copied internet address lists are fragile, not the actual network issue: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Verify the required tuple is allowed by both subnet and NIC NSGs.
B:
“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: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Verify the required tuple is allowed by both subnet and NIC NSGs.
C:
“Send a controlled rule-triggering test request and confirm it is logged rather than blocked” concerns The application team has not assessed managed-rule matches, not the actual network issue: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Verify the required tuple is allowed by both subnet and NIC NSGs.
Question 161
At Meridian Media, hub workloads need to preserve source private IP toward an on-premises inspection appliance. The approved change is intended to address: Firewall unexpectedly translates flows because destination was treated as public. Which configuration action best implements the solution?
- Add required private destination prefixes to the Firewall Policy private IP ranges
- Add RDP/SSH allowances from the Bastion subnet to appropriate target VM subnet/NIC
- Create and associate subnet route table with firewall next hop
- Configure a precise exclusion for the verified parameter/rule and keep other rules enabled
Explanation
Correct Answer
A:
Firewall unexpectedly translates flows because destination was treated as public. Add required private destination prefixes to the Firewall Policy private IP ranges.
Incorrect Answers
B:
“Add RDP/SSH allowances from the Bastion subnet to appropriate target VM subnet/NIC” concerns The target VM NSG blocks traffic from AzureBastionSubnet, not the actual network issue: Firewall unexpectedly translates flows because destination was treated as public. Add required private destination prefixes to the Firewall Policy private IP ranges.
C:
“Create and associate subnet route table with firewall next hop” concerns Subnet effective route still uses Internet next hop, not the actual network issue: Firewall unexpectedly translates flows because destination was treated as public. Add required private destination prefixes to the Firewall Policy private IP ranges.
D:
“Configure a precise exclusion for the verified parameter/rule and keep other rules enabled” concerns Developers want to disable the entire WAF policy to restore service, not the actual network issue: Firewall unexpectedly translates flows because destination was treated as public. Add required private destination prefixes to the Firewall Policy private IP ranges.
Question 162
At Highland Research, a public service experiences bursts of volumetric traffic and needs DDoS visibility. The networking change intended to correct this problem has been applied: The team has no clear mitigation telemetry for protected public IP resources. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Resolve the root hostname and confirm it follows the current target IP
- Confirm DDoS metrics and mitigation indicators are visible during approved testing
- Confirm a supported VM record appears after VM creation and tracks the private IP
- Verify resolved findings no longer appear after assessment refresh
Explanation
Correct Answer
B:
Confirm DDoS metrics and mitigation indicators are visible during approved testing. DDoS protection coverage and Azure DDoS mitigation metrics must be checked on the protected resources. Enabling a plan alone does not establish ongoing evidence that mitigation is working.
Incorrect Answers
A:
“Resolve the root hostname and confirm it follows the current target IP” concerns A conventional CNAME cannot be used at the zone apex, not the actual network issue: The team has no clear mitigation telemetry for protected public IP resources. Confirm DDoS metrics and mitigation indicators are visible during approved testing. DDoS protection coverage and Azure DDoS mitigation metrics must be checked on the protected resources. Enabling a plan alone does not establish ongoing evidence that mitigation is working.
C:
“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: The team has no clear mitigation telemetry for protected public IP resources. Confirm DDoS metrics and mitigation indicators are visible during approved testing. DDoS protection coverage and Azure DDoS mitigation metrics must be checked on the protected resources. Enabling a plan alone does not establish ongoing evidence that mitigation is working.
D:
“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 team has no clear mitigation telemetry for protected public IP resources. Confirm DDoS metrics and mitigation indicators are visible during approved testing. DDoS protection coverage and Azure DDoS mitigation metrics must be checked on the protected resources. Enabling a plan alone does not establish ongoing evidence that mitigation is working.
Question 163
At Oakbridge Logistics, two branch classes require distinct routes into shared workloads. The networking change intended to correct this problem has been applied: All connections propagate into the same hub routing table unintentionally. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm campus-to-campus traffic follows the Global Reach connection
- Verify private branch-to-VNet addresses are learned and reachable
- Verify the expected branch prefixes are learned by only authorized connections
- Confirm requested branch and circuit connection types are configurable
Explanation
Correct Answer
C:
All connections propagate into the same hub routing table unintentionally. Verify the expected branch prefixes are learned by only authorized connections.
Incorrect Answers
A:
“Confirm campus-to-campus traffic follows the Global Reach connection” concerns The campuses need direct private WAN transit through the Microsoft backbone, not the actual network issue: All connections propagate into the same hub routing table unintentionally. Verify the expected branch prefixes are learned by only authorized connections.
B:
“Verify private branch-to-VNet addresses are learned and reachable” concerns The planned circuit has no private peering for VNet prefixes, not the actual network issue: All connections propagate into the same hub routing table unintentionally. Verify the expected branch prefixes are learned by only authorized connections.
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: All connections propagate into the same hub routing table unintentionally. Verify the expected branch prefixes are learned by only authorized connections.
Question 164
At Lakeside Technology, remote users must reach Azure private subnets while keeping ordinary internet traffic local. The design must resolve this constraint: The client profile is missing a route to a connected VNet prefix. Which architecture or control choice most directly meets that requirement?
- Use a secured Virtual WAN hub with Azure Firewall and appropriate routing intent
- Select OpenVPN-based point-to-site access with supported Microsoft Entra ID authentication
- Use MACsec for supported link-layer encryption on ExpressRoute Direct ports
- Use intended split-tunnel routes for authorized Azure address prefixes
Explanation
Correct Answer
D:
The client profile is missing a route to a connected VNet prefix. Use intended split-tunnel routes for authorized Azure address prefixes.
Incorrect Answers
A:
“Use a secured Virtual WAN hub with Azure Firewall and appropriate routing intent” concerns VNet connections can currently route around the intended inspection point, not the actual network issue: The client profile is missing a route to a connected VNet prefix. Use intended split-tunnel routes for authorized Azure address prefixes.
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 client profile is missing a route to a connected VNet prefix. Use intended split-tunnel routes for authorized Azure address prefixes.
C:
“Use MACsec for supported link-layer encryption on ExpressRoute Direct ports” concerns The current direct port link is not configured for MACsec, not the actual network issue: The client profile is missing a route to a connected VNet prefix. Use intended split-tunnel routes for authorized Azure address prefixes.
Question 165
At Aspen Ridge Software, a small engineering team needs certificate-authenticated point-to-site access. The approved change is intended to address: Client certificates have not been tied to a trusted root on the gateway. Which configuration action best implements the solution?
- Upload trusted root public certificate to gateway and install valid client certificates
- Connect redundant circuits and advertise routes with appropriate preference
- Upgrade the circuit to Premium and authorize eligible VNet connections
- Set RADIUS server IP and shared secret and select compatible P2S tunnel settings
Explanation
Correct Answer
A:
Client certificates have not been tied to a trusted root on the gateway. Upload trusted root public certificate to gateway and install valid client certificates.
Incorrect Answers
B:
“Connect redundant circuits and advertise routes with appropriate preference” concerns All traffic currently depends on one circuit at one peering location, not the actual network issue: Client certificates have not been tied to a trusted root on the gateway. Upload trusted root public certificate to gateway and install valid client certificates.
C:
“Upgrade the circuit to Premium and authorize eligible VNet connections” concerns Current circuit tier limits required VNet cross-region reach, not the actual network issue: Client certificates have not been tied to a trusted root on the gateway. Upload trusted root public certificate to gateway and install valid client certificates.
D:
“Set RADIUS server IP and shared secret and select compatible P2S tunnel settings” concerns The team cannot migrate sign-in to Microsoft Entra ID for this rollout, not the actual network issue: Client certificates have not been tied to a trusted root on the gateway. Upload trusted root public certificate to gateway and install valid client certificates.
Question 166
At Falcon Works, an internet-facing Front Door must reach an Azure-hosted origin without exposing its public listener. The design must resolve this constraint: Origin public network access is prohibited by the security team. Which architecture or control choice most directly meets that requirement?
- Choose a Standard internal Azure Load Balancer for regional private Layer 4 distribution
- Use Front Door Premium with supported Private Link private origin connectivity
- Use a validated Front Door custom domain with managed HTTPS certificate when supported
- Use Gateway Load Balancer to chain a scalable network virtual appliance service
Explanation
Correct Answer
B:
Use Front Door Premium with supported Private Link private origin connectivity. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
Incorrect Answers
A:
“Choose a Standard internal Azure Load Balancer for regional private Layer 4 distribution” concerns Clients should not receive a public load-balancer address, not the actual network issue: Origin public network access is prohibited by the security team. Use Front Door Premium with supported Private Link private origin connectivity. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
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: Origin public network access is prohibited by the security team. Use Front Door Premium with supported Private Link private origin connectivity. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
D:
“Use Gateway Load Balancer to chain a scalable network virtual appliance service” concerns The current public frontend does not route traffic through inspection appliances, not the actual network issue: Origin public network access is prohibited by the security team. Use Front Door Premium with supported Private Link private origin connectivity. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
Question 167
At Marbleview Design, a hub hosts two routing NVAs whose remote prefixes change frequently. The team has addressed this networking issue: Manual static routes to changing remote networks go stale. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor denied flows and effective security rule changes
- Detect unauthorized resource placements in the gateway subnet
- Monitor BGP peer state and unexpected prefix changes
- Alert on direct Internet default routes and loss of the firewall egress path
Explanation
Correct Answer
C:
Manual static routes to changing remote networks go stale. Monitor BGP peer state and unexpected prefix changes.
Incorrect Answers
A:
“Monitor denied flows and effective security rule changes” concerns An NSG deny may be taking precedence over an allow, not the actual network issue: Manual static routes to changing remote networks go stale. Monitor BGP peer state and unexpected prefix changes.
B:
“Detect unauthorized resource placements in the gateway subnet” concerns The proposed Application Gateway subnet already hosts unrelated virtual machines, not the actual network issue: Manual static routes to changing remote networks go stale. Monitor BGP peer state and unexpected prefix changes.
D:
“Alert on direct Internet default routes and loss of the firewall egress path” concerns An existing route table sends 0.0.0.0/0 to Internet, not the actual network issue: Manual static routes to changing remote networks go stale. Monitor BGP peer state and unexpected prefix changes.
Question 168
At Cobalt Analytics, a site-to-site VPN tunnel is up but one branch LAN is unreachable. The approved change is intended to address: The Azure local network gateway object omits a newly added on-premises prefix. Which configuration action best implements the solution?
- Configure supported policy-based traffic selectors and compatible IPsec settings where applicable
- Upload trusted root public certificate to gateway and install valid client certificates
- Configure MACsec settings and shared connectivity association credentials on supported ports
- Update the local network gateway prefix configuration and dependent connection
Explanation
Correct Answer
D:
The Azure local network gateway object omits a newly added on-premises prefix. Update the local network gateway prefix configuration and dependent connection.
Incorrect Answers
A:
“Configure supported policy-based traffic selectors and compatible IPsec settings where applicable” concerns An engineer assumed all VPN gateway setups interoperate with any remote IKE parameters, not the actual network issue: The Azure local network gateway object omits a newly added on-premises prefix. Update the local network gateway prefix configuration and dependent connection.
B:
“Upload trusted root public certificate to gateway and install valid client certificates” concerns Client certificates have not been tied to a trusted root on the gateway, not the actual network issue: The Azure local network gateway object omits a newly added on-premises prefix. Update the local network gateway prefix configuration and dependent connection.
C:
“Configure MACsec settings and shared connectivity association credentials on supported ports” concerns The current direct port link is not configured for MACsec, not the actual network issue: The Azure local network gateway object omits a newly added on-premises prefix. Update the local network gateway prefix configuration and dependent connection.
Question 169
At Westwind Medical, windows-managed remote devices must connect to Azure hybrid resources with automated VPN. The team has addressed this networking issue: A standard user-launched connection workflow does not satisfy auto-connect requirements. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor automated VPN reconnect failures and gateway authentication events
- Monitor site VPN gateway throughput and scale unit saturation
- Watch port operational state and circuit bandwidth utilization
- Monitor new address allocations for future prefix overlap
Explanation
Correct Answer
A:
Monitor automated VPN reconnect failures and gateway authentication events. 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
B:
“Monitor site VPN gateway throughput and scale unit saturation” concerns Initial site-to-site VPN gateway capacity is undersized, not the actual network issue: A standard user-launched connection workflow does not satisfy auto-connect requirements. Monitor automated VPN reconnect failures and gateway authentication events. 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:
“Watch port operational state and circuit bandwidth utilization” concerns A conventional provider-hosted circuit does not meet the direct port ownership requirement, not the actual network issue: A standard user-launched connection workflow does not satisfy auto-connect requirements. Monitor automated VPN reconnect failures and gateway authentication events. 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:
“Monitor new address allocations for future prefix overlap” 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. Monitor automated VPN reconnect failures and gateway authentication events. 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 170
At Horizon Education, a newly provisioned storage account private endpoint uses a stale manually managed A record. The networking change intended to correct this problem has been applied: The endpoint IP changes after redeployment and name resolution fails. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Attempt access to allowed and disallowed Storage accounts from the subnet
- Reprovision in a test and verify DNS record tracks the endpoint private IP
- Check the endpoint NIC is reachable from authorized consumer segments
- Connect from approved subnet and reject a nonlisted public network
Explanation
Correct Answer
B:
The endpoint IP changes after redeployment and name resolution fails. Reprovision in a test and verify DNS record tracks the endpoint private IP.
Incorrect Answers
A:
“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 endpoint IP changes after redeployment and name resolution fails. Reprovision in a test and verify DNS record tracks the endpoint private IP.
C:
“Check the endpoint NIC is reachable from authorized consumer segments” concerns The consumer application network needs local private routing to the service, not the actual network issue: The endpoint IP changes after redeployment and name resolution fails. Reprovision in a test and verify DNS record tracks the endpoint private IP.
D:
“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 endpoint IP changes after redeployment and name resolution fails. Reprovision in a test and verify DNS record tracks the endpoint private IP.