100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 300
A branch router's public address and internal network range must be represented in Azure. During acceptance testing, the tunnel connects but on-premises subnets remain unreachable. Which underlying configuration problem best explains the symptom?
- The failure lies in BGP or gateway linkage rather than circuit resource existence
- Local network gateway address prefixes are wrong
- User VPN gateway or client authentication configuration is incomplete
- The gateway cannot reach the RADIUS endpoint or the shared secret differs
Explanation
Correct Answer
B:Local network gateway address prefixes are wrong explains the observed failure: the tunnel connects but on-premises subnets remain unreachable. Correct the design by using create a local network gateway with correct site address and prefixes, implemented through configure remote public VPN endpoint and its reachable on-premises network CIDRs.
Incorrect Answers
A:The failure lies in BGP or gateway linkage rather than circuit resource existence. This is relevant when a team is troubleshooting a circuit that is not passing traffic after handoff. Here, local network gateway address prefixes are wrong.
C:User VPN gateway or client authentication configuration is incomplete. This concerns remote employees need user vpn access through the managed global wan. Here, local network gateway address prefixes are wrong.
D:The gateway cannot reach the RADIUS endpoint or the shared secret differs. This concerns a central radius service to validate users. Here, local network gateway address prefixes are wrong.
Question 301
A corporate IPsec tunnel negotiation fails because peers support different cryptographic suites. Which Azure networking design most directly satisfies this requirement?
- Align both ends on a supported IKE/IPsec policy
- Deploy an Azure VPN Gateway with a site-to-site IPsec connection
- Add an encryption overlay where supported instead of assuming ExpressRoute is encrypted
- Select supported OpenVPN or IKEv2 according to platform and auth requirements
Explanation
Correct Answer
A:Align both ends on a supported IKE/IPsec policy addresses the topology, access or delivery requirement in the scenario. Apply it by set matching encryption, integrity, DH and PFS parameters where supported; confirm by inspect IKE negotiation diagnostics and re-establish the tunnel.
Incorrect Answers
B:Deploy an Azure VPN Gateway with a site-to-site IPsec connection. This concerns an encrypted tunnel to an Azure VNet over the public internet. Here, align both ends on a supported IKE/IPsec policy.
C:Add an encryption overlay where supported instead of assuming ExpressRoute is encrypted. This is relevant when a private circuit but also requires cryptographic encryption in transit. Here, align both ends on a supported IKE/IPsec policy.
D:Select supported OpenVPN or IKEv2 according to platform and auth requirements. This concerns using an approved tunnel protocol for mobile remote-user connectivity. Here, align both ends on a supported IKE/IPsec policy.
Question 302
A corporate IPsec tunnel negotiation fails because peers support different cryptographic suites. The architecture uses this design: Align both ends on a supported IKE/IPsec policy. Which configuration should the engineer apply to implement it?
- Add a correctly named GatewaySubnet of supported prefix size before deployment
- Set required primary/secondary peering parameters and BGP ASNs with the provider
- Deploy a supported hub-integrated NVA and configure routing intent or route tables as applicable
- Set matching encryption, integrity, DH and PFS parameters where supported
Explanation
Correct Answer
D:Set matching encryption, integrity, DH and PFS parameters where supported is the operational configuration for align both ends on a supported ike/ipsec policy. The acceptance test is to inspect IKE negotiation diagnostics and re-establish the tunnel.
Incorrect Answers
A:Add a correctly named GatewaySubnet of supported prefix size before deployment is a concrete step for create a valid dedicated gatewaysubnet inside the target vnet. Here the selected design is align both ends on a supported ike/ipsec policy, which instead requires set matching encryption, integrity, dh and pfs parameters where supported.
B:Set required primary/secondary peering parameters and BGP ASNs with the provider is a concrete step for configure azure private peering on the expressroute circuit. Here the selected design is align both ends on a supported ike/ipsec policy, which instead requires set matching encryption, integrity, dh and pfs parameters where supported.
C:Deploy a supported hub-integrated NVA and configure routing intent or route tables as applicable is a concrete step for use supported virtual wan nva integration rather than an arbitrary subnet vm route. Here the selected design is align both ends on a supported ike/ipsec policy, which instead requires set matching encryption, integrity, dh and pfs parameters where supported.
Question 303
A corporate IPsec tunnel negotiation fails because peers support different cryptographic suites. After the team applies this change—set matching encryption, integrity, DH and PFS parameters where supported—which validation best proves the intended result?
- Inspect circuit provider status and Azure private peering state
- Fail a simulated tunnel and verify a second connection still passes traffic
- Inspect IKE negotiation diagnostics and re-establish the tunnel
- Inspect circuit-to-gateway connection status and test private IP access
Explanation
Correct Answer
C:Inspect IKE negotiation diagnostics and re-establish the tunnel directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether iPsec security association parameters differ between peers.
Incorrect Answers
A:Inspect circuit provider status and Azure private peering state. This concerns a private connectivity path from its network provider into microsoft cloud. Instead, inspect IKE negotiation diagnostics and re-establish the tunnel.
B:Fail a simulated tunnel and verify a second connection still passes traffic. This concerns two branch vpn devices should both be able to provide resilient connectivity to azure. Instead, inspect IKE negotiation diagnostics and re-establish the tunnel.
D:Inspect circuit-to-gateway connection status and test private IP access. This concerns its VNet connected to an existing private expressroute circuit. Instead, inspect IKE negotiation diagnostics and re-establish the tunnel.
Question 304
A corporate IPsec tunnel negotiation fails because peers support different cryptographic suites. During acceptance testing, iKE authentication succeeds but CHILD_SA negotiation fails. Which underlying configuration problem best explains the symptom?
- The secured hub internet routing intent or association is missing
- Route table association or propagation policy is too broad
- The hub NVA integration or routing intent is not configured
- IPsec security association parameters differ between peers
Explanation
Correct Answer
D:IPsec security association parameters differ between peers explains the observed failure: iKE authentication succeeds but CHILD_SA negotiation fails. Correct the design by using align both ends on a supported IKE/IPsec policy, implemented through set matching encryption, integrity, DH and PFS parameters where supported.
Incorrect Answers
A:The secured hub internet routing intent or association is missing. This concerns secure inspection for all virtual wan internet and private paths. Here, iPsec security association parameters differ between peers.
B:Route table association or propagation policy is too broad. This concerns controlled inter-hub route propagation. Here, iPsec security association parameters differ between peers.
C:The hub NVA integration or routing intent is not configured. This concerns a third-party network virtual appliance inserted into virtual wan traffic paths. Here, iPsec security association parameters differ between peers.
Question 305
A hybrid connection must advertise and learn routes dynamically across a routed VPN. Which Azure networking design most directly satisfies this requirement?
- Enable BGP with supported gateway and customer edge configuration
- Select appropriate Virtual WAN VPN gateway scale units
- Update the corresponding local network gateway public IP endpoint
- Revoke the contractor certificate using the supported VPN certificate revocation process
Explanation
Correct Answer
A:Enable BGP with supported gateway and customer edge configuration addresses the topology, access or delivery requirement in the scenario. Apply it by configure peer ASN/BGP addresses and BGP on the connection; confirm by inspect BGP learned routes and test a newly advertised prefix.
Incorrect Answers
B:Select appropriate Virtual WAN VPN gateway scale units. This concerns branch bandwidth requirements exceed the default hub VPN capacity. Instead, enable BGP with supported gateway and customer edge configuration.
C:Update the corresponding local network gateway public IP endpoint. This is relevant when a company is moving its site-to-site tunnel to a different on-premises public address. Instead, enable BGP with supported gateway and customer edge configuration.
D:Revoke the contractor certificate using the supported VPN certificate revocation process. This concerns revoking one contractor. Instead, enable BGP with supported gateway and customer edge configuration.
Question 306
A hybrid connection must advertise and learn routes dynamically across a routed VPN. The architecture uses this design: Enable BGP with supported gateway and customer edge configuration. Which configuration should the engineer apply to implement it?
- Configure peer ASN/BGP addresses and BGP on the connection
- Associate each connection with the appropriate route table and set propagation destinations
- Configure a compatible VPN client profile and required device or user tunnel policy
- Configure independent local network gateways/connections for both provider paths
Explanation
Correct Answer
A:Configure peer ASN/BGP addresses and BGP on the connection is the operational configuration for enable bgp with supported gateway and customer edge configuration. The acceptance test is to inspect BGP learned routes and test a newly advertised prefix.
Incorrect Answers
B:Associate each connection with the appropriate route table and set propagation destinations is a concrete step for configure virtual hub route tables, labels and propagations. Here the selected design is enable bgp with supported gateway and customer edge configuration, which instead requires configure peer asn/bgp addresses and bgp on the connection.
C:Configure a compatible VPN client profile and required device or user tunnel policy is a concrete step for evaluate azure p2s settings against windows always on vpn prerequisites. Here the selected design is enable bgp with supported gateway and customer edge configuration, which instead requires configure peer asn/bgp addresses and bgp on the connection.
D:Configure independent local network gateways/connections for both provider paths is a concrete step for use redundant site-to-site vpn connections over separate isp endpoints. Here the selected design is enable bgp with supported gateway and customer edge configuration, which instead requires configure peer asn/bgp addresses and bgp on the connection.
Question 307
A hybrid connection must advertise and learn routes dynamically across a routed VPN. After the team applies this change—configure peer ASN/BGP addresses and BGP on the connection—which validation best proves the intended result?
- Inspect BGP learned routes and test a newly advertised prefix
- Inspect negotiated selectors and confirm required prefixes pass
- Inspect FastPath configuration and measure the supported VM data path
- Inspect Microsoft peering advertisements and permitted service reachability
Explanation
Correct Answer
A:Inspect BGP learned routes and test a newly advertised prefix directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the BGP peering session or route advertisement is absent.
Incorrect Answers
B:Inspect negotiated selectors and confirm required prefixes pass. This concerns a legacy on-premises IPSEC device only supports policy-based traffic selectors. Instead, inspect BGP learned routes and test a newly advertised prefix.
C:Inspect FastPath configuration and measure the supported VM data path. This concerns an azure VNet gateway that sends applicable traffic directly over the expressroute data path for better throughput. Instead, inspect BGP learned routes and test a newly advertised prefix.
D:Inspect Microsoft peering advertisements and permitted service reachability. This concerns microsoft peering to reach applicable microsoft public service prefixes. Instead, inspect BGP learned routes and test a newly advertised prefix.
Question 308
A hybrid connection must advertise and learn routes dynamically across a routed VPN. During acceptance testing, the tunnel is up but new routes never appear. Which underlying configuration problem best explains the symptom?
- The BGP peering session or route advertisement is absent
- The client route profile lacks the spoke destination prefix
- The subnet CIDR was not advertised over private peering
- Route table association or propagation policy is too broad
Explanation
Correct Answer
A:The BGP peering session or route advertisement is absent explains the observed failure: the tunnel is up but new routes never appear. Correct the design by using enable BGP with supported gateway and customer edge configuration, implemented through configure peer ASN/BGP addresses and BGP on the connection.
Incorrect Answers
B: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 BGP peering session or route advertisement is absent.
C:The subnet CIDR was not advertised over private peering. This concerns routing advertisement changes between the datacenter and azure VNet. Here, the BGP peering session or route advertisement is absent.
D:Route table association or propagation policy is too broad. This concerns controlled inter-hub route propagation. Here, the BGP peering session or route advertisement is absent.
Question 309
A VPN Gateway is provisioned but its resource cannot be placed in the intended VNet. Which Azure networking design most directly satisfies this requirement?
- Create a local network gateway with correct site address and prefixes
- Review the Virtual WAN VNet connection association and propagation settings
- Evaluate ExpressRoute Direct for dedicated physical ports
- Create a valid dedicated GatewaySubnet inside the target VNet
Explanation
Correct Answer
D:Create a valid dedicated GatewaySubnet inside the target VNet addresses the topology, access or delivery requirement in the scenario. Apply it by add a correctly named GatewaySubnet of supported prefix size before deployment; confirm by confirm gateway deployment completes and the correct subnet attachment is shown.
Incorrect Answers
A:Create a local network gateway with correct site address and prefixes. This concerns being represented in Azure. Instead, create a valid dedicated GatewaySubnet inside the target VNet.
B:Review the Virtual WAN VNet connection association and propagation settings. This is relevant when a virtual hub is connected to many VNets but one spoke is missing remote routes. Instead, create a valid dedicated GatewaySubnet inside the target VNet.
C:Evaluate ExpressRoute Direct for dedicated physical ports. This concerns a high-throughput dedicated connection to Microsoft without a standard provider-managed circuit. Instead, create a valid dedicated GatewaySubnet inside the target VNet.
Question 310
A VPN Gateway is provisioned but its resource cannot be placed in the intended VNet. The architecture uses this design: Create a valid dedicated GatewaySubnet inside the target VNet. Which configuration should the engineer apply to implement it?
- Set the connection's route table association and propagation labels correctly
- Use supported gateway SKU and enable FastPath on the eligible connection
- Add a correctly named GatewaySubnet of supported prefix size before deployment
- Set matching encryption, integrity, DH and PFS parameters where supported
Explanation
Correct Answer
C:Add a correctly named GatewaySubnet of supported prefix size before deployment is the operational configuration for create a valid dedicated gatewaysubnet inside the target vnet. The acceptance test is to confirm gateway deployment completes and the correct subnet attachment is shown.
Incorrect Answers
A: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 create a valid dedicated gatewaysubnet inside the target vnet, which instead requires add a correctly named gatewaysubnet of supported prefix size before deployment.
B:Use supported gateway SKU and enable FastPath on the eligible connection is a concrete step for consider expressroute fastpath on supported gateway and circuit combinations. Here the selected design is create a valid dedicated gatewaysubnet inside the target vnet, which instead requires add a correctly named gatewaysubnet of supported prefix size before deployment.
D:Set matching encryption, integrity, DH and PFS parameters where supported is a concrete step for align both ends on a supported ike/ipsec policy. Here the selected design is create a valid dedicated gatewaysubnet inside the target vnet, which instead requires add a correctly named gatewaysubnet of supported prefix size before deployment.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests