100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 450
A team is troubleshooting a circuit that is not passing traffic after handoff. The architecture uses this design: Compare provider provisioning, Azure circuit state and BGP peering diagnostics. Which configuration should the engineer apply to implement it?
- Inspect service key status and provider/peering/connection health in one workflow
- Enable gateway diagnostic categories and review connection events
- Set the RADIUS server IP/secret and ensure the gateway can reach the service
- Configure Microsoft peering BGP and route filtering as required
Explanation
Correct Answer
A:Inspect service key status and provider/peering/connection health in one workflow is the operational configuration for compare provider provisioning, azure circuit state and bgp peering diagnostics. The acceptance test is to find the exact failed stage before restarting components.
Incorrect Answers
B:Enable gateway diagnostic categories and review connection events is a concrete step for use vpn gateway diagnostic logs and tunnel metrics. Here the selected design is compare provider provisioning, azure circuit state and bgp peering diagnostics, which instead requires inspect service key status and provider/peering/connection health in one workflow.
C:Set the RADIUS server IP/secret and ensure the gateway can reach the service is a concrete step for configure radius authentication for the supported p2s gateway setup. Here the selected design is compare provider provisioning, azure circuit state and bgp peering diagnostics, which instead requires inspect service key status and provider/peering/connection health in one workflow.
D:Configure Microsoft peering BGP and route filtering as required is a concrete step for choose microsoft peering only when its supported service requirements apply. Here the selected design is compare provider provisioning, azure circuit state and bgp peering diagnostics, which instead requires inspect service key status and provider/peering/connection health in one workflow.
Question 451
A team is troubleshooting a circuit that is not passing traffic after handoff. After the team applies this change—inspect service key status and provider/peering/connection health in one workflow—which validation best proves the intended result?
- Check client assigned address against local LAN and Azure VNet prefixes
- Verify learned private prefixes on both BGP sessions
- Verify branch-to-branch and VNet reachability under intended hub routing
- Find the exact failed stage before restarting components
Explanation
Correct Answer
D:Find the exact failed stage before restarting components directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the failure lies in BGP or gateway linkage rather than circuit resource existence.
Incorrect Answers
A:Check client assigned address against local LAN and Azure VNet prefixes. This concerns p2s vpn clients receive addresses overlapping their home office lan. Instead, find the exact failed stage before restarting components.
B:Verify learned private prefixes on both BGP sessions. This concerns exchange private azure VNet routes over expressroute. Instead, find the exact failed stage before restarting components.
C:Verify branch-to-branch and VNet reachability under intended hub routing. This concerns centralized transitive connectivity among dozens of branches and azure vnets. Instead, find the exact failed stage before restarting components.
Question 452
A team is troubleshooting a circuit that is not passing traffic after handoff. During acceptance testing, circuit status is healthy but BGP peering remains Down. Which underlying configuration problem best explains the symptom?
- The failure lies in BGP or gateway linkage rather than circuit resource existence
- The required Virtual WAN VPN gateway was not deployed
- The VPN gateway scale unit count is insufficient
- The selected VPN Gateway SKU was undersized or incompatible
Explanation
Correct Answer
A:The failure lies in BGP or gateway linkage rather than circuit resource existence explains the observed failure: circuit status is healthy but BGP peering remains Down. Correct the design by using compare provider provisioning, Azure circuit state and BGP peering diagnostics, implemented through inspect service key status and provider/peering/connection health in one workflow.
Incorrect Answers
B:The required Virtual WAN VPN gateway was not deployed. This concerns an IPSEC termination point for corporate branches. Here, the failure lies in BGP or gateway linkage rather than circuit resource existence.
C:The VPN gateway scale unit count is insufficient. This concerns branch bandwidth requirements exceed the default hub vpn capacity. Here, the failure lies in BGP or gateway linkage rather than circuit resource existence.
D:The selected VPN Gateway SKU was undersized or incompatible. This concerns selecting a vpn gateway sku for expected throughput and resiliency. Here, the failure lies in BGP or gateway linkage rather than circuit resource existence.
Question 453
A service needs route advertisement changes between the datacenter and Azure VNet. Which Azure networking design most directly satisfies this requirement?
- Update customer edge BGP prefix advertisements on ExpressRoute private peering
- Advertise or configure only appropriate private destination routes
- Add an ExpressRoute gateway and circuit connection to an eligible virtual hub
- Use the supported ExpressRoute exchange-provider colocation model
Explanation
Correct Answer
A:Update customer edge BGP prefix advertisements on ExpressRoute private peering addresses the topology, access or delivery requirement in the scenario. Apply it by advertise approved CIDRs from the customer router without broad defaults; confirm by check the route table for the new prefix on the Azure side.
Incorrect Answers
B:Advertise or configure only appropriate private destination routes. This concerns sending selected Azure prefixes through the VPN while retaining direct internet access. Instead, update customer edge BGP prefix advertisements on ExpressRoute private peering.
C:Add an ExpressRoute gateway and circuit connection to an eligible virtual hub. This concerns private ExpressRoute access to its global Virtual WAN topology. Instead, update customer edge BGP prefix advertisements on ExpressRoute private peering.
D:Use the supported ExpressRoute exchange-provider colocation model. This concerns choosing the correct ExpressRoute connectivity model for a colocation facility. Instead, update customer edge BGP prefix advertisements on ExpressRoute private peering.
Question 454
A service needs route advertisement changes between the datacenter and Azure VNet. The architecture uses this design: Update customer edge BGP prefix advertisements on ExpressRoute private peering. Which configuration should the engineer apply to implement it?
- Set nonoverlapping P2S CIDRs and update/reimport affected profiles
- Enable BFD on eligible customer edge routers with compatible settings
- Advertise approved CIDRs from the customer router without broad defaults
- Configure remote public VPN endpoint and its reachable on-premises network CIDRs
Explanation
Correct Answer
C:Advertise approved CIDRs from the customer router without broad defaults is the operational configuration for update customer edge bgp prefix advertisements on expressroute private peering. The acceptance test is to check the route table for the new prefix on the Azure side.
Incorrect Answers
A:Set nonoverlapping P2S CIDRs and update/reimport affected profiles is a concrete step for allocate a distinct p2s client address pool that does not overlap remote networks. Here the selected design is update customer edge bgp prefix advertisements on expressroute private peering, which instead requires advertise approved cidrs from the customer router without broad defaults.
B:Enable BFD on eligible customer edge routers with compatible settings is a concrete step for use bidirectional forwarding detection with supported expressroute peering. Here the selected design is update customer edge bgp prefix advertisements on expressroute private peering, which instead requires advertise approved cidrs from the customer router without broad defaults.
D:Configure remote public VPN endpoint and its reachable on-premises network CIDRs is a concrete step for create a local network gateway with correct site address and prefixes. Here the selected design is update customer edge bgp prefix advertisements on expressroute private peering, which instead requires advertise approved cidrs from the customer router without broad defaults.
Question 455
A service needs route advertisement changes between the datacenter and Azure VNet. After the team applies this change—advertise approved CIDRs from the customer router without broad defaults—which validation best proves the intended result?
- Inspect BGP learned routes and test a newly advertised prefix
- Trace Azure-destined traffic and general internet traffic separately
- Check the route table for the new prefix on the Azure side
- Inspect circuit provider status and Azure private peering state
Explanation
Correct Answer
C:Check the route table for the new prefix on the Azure side directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the subnet CIDR was not advertised over private peering.
Incorrect Answers
A:Inspect BGP learned routes and test a newly advertised prefix. This concerns advertising and learn routes dynamically across a routed vpn. Instead, check the route table for the new prefix on the Azure side.
B:Trace Azure-destined traffic and general internet traffic separately. This concerns sending selected azure prefixes through the vpn while retaining direct internet access. Instead, check the route table for the new prefix on the Azure side.
D:Inspect circuit provider status and Azure private peering state. This concerns a private connectivity path from its network provider into microsoft cloud. Instead, check the route table for the new prefix on the Azure side.
Question 456
A service needs route advertisement changes between the datacenter and Azure VNet. During acceptance testing, a newly onboarded on-premises subnet never reaches Azure. Which underlying configuration problem best explains the symptom?
- Route table association or propagation policy is too broad
- VPN-client DNS configuration or private DNS forwarding is missing
- The subnet CIDR was not advertised over private peering
- The BGP peering session or route advertisement is absent
Explanation
Correct Answer
C:The subnet CIDR was not advertised over private peering explains the observed failure: a newly onboarded on-premises subnet never reaches Azure. Correct the design by using update customer edge BGP prefix advertisements on ExpressRoute private peering, implemented through advertise approved CIDRs from the customer router without broad defaults.
Incorrect Answers
A:Route table association or propagation policy is too broad. This concerns controlled inter-hub route propagation. Here, the subnet CIDR was not advertised over private peering.
B:VPN-client DNS configuration or private DNS forwarding is missing. This is relevant when an employee is connected to azure vpn but private DNS names are not resolving. Here, the subnet CIDR was not advertised over private peering.
D:The BGP peering session or route advertisement is absent. This concerns advertising and learn routes dynamically across a routed vpn. Here, the subnet CIDR was not advertised over private peering.
Question 457
An enterprise needs centralized transitive connectivity among dozens of branches and Azure VNets. Which THREE choices together identify the appropriate design, its implementation, and a direct verification test? (Choose THREE.)
- Evaluate policy-based compatibility against Azure VPN Gateway support and requirements
- Configure Microsoft peering BGP and route filtering as required
- Create a Standard Virtual WAN, virtual hub and required branch/VNet connections
- Verify branch-to-branch and VNet reachability under intended hub routing
- Use Azure Virtual WAN with a Standard virtual hub design
- Inspect Microsoft peering advertisements and permitted service reachability
Explanation
Correct Answers
C:Create a Standard Virtual WAN, virtual hub and required branch/VNet connections is the operational configuration for use azure virtual wan with a standard virtual hub design. The acceptance test is to verify branch-to-branch and VNet reachability under intended hub routing.
D:Verify branch-to-branch and VNet reachability under intended hub routing directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the Virtual WAN SKU or route tables do not permit the desired transit.
E:Use Azure Virtual WAN with a Standard virtual hub design addresses the topology, access or delivery requirement in the scenario. Apply it by create a Standard Virtual WAN, virtual hub and required branch/VNet connections; confirm by verify branch-to-branch and VNet reachability under intended hub routing.
Incorrect Answers
A:Evaluate policy-based compatibility against Azure VPN Gateway support and requirements. This concerns a legacy on-premises IPSEC device only supports policy-based traffic selectors. Instead, create a Standard Virtual WAN, virtual hub and required branch/VNet connections.
B:Configure Microsoft peering BGP and route filtering as required is a concrete step for choose microsoft peering only when its supported service requirements apply. Here the selected design is use azure virtual wan with a standard virtual hub design, which instead requires create a standard virtual wan, virtual hub and required branch/vnet connections.
F:Inspect Microsoft peering advertisements and permitted service reachability. This concerns microsoft peering to reach applicable microsoft public service prefixes. Instead, create a Standard Virtual WAN, virtual hub and required branch/VNet connections.
Question 458
An enterprise needs centralized transitive connectivity among dozens of branches and Azure VNets. The architecture uses this design: Use Azure Virtual WAN with a Standard virtual hub design. Which configuration should the engineer apply to implement it?
- Scale the ExpressRoute virtual network gateway to an eligible capacity tier
- Create a Standard Virtual WAN, virtual hub and required branch/VNet connections
- Configure Microsoft peering BGP and route filtering as required
- Set the connection's route table association and propagation labels correctly
Explanation
Correct Answer
B:Create a Standard Virtual WAN, virtual hub and required branch/VNet connections is the operational configuration for use azure virtual wan with a standard virtual hub design. The acceptance test is to verify branch-to-branch and VNet reachability under intended hub routing.
Incorrect Answers
A:Scale the ExpressRoute virtual network gateway to an eligible capacity tier is a concrete step for choose a supported larger expressroute gateway sku. Here the selected design is use azure virtual wan with a standard virtual hub design, which instead requires create a standard virtual wan, virtual hub and required branch/vnet connections.
C:Configure Microsoft peering BGP and route filtering as required is a concrete step for choose microsoft peering only when its supported service requirements apply. Here the selected design is use azure virtual wan with a standard virtual hub design, which instead requires create a standard virtual wan, virtual hub and required branch/vnet connections.
D:Set the connection's route table association and propagation labels correctly is a concrete step for review the virtual wan vnet connection association and propagation settings. Here the selected design is use azure virtual wan with a standard virtual hub design, which instead requires create a standard virtual wan, virtual hub and required branch/vnet connections.
Question 459
An enterprise needs centralized transitive connectivity among dozens of branches and Azure VNets. After the team applies this change—create a Standard Virtual WAN, virtual hub and required branch/VNet connections—which validation best proves the intended result?
- Verify branch-to-branch and VNet reachability under intended hub routing
- Inspect Microsoft peering advertisements and permitted service reachability
- Verify learned private prefixes on both BGP sessions
- Trace traffic through the NVA and verify supported hub route entries
Explanation
Correct Answer
A:Verify branch-to-branch and VNet reachability under intended hub routing directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the Virtual WAN SKU or route tables do not permit the desired transit.
Incorrect Answers
B:Inspect Microsoft peering advertisements and permitted service reachability. This concerns microsoft peering to reach applicable microsoft public service prefixes. Instead, verify branch-to-branch and VNet reachability under intended hub routing.
C:Verify learned private prefixes on both BGP sessions. This concerns exchange private azure VNet routes over expressroute. Instead, verify branch-to-branch and VNet reachability under intended hub routing.
D:Trace traffic through the NVA and verify supported hub route entries. This concerns a third-party network virtual appliance inserted into virtual wan traffic paths. Instead, verify branch-to-branch and VNet reachability under intended hub routing.
Question 460
An enterprise needs centralized transitive connectivity among dozens of branches and Azure VNets. During acceptance testing, branches reach the hub but cannot transit to other branches. Which underlying configuration problem best explains the symptom?
- The client route profile lacks the spoke destination prefix
- The required Microsoft peering or route filter is missing
- The Virtual WAN SKU or route tables do not permit the desired transit
- The return route or firewall policy is asymmetric
Explanation
Correct Answer
C:The Virtual WAN SKU or route tables do not permit the desired transit explains the observed failure: branches reach the hub but cannot transit to other branches. Correct the design by using use Azure Virtual WAN with a Standard virtual hub design, implemented through create a Standard Virtual WAN, virtual hub and required branch/VNet connections.
Incorrect Answers
A:The client route profile lacks the spoke destination prefix. This is relevant when a vpn user can reach the hub VNet but cannot access a connected spoke. Here, the Virtual WAN SKU or route tables do not permit the desired transit.
B:The required Microsoft peering or route filter is missing. This concerns microsoft peering to reach applicable microsoft public service prefixes. Here, the Virtual WAN SKU or route tables do not permit the desired transit.
D:The return route or firewall policy is asymmetric. This concerns a vpn connects but only azure-to-branch traffic succeeds, not the reverse. Here, the Virtual WAN SKU or route tables do not permit the desired transit.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests