100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 110
A private Key Vault endpoint is deployed but clients get an unexpected public resolution. The architecture uses this design: Bind the appropriate private DNS zone to the Key Vault Private Endpoint. Which configuration should the engineer apply to implement it?
- Create an Azure public DNS TXT record set containing the token string
- Configure VNet flow log collection to a supported storage destination
- Configure the endpoint zone group for privatelink.vaultcore.azure.net
- Associate a DDoS protection plan and configure telemetry alerts
Explanation
Correct Answer
C:Configure the endpoint zone group for privatelink.vaultcore.azure.net is the operational configuration for bind the appropriate private dns zone to the key vault private endpoint. The acceptance test is to test the Key Vault hostname from a VM linked to the relevant private zone.
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 bind the appropriate private dns zone to the key vault private endpoint, which instead requires configure the endpoint zone group for privatelink.vaultcore.azure.net.
B:Configure VNet flow log collection to a supported storage destination is a concrete step for enable virtual network flow logs on the supported network scope. Here the selected design is bind the appropriate private dns zone to the key vault private endpoint, which instead requires configure the endpoint zone group for privatelink.vaultcore.azure.net.
D:Associate a DDoS protection plan and configure telemetry alerts is a concrete step for enable and monitor azure ddos protection on applicable public-ip vnets. Here the selected design is bind the appropriate private dns zone to the key vault private endpoint, which instead requires configure the endpoint zone group for privatelink.vaultcore.azure.net.
Question 111
A private Key Vault endpoint is deployed but clients get an unexpected public resolution. After the team applies this change—configure the endpoint zone group for privatelink.vaultcore.azure.net—which validation best proves the intended result?
- Inspect the private endpoint NIC private address and approved connection
- Test the Key Vault hostname from a VM linked to the relevant private zone
- Inspect subnet prefixes and provision one test NIC in each
- Take one resolver offline and test supported fallback behavior
Explanation
Correct Answer
B:Test the Key Vault hostname from a VM linked to the relevant private zone directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the relevant privatelink zone or VNet link is absent.
Incorrect Answers
A:Inspect the private endpoint NIC private address and approved connection. This concerns having an address in a planned network segment. Instead, test the Key Vault hostname from a VM linked to the relevant private zone.
C: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. Instead, test the Key Vault hostname from a VM linked to the relevant private zone.
D:Take one resolver offline and test supported fallback behavior. This concerns failover if one resolver is offline. Instead, test the Key Vault hostname from a VM linked to the relevant private zone.
Question 112
A private Key Vault endpoint is deployed but clients get an unexpected public resolution. During acceptance testing, the hostname resolves publicly despite private network requirements. Which underlying configuration problem best explains the symptom?
- The two VNet address prefixes overlap
- The relevant privatelink zone or VNet link is absent
- The deployment scope or network group assignment excludes the VNet
- Private DNS links were configured only for the first two spokes
Explanation
Correct Answer
B:The relevant privatelink zone or VNet link is absent explains the observed failure: the hostname resolves publicly despite private network requirements. Correct the design by using bind the appropriate private DNS zone to the Key Vault Private Endpoint, implemented through configure the endpoint zone group for privatelink.vaultcore.azure.net.
Incorrect Answers
A:The two VNet address prefixes overlap. This concerns avoiding overlapping ip blocks. Here, the relevant privatelink zone or VNet link is absent.
C:The deployment scope or network group assignment excludes the VNet. This is relevant when a large region uses a central routing policy for many hub-spoke links. Here, the relevant privatelink zone or VNet link is absent.
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 relevant privatelink zone or VNet link is absent.
Question 113
A public application must direct mail to an externally hosted mail service. Which Azure networking design most directly satisfies this requirement?
- 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
- Publish the correct MX resource record in an Azure public DNS zone
- Deploy Azure Route Server and establish BGP peering with the NVA
Explanation
Correct Answer
C:Publish the correct MX resource record in an Azure public DNS zone addresses the topology, access or delivery requirement in the scenario. Apply it by create the MX record set with the provider-supplied priority and hostname; confirm by query the authoritative public zone for MX and confirm expected values.
Incorrect Answers
A: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, publish the correct MX resource record in an Azure public DNS zone.
B: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, publish the correct MX resource record in an Azure public DNS zone.
D:Deploy Azure Route Server and establish BGP peering with the NVA. This concerns Azure to learn BGP routes from an existing virtual appliance. Instead, publish the correct MX resource record in an Azure public DNS zone.
Question 114
A public application must direct mail to an externally hosted mail service. The architecture uses this design: Publish the correct MX resource record in an Azure public DNS zone. Which configuration should the engineer apply to implement it?
- Create the public IP prefix in the intended region and create addresses from it
- Create the matching private DNS zone group for the storage private endpoint
- Create the MX record set with the provider-supplied priority and hostname
- Apply an appropriate 0.0.0.0/0 UDR to the workload subnet with the inspection next hop
Explanation
Correct Answer
C:Create the MX record set with the provider-supplied priority and hostname is the operational configuration for publish the correct mx resource record in an azure public dns zone. The acceptance test is to query the authoritative public zone for MX and confirm expected values.
Incorrect Answers
A:Create the public IP prefix in the intended region and create addresses from it is a concrete step for allocate a standard public ip prefix and draw public ips from the prefix. Here the selected design is publish the correct mx resource record in an azure public dns zone, which instead requires create the mx record set with the provider-supplied priority and hostname.
B:Create the matching private DNS zone group for the storage private endpoint is a concrete step for use the recommended privatelink private dns zone for the storage subresource. Here the selected design is publish the correct mx resource record in an azure public dns zone, which instead requires create the mx record set with the provider-supplied priority and hostname.
D:Apply an appropriate 0.0.0.0/0 UDR to the workload subnet with the inspection next hop is a concrete step for configure forced tunneling through a virtual appliance or hybrid gateway. Here the selected design is publish the correct mx resource record in an azure public dns zone, which instead requires create the mx record set with the provider-supplied priority and hostname.
Question 115
A public application must direct mail to an externally hosted mail service. After the team applies this change—create the MX record set with the provider-supplied priority and hostname—which validation best proves the intended result?
- Query an Azure private hostname from a branch DNS client
- Query the authoritative public zone for MX and confirm expected values
- Query peering write operations and the caller in retained logs
- Check whether all spokes learn the expected remote prefix
Explanation
Correct Answer
B:Query the authoritative public zone for MX and confirm expected values directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the MX record set is missing or points to an obsolete exchanger.
Incorrect Answers
A:Query an Azure private hostname from a branch DNS client. This concerns resolving azure private DNS records without manually creating duplicates. Instead, query the authoritative public zone for MX and confirm expected values.
C:Query peering write operations and the caller in retained logs. This concerns tracking of VNet peering changes across subscriptions. Instead, query the authoritative public zone for MX and confirm expected values.
D:Check whether all spokes learn the expected remote prefix. This concerns being usable by multiple spoke vnets. Instead, query the authoritative public zone for MX and confirm expected values.
Question 116
A public application must direct mail to an externally hosted mail service. During acceptance testing, external mail senders cannot locate the domain's mail exchanger. Which underlying configuration problem best explains the symptom?
- One direction of VNet peering or the effective network policy is missing
- Metric alert rules or action group routing is missing
- The required UDR is missing or less specific than another route
- The MX record set is missing or points to an obsolete exchanger
Explanation
Correct Answer
D:The MX record set is missing or points to an obsolete exchanger explains the observed failure: external mail senders cannot locate the domain's mail exchanger. Correct the design by using publish the correct MX resource record in an Azure public DNS zone, implemented through create the MX record set with the provider-supplied priority and hostname.
Incorrect Answers
A: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 MX record set is missing or points to an obsolete exchanger.
B:Metric alert rules or action group routing is missing. This concerns actionable health alerts when expressroute or vpn resources degrade. Here, the MX record set is missing or points to an obsolete exchanger.
C:The required UDR is missing or less specific than another route. This concerns using a specific next hop. Here, the MX record set is missing or points to an obsolete exchanger.
Question 117
A service moving to new infrastructure must preserve a stable human-readable alias. Which Azure networking design most directly satisfies this requirement?
- Deploy a supported Azure Virtual Network Manager routing configuration
- Assign the appliance NICs to valid, segregated subnets within one VNet
- Use a CNAME record to point the alias to its current canonical hostname
- Create distinct private DNS record sets within the appropriate zone
Explanation
Correct Answer
C:Use a CNAME record to point the alias to its current canonical hostname addresses the topology, access or delivery requirement in the scenario. Apply it by create a CNAME record rather than conflicting A records at the alias name; confirm by query the alias and inspect its canonical target.
Incorrect Answers
A:Deploy a supported Azure Virtual Network Manager routing configuration. This is relevant when a large region uses a central routing policy for many hub-spoke links. Instead, use a CNAME record to point the alias to its current canonical hostname.
B:Assign the appliance NICs to valid, segregated subnets within one VNet. This concerns separating NICs for trusted and untrusted network segments. Instead, use a CNAME record to point the alias to its current canonical hostname.
D:Create distinct private DNS record sets within the appropriate zone. This concerns using separate DNS names for production and nonproduction endpoints. Instead, use a CNAME record to point the alias to its current canonical hostname.
Question 118
A service moving to new infrastructure must preserve a stable human-readable alias. The architecture uses this design: Use a CNAME record to point the alias to its current canonical hostname. Which configuration should the engineer apply to implement it?
- Create network groups and deploy a hub-and-spoke connectivity configuration
- Create a CNAME record rather than conflicting A records at the alias name
- Create the private zone and add a virtual network link
- Create the public IP prefix in the intended region and create addresses from it
Explanation
Correct Answer
B:Create a CNAME record rather than conflicting A records at the alias name is the operational configuration for use a cname record to point the alias to its current canonical hostname. The acceptance test is to query the alias and inspect its canonical target.
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 use a cname record to point the alias to its current canonical hostname, which instead requires create a cname record rather than conflicting a records at the alias name.
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 use a cname record to point the alias to its current canonical hostname, which instead requires create a cname record rather than conflicting a records at the alias name.
D:Create the public IP prefix in the intended region and create addresses from it is a concrete step for allocate a standard public ip prefix and draw public ips from the prefix. Here the selected design is use a cname record to point the alias to its current canonical hostname, which instead requires create a cname record rather than conflicting a records at the alias name.
Question 119
A service moving to new infrastructure must preserve a stable human-readable alias. After the team applies this change—create a CNAME record rather than conflicting A records at the alias name—which validation best proves the intended result?
- Inspect prefix provisioning status and test external routing of an assigned address
- Query the alias and inspect its canonical target
- Query authoritative NS records and the public A record from an external resolver
- Inspect the resulting address plan against all service subnet minimum sizes
Explanation
Correct Answer
B:Query the alias and inspect its canonical target directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the CNAME points to the previous target.
Incorrect Answers
A:Inspect prefix provisioning status and test external routing of an assigned address. This concerns using its own address range in azure. Instead, query the alias and inspect its canonical target.
C:Query authoritative NS records and the public A record from an external resolver. This concerns an organization publishes an external company domain using azure-hosted authoritative DNS. Instead, query the alias and inspect its canonical target.
D:Inspect the resulting address plan against all service subnet minimum sizes. This concerns route-aware service placement before defining the hub address blocks. Instead, query the alias and inspect its canonical target.
Question 120
A service moving to new infrastructure must preserve a stable human-readable alias. During acceptance testing, clients continue resolving the old destination from the alias. Which underlying configuration problem best explains the symptom?
- The service subnet was mixed with incompatible workloads
- Activity Log retention/export was not configured for the needed period
- The CNAME points to the previous target
- IP planning permitted duplicate prefixes across regions
Explanation
Correct Answer
C:The CNAME points to the previous target explains the observed failure: clients continue resolving the old destination from the alias. Correct the design by using use a CNAME record to point the alias to its current canonical hostname, implemented through create a CNAME record rather than conflicting A records at the alias name.
Incorrect Answers
A:The service subnet was mixed with incompatible workloads. This concerns retaining separation from general-purpose virtual machines. Here, the CNAME points to the previous target.
B:Activity Log retention/export was not configured for the needed period. This concerns tracking of VNet peering changes across subscriptions. Here, the CNAME points to the previous target.
D:IP planning permitted duplicate prefixes across regions. This concerns scale without manual ip conflicts. Here, the CNAME points to the previous target.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests