100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 20
A private endpoint will coexist with VMs but must have an address in a planned network segment. During acceptance testing, the endpoint resolves to a public address instead of a VNet IP. Which underlying configuration problem best explains the symptom?
- The private endpoint or its private DNS integration is missing
- The required UDR is missing or less specific than another route
- One direction of VNet peering or the effective network policy is missing
- Private DNS links were configured only for the first two spokes
Explanation
Correct Answer
A:The private endpoint or its private DNS integration is missing explains the observed failure: the endpoint resolves to a public address instead of a VNet IP. Correct the design by using create a suitable subnet and deploy the private endpoint NIC in it, implemented through choose a subnet in the target VNet and allocate a private endpoint there.
Incorrect Answers
B:The required UDR is missing or less specific than another route. This concerns using a specific next hop. Here, the private endpoint or its private DNS integration is missing.
C:One direction of VNet peering or the effective network policy is missing. This concerns two azure vnets in the same tenant require private low-latency connectivity without routing through the internet. Here, the private endpoint or its private DNS integration is missing.
D:Private DNS links were configured only for the first two spokes. This concerns a shared hub contains a private DNS zone but only one of three spokes resolves it. Here, the private endpoint or its private DNS integration is missing.
Question 21
A company expects several firewalls, gateways, and Bastion services to use separate platform subnets. Which Azure networking design most directly satisfies this requirement?
- Associate the route table with the VM's subnet
- Implement VNet peering with reciprocal connections
- Use a dedicated subnet delegated to the correct resource provider
- Reserve correctly named, dedicated service subnets with adequate sizes
Explanation
Correct Answer
D:Reserve correctly named, dedicated service subnets with adequate sizes addresses the topology, access or delivery requirement in the scenario. Apply it by create GatewaySubnet and AzureBastionSubnet plus separate firewall subnet as required; confirm by validate supported subnet names and minimum prefix sizing before deployment.
Incorrect Answers
A:Associate the route table with the VM's subnet. This is relevant when a route table is created but its UDRs have no effect on an application VM. Here, reserve correctly named, dedicated service subnets with adequate sizes.
B:Implement VNet peering with reciprocal connections. This concerns two Azure VNets in the same tenant require private low-latency connectivity without routing through the internet. Here, reserve correctly named, dedicated service subnets with adequate sizes.
C:Use a dedicated subnet delegated to the correct resource provider. This concerns exclusive delegation. Here, reserve correctly named, dedicated service subnets with adequate sizes.
Question 22
A company expects several firewalls, gateways, and Bastion services to use separate platform subnets. The architecture uses this design: Reserve correctly named, dedicated service subnets with adequate sizes. Which configuration should the engineer apply to implement it?
- Inspect effective rules for the VM NIC including subnet and NIC scope
- Create GatewaySubnet and AzureBastionSubnet plus separate firewall subnet as required
- Create the private zone and add a virtual network link
- Set the subnet delegation to the supported Microsoft service type
Explanation
Correct Answer
B:Create GatewaySubnet and AzureBastionSubnet plus separate firewall subnet as required is the operational configuration for reserve correctly named, dedicated service subnets with adequate sizes. The acceptance test is to validate supported subnet names and minimum prefix sizing before deployment.
Incorrect Answers
A:Inspect effective rules for the VM NIC including subnet and NIC scope is a concrete step for use network watcher effective security rules. Here the selected design is reserve correctly named, dedicated service subnets with adequate sizes, which instead requires create gatewaysubnet and azurebastionsubnet plus separate firewall subnet as required.
C:Create the private zone and add a virtual network link is a concrete step for use an azure private dns zone linked to the relevant vnet. Here the selected design is reserve correctly named, dedicated service subnets with adequate sizes, which instead requires create gatewaysubnet and azurebastionsubnet plus separate firewall subnet as required.
D:Set the subnet delegation to the supported Microsoft service type is a concrete step for use a dedicated subnet delegated to the correct resource provider. Here the selected design is reserve correctly named, dedicated service subnets with adequate sizes, which instead requires create gatewaysubnet and azurebastionsubnet plus separate firewall subnet as required.
Question 23
A company expects several firewalls, gateways, and Bastion services to use separate platform subnets. After the team applies this change—create GatewaySubnet and AzureBastionSubnet plus separate firewall subnet as required—which validation best proves the intended result?
- Validate supported subnet names and minimum prefix sizing before deployment
- Take one resolver offline and test supported fallback behavior
- Check whether all spokes learn the expected remote prefix
- Inspect subnet prefixes and provision one test NIC in each
Explanation
Correct Answer
A:Validate supported subnet names and minimum prefix sizing before deployment directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the platform subnet name or required sizing is incorrect.
Incorrect Answers
B:Take one resolver offline and test supported fallback behavior. This concerns failover if one resolver is offline. Here, validate supported subnet names and minimum prefix sizing before deployment.
C:Check whether all spokes learn the expected remote prefix. This concerns being usable by multiple spoke vnets. Here, validate supported subnet names and minimum prefix sizing before deployment.
D:Inspect subnet prefixes and provision one test NIC in each. This concerns a migration adds a second application subnet without changing the first application's private ip space. Here, validate supported subnet names and minimum prefix sizing before deployment.
Question 24
A company expects several firewalls, gateways, and Bastion services to use separate platform subnets. During acceptance testing, deployment rejects a service subnet despite free VNet address space. Which underlying configuration problem best explains the symptom?
- The required UDR is missing or less specific than another route
- The route table was never associated with the workload subnet
- The platform subnet name or required sizing is incorrect
- Outbound traffic depended on per-instance public IPs instead of subnet NAT
Explanation
Correct Answer
C:The platform subnet name or required sizing is incorrect explains the observed failure: deployment rejects a service subnet despite free VNet address space. Correct the design by using reserve correctly named, dedicated service subnets with adequate sizes, implemented through create GatewaySubnet and AzureBastionSubnet plus separate firewall subnet as required.
Incorrect Answers
A:The required UDR is missing or less specific than another route. This concerns using a specific next hop. Here, the platform subnet name or required sizing is incorrect.
B:The route table was never associated with the workload subnet. This is relevant when a route table is created but its udrs have no effect on an application vm. Here, the platform subnet name or required sizing is incorrect.
D:Outbound traffic depended on per-instance public IPs instead of subnet NAT. This concerns egress ip consistency during vm scale-in and scale-out. Here, the platform subnet name or required sizing is incorrect.
Question 25
A team must provide a contiguous block of predictable Azure public IPs for partner firewall allowlists. Which Azure networking design most directly satisfies this requirement?
- Enable and monitor Azure DDoS Protection on applicable public-IP VNets
- Add a distinct nonoverlapping subnet inside an available VNet prefix
- Allocate a Standard Public IP Prefix and draw public IPs from the prefix
- Apply longest-prefix-match when selecting the effective route
Explanation
Correct Answer
C:Allocate a Standard Public IP Prefix and draw public IPs from the prefix addresses the topology, access or delivery requirement in the scenario. Apply it by create the public IP prefix in the intended region and create addresses from it; confirm by confirm created public IP addresses belong to the allocated prefix.
Incorrect Answers
A:Enable and monitor Azure DDoS Protection on applicable public-IP VNets. This is relevant when an early warning when its Azure public endpoint is targeted by volumetric attacks. Instead, allocate a Standard Public IP Prefix and draw public IPs from the prefix.
B:Add a distinct nonoverlapping subnet inside an available VNet prefix. This concerns a migration adds a second application subnet without changing the first application's private IP space. Instead, allocate a Standard Public IP Prefix and draw public IPs from the prefix.
D:Apply longest-prefix-match when selecting the effective route. This concerns a VM has an effective UDR for a private destination and a broader BGP route for the same service. Instead, allocate a Standard Public IP Prefix and draw public IPs from the prefix.
Question 26
A team must provide a contiguous block of predictable Azure public IPs for partner firewall allowlists. The architecture uses this design: Allocate a Standard Public IP Prefix and draw public IPs from the prefix. Which configuration should the engineer apply to implement it?
- Create network groups and deploy a hub-and-spoke connectivity configuration
- Create the public IP prefix in the intended region and create addresses from it
- Set primary and secondary DNS server addresses and validate route reachability
- Remove direct VM public IP attachments and configure NAT Gateway egress
Explanation
Correct Answer
B:Create the public IP prefix in the intended region and create addresses from it is the operational configuration for allocate a standard public ip prefix and draw public ips from the prefix. The acceptance test is to confirm created public IP addresses belong to the allocated prefix.
Incorrect Answers
A:Create network groups and deploy a hub-and-spoke connectivity configuration is a concrete step for use azure virtual network manager connectivity configurations. Here the selected design is allocate a standard public ip prefix and draw public ips from the prefix, which instead requires create the public ip prefix in the intended region and create addresses from it.
C:Set primary and secondary DNS server addresses and validate route reachability is a concrete step for configure multiple reachable custom dns server ips for the vnet. Here the selected design is allocate a standard public ip prefix and draw public ips from the prefix, which instead requires create the public ip prefix in the intended region and create addresses from it.
D:Remove direct VM public IP attachments and configure NAT Gateway egress is a concrete step for avoid attaching unnecessary public ips to vm nics and use subnet nat gateway. Here the selected design is allocate a standard public ip prefix and draw public ips from the prefix, which instead requires create the public ip prefix in the intended region and create addresses from it.
Question 27
A team must provide a contiguous block of predictable Azure public IPs for partner firewall allowlists. After the team applies this change—create the public IP prefix in the intended region and create addresses from it—which validation best proves the intended result?
- Query the public TXT record and compare the expected verification token
- Check whether all spokes learn the expected remote prefix
- Confirm created public IP addresses belong to the allocated prefix
- Verify the VM has no public NIC IP but can reach approved external targets
Explanation
Correct Answer
C:Confirm created public IP addresses belong to the allocated prefix directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether public IP resources were not allocated from the reserved prefix.
Incorrect Answers
A:Query the public TXT record and compare the expected verification token. This concerns external consumers to discover its public verification token. Instead, confirm created public IP addresses belong to the allocated prefix.
B:Check whether all spokes learn the expected remote prefix. This concerns being usable by multiple spoke vnets. Instead, confirm created public IP addresses belong to the allocated prefix.
D:Verify the VM has no public NIC IP but can reach approved external targets. This concerns private vm interfaces but only a central nat resource exposed to the internet. Instead, confirm created public IP addresses belong to the allocated prefix.
Question 28
A team must provide a contiguous block of predictable Azure public IPs for partner firewall allowlists. During acceptance testing, a partner sees changing source addresses outside its expected block. Which underlying configuration problem best explains the symptom?
- Private DNS links were configured only for the first two spokes
- Public IP resources were not allocated from the reserved prefix
- The assumed route choice ignores the more-specific prefix
- Outbound traffic depended on per-instance public IPs instead of subnet NAT
Explanation
Correct Answer
B:Public IP resources were not allocated from the reserved prefix explains the observed failure: a partner sees changing source addresses outside its expected block. Correct the design by using allocate a Standard Public IP Prefix and draw public IPs from the prefix, implemented through create the public IP prefix in the intended region and create addresses from it.
Incorrect Answers
A:Private DNS links were configured only for the first two spokes. This concerns a shared hub contains a private DNS zone but only one of three spokes resolves it. Here, public IP resources were not allocated from the reserved prefix.
C:The assumed route choice ignores the more-specific prefix. This concerns a vm has an effective udr for a private destination and a broader BGP route for the same service. Here, public IP resources were not allocated from the reserved prefix.
D:Outbound traffic depended on per-instance public IPs instead of subnet NAT. This concerns egress ip consistency during vm scale-in and scale-out. Here, public IP resources were not allocated from the reserved prefix.
Question 29
A company owns a routable public prefix and wants to use its own address range in Azure. Which Azure networking design most directly satisfies this requirement?
- Use Azure Custom IP Prefix with proof of address ownership
- Configure supported Azure public DNS A/alias and www record mappings
- Forward Azure private DNS requests to an Azure DNS Private Resolver inbound endpoint
- Use a static Standard SKU public IP with the public load balancer frontend
Explanation
Correct Answer
A:Use Azure Custom IP Prefix with proof of address ownership addresses the topology, access or delivery requirement in the scenario. Apply it by onboard the BYOIP prefix, complete validation and provision public IP prefix resources; confirm by inspect prefix provisioning status and test external routing of an assigned address.
Incorrect Answers
B:Configure supported Azure public DNS A/alias and www record mappings. This concerns being reachable at both apex and www with proper public DNS. Instead, use Azure Custom IP Prefix with proof of address ownership.
C:Forward Azure private DNS requests to an Azure DNS Private Resolver inbound endpoint. This concerns resolving Azure Private DNS records without manually creating duplicates. Instead, use Azure Custom IP Prefix with proof of address ownership.
D:Use a static Standard SKU public IP with the public load balancer frontend. This concerns a persistent internet-facing endpoint rather than a VM-level ephemeral address. Instead, use Azure Custom IP Prefix with proof of address ownership.
Question 30
A company owns a routable public prefix and wants to use its own address range in Azure. The architecture uses this design: Use Azure Custom IP Prefix with proof of address ownership. Which configuration should the engineer apply to implement it?
- Create an Azure public DNS TXT record set containing the token string
- Compare specific UDR and learned BGP prefix lengths on the NIC
- Remove direct VM public IP attachments and configure NAT Gateway egress
- Onboard the BYOIP prefix, complete validation and provision public IP prefix resources
Explanation
Correct Answer
D:Onboard the BYOIP prefix, complete validation and provision public IP prefix resources is the operational configuration for use azure custom ip prefix with proof of address ownership. The acceptance test is to inspect prefix provisioning status and test external routing of an assigned address.
Incorrect Answers
A:Create an Azure public DNS TXT record set containing the token string is a concrete step for publish a txt record at the provider-required dns name. Here the selected design is use azure custom ip prefix with proof of address ownership, which instead requires onboard the byoip prefix, complete validation and provision public ip prefix resources.
B:Compare specific UDR and learned BGP prefix lengths on the NIC is a concrete step for apply longest-prefix-match when selecting the effective route. Here the selected design is use azure custom ip prefix with proof of address ownership, which instead requires onboard the byoip prefix, complete validation and provision public ip prefix resources.
C:Remove direct VM public IP attachments and configure NAT Gateway egress is a concrete step for avoid attaching unnecessary public ips to vm nics and use subnet nat gateway. Here the selected design is use azure custom ip prefix with proof of address ownership, which instead requires onboard the byoip prefix, complete validation and provision public ip prefix resources.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests