100% Latest & Updated Microsoft AZ-801 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 620
A dashboard has a green average across 50 VMs while one database VM experiences an extreme latency regression. Which configuration or recovery action best matches this evidence?
- Add a Windows event or application health alert that directly represents service termination.
- Segment performance reporting and alert on per-VM/tier distributions rather than aggregate fleet averages.
- Update the action group recipients and verify a test alert delivery.
- Reconcile alert evaluation frequency and missing-data behavior with the service recovery requirement.
Explanation
Correct Answer
B:Global averages conceal severe failures in individual business-critical assets. A suitable corrective action is to segment performance reporting and alert on per-VM/tier distributions rather than aggregate fleet averages.
Incorrect Answers
A:Compute metrics cannot reliably classify a discrete Windows service stop event. In this situation, global averages conceal severe failures in individual business-critical assets.
C:Detection without a functioning response destination fails the monitoring operational objective. Here, global averages conceal severe failures in individual business-critical assets.
D:Metric alert windows determine when a signal becomes actionable. In this situation, global averages conceal severe failures in individual business-critical assets.
Question 621
A domain member resolves a file server's old IP after a migration despite successful ICMP tests to unrelated hosts. What is the best targeted remediation for the behavior described?
- Diagnose DNS suffix, A/AAAA record and client resolver settings.
- Remove stale DNS answers or update load-balancer records and validate client caching.
- Query the relevant DNS A record and resolver cache, then correct stale name resolution.
- Set the appropriate AD-integrated DNS servers and verify required SRV lookups.
Explanation
Correct Answer
C:ICMP connectivity to other addresses does not prove the target name resolves correctly. The targeted remedy is to query the relevant DNS A record and resolver cache, then correct stale name resolution.
Incorrect Answers
A:IP connectivity with FQDN failure points to name resolution rather than necessarily a firewall port rule. However, ICMP connectivity to other addresses does not prove the target name resolves correctly.
B:Multiple records can lead requests to an unhealthy address even when one destination works. Here, ICMP connectivity to other addresses does not prove the target name resolves correctly.
D:AD clients rely on internal service locator records not generally available through public DNS. However, ICMP connectivity to other addresses does not prove the target name resolves correctly.
Question 622
An app connects to a server IP but fails using its FQDN, while TCP 443 works when the literal IP is used. Which response addresses the identified root cause without weakening other controls?
- Query the relevant DNS A record and resolver cache, then correct stale name resolution.
- Remove stale DNS answers or update load-balancer records and validate client caching.
- Test TCP port reachability and examine the service listener, guest firewall and intervening NSG.
- Diagnose DNS suffix, A/AAAA record and client resolver settings.
Explanation
Correct Answer
D:Diagnose DNS suffix, A/AAAA record and client resolver settings. This addresses the condition because iP connectivity with FQDN failure points to name resolution rather than necessarily a firewall port rule.
Incorrect Answers
A:ICMP connectivity to other addresses does not prove the target name resolves correctly. Here, IP connectivity with FQDN failure points to name resolution rather than necessarily a firewall port rule.
B:Multiple records can lead requests to an unhealthy address even when one destination works. In this situation, IP connectivity with FQDN failure points to name resolution rather than necessarily a firewall port rule.
C:ICMP success cannot establish that the application transport port is open. However, IP connectivity with FQDN failure points to name resolution rather than necessarily a firewall port rule.
Question 623
A domain user has Kerberos ticket errors and the workstation's clock differs from the DC by twenty minutes. What should the administrator change first to correct this specific issue?
- Restore accurate W32Time synchronization with the domain time hierarchy.
- Manually set the workstation clock to approximately the domain controller's time once while leaving Windows Time synchronization disabled.
- Configure the domain workstation as an independent external time authority, bypassing its domain hierarchy to avoid the current DC clock.
- Query the relevant DNS A record and resolver cache, then correct stale name resolution.
Explanation
Correct Answer
A:Kerberos authentication relies on acceptable clock skew as part of ticket validation. For that reason, restore accurate W32Time synchronization with the domain time hierarchy.
Incorrect Answers
B:A one-time clock adjustment cannot maintain the Kerberos skew boundary when the host continues drifting. W32Time must rejoin its domain time hierarchy for a reliable correction.
C:Introducing a separate workstation time authority can create a different drift path from the authoritative domain chain. The reported twenty-minute skew should be repaired through supported domain time synchronization.
D:ICMP connectivity to other addresses does not prove the target name resolves correctly. In this situation, Kerberos authentication relies on acceptable clock skew as part of ticket validation.
Question 624
A standalone Windows Server is configured to use a retired NTP peer and its time source reports 'Local CMOS Clock'. Which implementation step directly corrects the underlying problem?
- Set the standalone server to NT5DS domain-hierarchy time mode even though it is not joined to an Active Directory domain.
- Configure a reachable approved time peer and verify W32Time synchronization state.
- Validate authoritative forest time hierarchy and peer configuration using W32Time diagnostics.
- Correct the specific route/next hop and verify path tracing to the intended destination.
Explanation
Correct Answer
B:Configure a reachable approved time peer and verify W32Time synchronization state. The underlying technical reason is that local free-running clock is not equivalent to synchronized network time.
Incorrect Answers
A:NT5DS follows a domain time hierarchy that a standalone workgroup server does not possess. The replacement should configure a reachable, approved NTP peer and confirm W32Time is synchronizing with it.
C:Domain time service follows a hierarchy; a broken upstream reference propagates drift. In this situation, local free-running clock is not equivalent to synchronized network time.
D:Incorrect routing can prevent connectivity even when source/destination firewall rules allow packets. However, local free-running clock is not equivalent to synchronized network time.
Question 625
A server's route table directs a private Azure subnet through the wrong VPN gateway after a topology update. Which implementation step directly corrects the underlying problem?
- Change the target server DNS record without checking the route table or effective next hop.
- Allow the traffic in Windows Firewall while leaving the incorrect private-subnet route unchanged.
- Correct the specific route/next hop and verify path tracing to the intended destination.
- Add a new default route but keep the more-specific wrong private-subnet route at higher precedence.
Explanation
Correct Answer
C:For an incorrect private-subnet path, examine the route table, route precedence and effective next hop. Fix the specific route or gateway mapping, then validate with tracert or appropriate network-path observations.
Incorrect Answers
A:Name resolution changes cannot fix a known incorrect IP next-hop decision. The route to the private subnet still directs packets through the wrong gateway.
B:A firewall permit does not change the local routing decision. Traffic sent to the wrong VPN gateway will still follow the bad next hop.
D:Longest-prefix matching means a specific private-subnet route can override a default route. The incorrect more-specific next hop must be corrected.
Question 626
A Windows host cannot connect to TCP 1433 although DNS resolves correctly and the target IP responds to ping. Which supported action should be taken for this reported condition?
- Diagnose DNS suffix, A/AAAA record and client resolver settings.
- Query the relevant DNS A record and resolver cache, then correct stale name resolution.
- Set the appropriate AD-integrated DNS servers and verify required SRV lookups.
- Test TCP port reachability and examine the service listener, guest firewall and intervening NSG.
Explanation
Correct Answer
D:ICMP success cannot establish that the application transport port is open. The targeted remedy is to test TCP port reachability and examine the service listener, guest firewall and intervening NSG.
Incorrect Answers
A:IP connectivity with FQDN failure points to name resolution rather than necessarily a firewall port rule. In this situation, ICMP success cannot establish that the application transport port is open.
B:ICMP connectivity to other addresses does not prove the target name resolves correctly. However, ICMP success cannot establish that the application transport port is open.
C:AD clients rely on internal service locator records not generally available through public DNS. Here, ICMP success cannot establish that the application transport port is open.
Question 627
A server resolves external sites but not internal Active Directory records because its NIC uses only a public DNS resolver. What is the best targeted remediation for the behavior described?
- Set the appropriate AD-integrated DNS servers and verify required SRV lookups.
- Remove stale DNS answers or update load-balancer records and validate client caching.
- Query the relevant DNS A record and resolver cache, then correct stale name resolution.
- Test TCP port reachability and examine the service listener, guest firewall and intervening NSG.
Explanation
Correct Answer
A:Set the appropriate AD-integrated DNS servers and verify required SRV lookups. This addresses the condition because aD clients rely on internal service locator records not generally available through public DNS.
Incorrect Answers
B:Multiple records can lead requests to an unhealthy address even when one destination works. Here, AD clients rely on internal service locator records not generally available through public DNS.
C:ICMP connectivity to other addresses does not prove the target name resolves correctly. In this situation, AD clients rely on internal service locator records not generally available through public DNS.
D:ICMP success cannot establish that the application transport port is open. However, AD clients rely on internal service locator records not generally available through public DNS.
Question 628
A host loses network connectivity after teaming updates and its preferred gateway is assigned to the wrong adapter. Which supported action should be taken for this reported condition?
- Correct the specific route/next hop and verify path tracing to the intended destination.
- Inspect adapter addresses, route metrics and default gateway ownership.
- Test TCP port reachability and examine the service listener, guest firewall and intervening NSG.
- Query the relevant DNS A record and resolver cache, then correct stale name resolution.
Explanation
Correct Answer
B:Multiple competing gateways can send traffic to the wrong network even with healthy link state. For that reason, inspect adapter addresses, route metrics and default gateway ownership.
Incorrect Answers
A:Incorrect routing can prevent connectivity even when source/destination firewall rules allow packets. Here, multiple competing gateways can send traffic to the wrong network even with healthy link state.
C:ICMP success cannot establish that the application transport port is open. However, multiple competing gateways can send traffic to the wrong network even with healthy link state.
D:ICMP connectivity to other addresses does not prove the target name resolves correctly. Here, multiple competing gateways can send traffic to the wrong network even with healthy link state.
Question 629
A branch domain controller has correct time initially but drifts after the PDC emulator source changes. What change should be prioritized to restore the intended behavior?
- Manually resynchronize the branch domain controller once while leaving the forest-root PDC emulator with its newly misconfigured time source.
- Point this branch domain controller to an unrelated public NTP server while the forest PDC emulator continues using the incorrect source.
- Validate authoritative forest time hierarchy and peer configuration using W32Time diagnostics.
- Remove stale DNS answers or update load-balancer records and validate client caching.
Explanation
Correct Answer
C:Validate authoritative forest time hierarchy and peer configuration using W32Time diagnostics. The underlying technical reason is that domain time service follows a hierarchy; a broken upstream reference propagates drift.
Incorrect Answers
A:The branch clock can drift again if the authoritative time hierarchy remains broken at the PDC. Investigate the PDC source and the domain time path rather than only resetting the downstream clock.
B:Replacing one downstream peer does not repair the domain-wide authoritative hierarchy and can create inconsistent clock sources among controllers. The PDC and domain W32Time chain require diagnosis.
D:Multiple records can lead requests to an unhealthy address even when one destination works. In this situation, domain time service follows a hierarchy; a broken upstream reference propagates drift.
Question 630
A name resolves to two IPs and clients intermittently hit a decommissioned backend. Which implementation step directly corrects the underlying problem?
- Query the relevant DNS A record and resolver cache, then correct stale name resolution.
- Diagnose DNS suffix, A/AAAA record and client resolver settings.
- Set the appropriate AD-integrated DNS servers and verify required SRV lookups.
- Remove stale DNS answers or update load-balancer records and validate client caching.
Explanation
Correct Answer
D:Multiple records can lead requests to an unhealthy address even when one destination works. A suitable corrective action is to remove stale DNS answers or update load-balancer records and validate client caching.
Incorrect Answers
A:ICMP connectivity to other addresses does not prove the target name resolves correctly. However, multiple records can lead requests to an unhealthy address even when one destination works.
B:IP connectivity with FQDN failure points to name resolution rather than necessarily a firewall port rule. Here, multiple records can lead requests to an unhealthy address even when one destination works.
C:AD clients rely on internal service locator records not generally available through public DNS. In this situation, multiple records can lead requests to an unhealthy address even when one destination works.
Configuring Windows Server Hybrid Advanced Services (AZ-801) Practice Tests