Microsoft AZ-800 Practice Test 60
Question 590
After the approved correction, which result would BEST establish success? A Windows Server join to an on-premises domain fails although the server can reach the public internet.
- The multi-domain users obtain intended access with no unintended nested membership.
- The intended security setting appears in resultant set of policy with the expected winning GPO identified.
- The computer account is created in the intended domain and secure-channel checks succeed.
- Only the intended Windows client devices process the setting while servers remain unaffected.
Explanation
Correct Answer
C:The computer account is created in the intended domain and secure-channel checks succeed. Appropriate intervention: Verify internal AD DNS, time synchronization and required domain controller connectivity before attempting the join.
Incorrect Answers
A:This evidence fits a different problem (A multinational organization needs one group containing users from different domains in the same forest for a shared business application.). For the stated issue, verify: The computer account is created in the intended domain and secure-channel checks succeed.
B:The intended security setting appears in resultant set of policy with the expected winning GPO identified. This evidence fits a different problem (Two domain GPOs configure conflicting security settings and an engineer mistakes creation time for precedence.). For the stated issue, verify: The computer account is created in the intended domain and secure-channel checks succeed.
D:Only the intended Windows client devices process the setting while servers remain unaffected. This evidence fits a different problem (A workstation-specific GPO accidentally applies a setting to Windows Server machines in the same OU.). For the stated issue, verify: The computer account is created in the intended domain and secure-channel checks succeed.
Question 591
During a hybrid infrastructure change, this issue arises: A department file share exposes confidential folder names to users who cannot open their contents. What should the administrator do FIRST?
- Compare supported application and file-system feature requirements and format the target volume using the appropriate NTFS or ReFS option.
- Enable appropriately scoped object access auditing and SACLs with protected event collection and retention.
- Enable supported access-based enumeration and retain correct underlying NTFS ACLs for authorized groups.
- Examine Azure Files share-level role assignment and file/directory ACLs and grant only the missing approved permission.
Explanation
Correct Answer
C:Enable supported access-based enumeration and retain correct underlying NTFS ACLs for authorized groups. Access-based enumeration hides unauthorized directory listings but is not a replacement for file permissions. Verified result: Users see only folders they are permitted to access while direct unauthorized attempts still fail.
Incorrect Answers
A:This action addresses a different Windows Server condition (A workload requires file-system features that differ across NTFS and ReFS but the engineer chooses based only on the displayed name.), not the stated case. Correct approach here: Enable supported access-based enumeration and retain correct underlying NTFS ACLs for authorized groups.
B:This action addresses a different Windows Server condition (A security review must identify which account accessed a sensitive share but file access audit settings do not generate any usable events.), not the stated case. Correct approach here: Enable supported access-based enumeration and retain correct underlying NTFS ACLs for authorized groups.
D:This action addresses a different Windows Server condition (A user has read NTFS ACL permissions on files in Azure Files but still receives access denied at share connection time.), not the stated case. Correct approach here: Enable supported access-based enumeration and retain correct underlying NTFS ACLs for authorized groups.
Question 592
An AZ-800 legacy workload administrator encounters: A VM receives an address in the wrong VLAN even though the physical uplink is a correctly configured trunk. What intervention is BEST justified?
- Remove embedded secrets and inject short-lived scoped credentials through a supported runtime secret mechanism.
- Configure the VM network adapter VLAN mode and applicable vSwitch/uplink settings consistently with intended segmentation.
- Use supported application-consistent backup procedures and, for short test rollback, choose production checkpoints only where appropriate.
- Enable supported Windows containers capabilities and runtime components and validate a controlled test image.
Explanation
Correct Answer
B:Configure the VM network adapter VLAN mode and applicable vSwitch/uplink settings consistently with intended segmentation. Hyper-V VM network adapter VLAN settings determine guest virtual port segmentation independently of IP naming. Verified result: VM traffic appears on the approved VLAN and cannot access disallowed network segments.
Incorrect Answers
A:This action addresses a different Windows Server condition (A Windows container image contains a database password in a Dockerfile environment declaration committed to source control.), not the stated case. Correct approach here: Configure the VM network adapter VLAN mode and applicable vSwitch/uplink settings consistently with intended segmentation.
C:This action addresses a different Windows Server condition (A domain controller VM is due for a risky update and an operator proposes a standard snapshot as its long-term backup.), not the stated case. Correct approach here: Configure the VM network adapter VLAN mode and applicable vSwitch/uplink settings consistently with intended segmentation.
D:This action addresses a different Windows Server condition (An administrator installed Docker tooling but neglected required Windows Server container host features and networking configuration.), not the stated case. Correct approach here: Configure the VM network adapter VLAN mode and applicable vSwitch/uplink settings consistently with intended segmentation.
Question 593
Which proposed shortcut creates the clearest avoidable risk for this scenario? Azure Policy flags a Windows Server setting as noncompliant and the team expects every audit policy to fix it automatically.
- Use approved secure transport for remote administrative operations.
- Interpret every noncompliant Azure Policy audit result as proof that the server has already been repaired.
- Review relevant Windows Event Logs when investigating service failures.
- Compare actual Azure and on-premises network prefixes before adding a route.
Explanation
Correct Answer
B:Azure Policy effects differ; audit findings do not by themselves install settings or grant remediation privileges. Safer intervention: Check whether the definition is audit-only or supports remediation and deploy the authorized remediation task when available.
Incorrect Answers
A:Use approved secure transport for remote administrative operations. Remote access protection must cover credentials and commands. For this case: Check whether the definition is audit-only or supports remediation and deploy the authorized remediation task when available.
C:Review relevant Windows Event Logs when investigating service failures. Recorded failure evidence is more reliable than guessing. For this case: Check whether the definition is audit-only or supports remediation and deploy the authorized remediation task when available.
D:Compare actual Azure and on-premises network prefixes before adding a route. Overlapping addresses can cause routing ambiguity. For this case: Check whether the definition is audit-only or supports remediation and deploy the authorized remediation task when available.
Question 594
Choose the most appropriate correction for the following Windows Server scenario: An Arc-enabled Windows Server uses WSUS and Azure Update Manager finds no approved packages after the team ignores its local update-source policy.
- Restrict exposed functions and validate that commands cannot escape the intended role capability.
- Verify the OS Windows Update or WSUS policy and approved catalog synchronization before rerunning assessment.
- Install and configure the supported OpenSSH Server feature, service startup, host keys and scoped firewall access.
- Configure supported managed identity and RBAC for the runbook's exact actions, then update authentication logic.
Explanation
Correct Answer
B:Verified result: Update Manager reports correctly approved WSUS updates without changing the server's trusted update source unexpectedly.
Incorrect Answers
A:This action addresses a different Windows Server condition (A custom JEA endpoint accidentally reveals arbitrary native command execution through an unrestricted shell command wrapper.), not the stated case. Correct approach here: Verify the OS Windows Update or WSUS policy and approved catalog synchronization before rerunning assessment.
C:This action addresses a different Windows Server condition (An operations team needs authenticated SSH management of a Windows Server, but service and firewall state were never configured.), not the stated case. Correct approach here: Verify the OS Windows Update or WSUS policy and approved catalog synchronization before rerunning assessment.
D:This action addresses a different Windows Server condition (A PowerShell automation runbook uses a retired stored credential to modify an Azure resource and repeatedly fails.), not the stated case. Correct approach here: Verify the OS Windows Update or WSUS policy and approved catalog synchronization before rerunning assessment.
Question 595
An AZ-800 legacy workload administrator encounters: A helpdesk analyst needs to reset passwords for one business OU but was offered Domain Admin membership. What intervention is BEST justified?
- Deploy redundant pass-through authentication agents and verify secure on-premises validation and failover.
- Delegate only password reset rights on the intended organizational unit and test permissions using a scoped support identity.
- Follow the documented lingering-object detection and remediation path, or rebuild the stale controller when necessary.
- Adjust supported OU and domain filtering in the sync configuration and verify deletion impacts before applying.
Explanation
Correct Answer
B:Delegate only password reset rights on the intended organizational unit and test permissions using a scoped support identity. AD object ACL delegation can scope administrative operations more tightly than broad built-in groups. Verified result: Resets succeed for in-scope users while out-of-scope privileged accounts remain protected.
Incorrect Answers
A:This action addresses a different Windows Server condition (A regulated environment requires cloud sign-in validation against on-premises AD DS passwords through supported agents.), not the stated case. Correct approach here: Delegate only password reset rights on the intended organizational unit and test permissions using a scoped support identity.
C:This action addresses a different Windows Server condition (A domain controller returns online after being disconnected beyond tombstone lifetime and has obsolete directory objects.), not the stated case. Correct approach here: Delegate only password reset rights on the intended organizational unit and test permissions using a scoped support identity.
D:This action addresses a different Windows Server condition (A pilot should synchronize one department but Entra Connect unexpectedly exports disabled lab accounts from another OU.), not the stated case. Correct approach here: Delegate only password reset rights on the intended organizational unit and test permissions using a scoped support identity.
Question 596
Select TWO statements: the suitable action and its verification for this Windows Server case. A domain controller's database is corrupted, but the site still has two healthy writable replicas.
- Verification: The recovered controller rejoins replication without USN rollback or unsupported database cloning.
- Unsafe shortcut: Copy NTDS.dit from an unrelated online controller over the failed server's open database file.
- Action: Verify internal AD DNS, time synchronization and required domain controller connectivity before attempting the join.
- Verification: Signed tokens validate after rollout without requiring every user to reset their password.
- Action: Validate replication health and a supported rebuild or restore strategy rather than copying live database files between DCs.
Explanation
Correct Answers
A:Verification: The recovered controller rejoins replication without USN rollback or unsupported database cloning. AD DS recovery depends on consistent directory replication identity and supported system-state procedures.
E:Action: Validate replication health and a supported rebuild or restore strategy rather than copying live database files between DCs. AD DS recovery depends on consistent directory replication identity and supported system-state procedures.
Incorrect Answers
B:Unsafe shortcut: Copy NTDS.dit from an unrelated online controller over the failed server's open database file. AD DS recovery depends on consistent directory replication identity and supported system-state procedures. Safer action: Validate replication health and a supported rebuild or restore strategy rather than copying live database files between DCs.
C:This applies to a different case (A Windows Server join to an on-premises domain fails although the server can reach the public internet.).
D:Verification: Signed tokens validate after rollout without requiring every user to reset their password. This evidence belongs to another problem (Cloud sign-ins fail when a federation service signing certificate expires without a coordinated rollover.). Here confirm: The recovered controller rejoins replication without USN rollback or unsupported database cloning.
Question 597
Before a production change, what specific verification best diagnoses this issue? A compliance standard requires SMB integrity protection, but an administrator disables SMB signing to solve one client compatibility issue.
- Inspect storage account kind, file share endpoint, authentication, private endpoint and client mount logs.
- Inspect Get-SmbConnection, signing policy, SMB client diagnostics and representative session properties.
- Inspect audit policy, file SACL, event IDs and collector retention.
- Inspect RBAC role at share scope, SMB mount identity, NTFS ACL and access logs.
Explanation
Correct Answer
B:Inspect Get-SmbConnection, signing policy, SMB client diagnostics and representative session properties. SMB signing protects message integrity and may be enforced separately from SMB encryption. Next step: Review supported SMB client/server signing requirements and resolve client compatibility without weakening required integrity policy.
Incorrect Answers
A:This diagnosis belongs to a different case (An organization wants to move a Windows file share into Azure but creates a storage account without configuring an SMB file share or supported network access.). Here examine: Inspect Get-SmbConnection, signing policy, SMB client diagnostics and representative session properties.
C:This diagnosis belongs to a different case (A security review must identify which account accessed a sensitive share but file access audit settings do not generate any usable events.).
D:This diagnosis belongs to a different case (A user has read NTFS ACL permissions on files in Azure Files but still receives access denied at share connection time.). Here examine: Inspect Get-SmbConnection, signing policy, SMB client diagnostics and representative session properties.
Question 598
A hybrid administrator must isolate a fault: A virtual domain controller experiences time jumps because host and domain time sources are configured inconsistently. Which evidence is MOST useful?
- Inspect image digest, registry permissions, build pipeline record and pull output.
- Inspect docker network settings, HNS endpoints, container DNS and port mapping.
- Inspect installed features, runtime service, image inventory and sample container execution.
- Check guest w32tm status, Hyper-V integration services and clock event logs.
Explanation
Correct Answer
D:Check guest w32tm status, Hyper-V integration services and clock event logs. Host-guest time integration must coexist with domain time synchronization policy for directory workloads. Next step: Review Hyper-V time synchronization integration settings and authoritative AD DS time hierarchy for that guest role.
Incorrect Answers
A:Inspect image digest, registry permissions, build pipeline record and pull output. This diagnosis belongs to a different case (Production deployment pulls an unpinned latest image and unexpectedly receives a breaking version.). Here examine: Check guest w32tm status, Hyper-V integration services and clock event logs.
B:This diagnosis belongs to a different case (Two Windows containers need an application-to-database connection, but their network is isolated and an administrator opens host firewall ports at random.). Here examine: Check guest w32tm status, Hyper-V integration services and clock event logs.
C:Inspect installed features, runtime service, image inventory and sample container execution. This diagnosis belongs to a different case (An administrator installed Docker tooling but neglected required Windows Server container host features and networking configuration.). Here examine: Check guest w32tm status, Hyper-V integration services and clock event logs.
Question 599
Choose the most appropriate correction for the following Windows Server scenario: A user account locks repeatedly after password changes because an old mobile client keeps sending stale credentials.
- Evaluate Microsoft Entra Domain Services managed-domain capabilities and join supported VMs using provided managed services.
- Confirm change authorization and schema compatibility, then execute the supported extension procedure with the schema FSMO owner reachable.
- Trace lockout source events to the device and update the saved credential without weakening lockout policy.
- Use appropriate security filtering and read/apply permissions on the intended GPO scope.
Explanation
Correct Answer
C:AD account lockout events can identify authentication sources and should be investigated before changing password policy.
Incorrect Answers
A:This action addresses a different Windows Server condition (A legacy LDAP/Kerberos application needs domain-compatible services in Azure but operators want to deploy their own forest controllers in a managed domain.), not the stated case. Correct approach here: Trace lockout source events to the device and update the saved credential without weakening lockout policy.
B:Confirm change authorization and schema compatibility, then execute the supported extension procedure with the schema FSMO owner reachable. This action addresses a different Windows Server condition (An approved directory application requires a forest schema extension but the update is attempted from a controller that cannot contact the schema master.), not the stated case. Correct approach here: Trace lockout source events to the device and update the saved credential without weakening lockout policy.
D:This action addresses a different Windows Server condition (A software-install GPO targets every user in a division, but only the accounting subgroup should receive it.), not the stated case.
Question 600
A hybrid administrator must isolate a fault: A company cannot add a new child domain because the domain naming FSMO role holder is unavailable. Which evidence is MOST useful?
- Inspect site-link configuration, ISTG topology, repadmin showrepl and WAN route monitoring.
- Use repadmin showrepl and replsummary with DNS, firewall and event log correlation.
- Review sign-in logs, report-only results, excluded emergency accounts and rollback plan.
- Inspect forest FSMO ownership, configuration naming context and trusted topology.
Explanation
Correct Answer
D:Inspect forest FSMO ownership, configuration naming context and trusted topology. The domain naming master controls additions and removals of domains in an AD DS forest. Next step: Restore or appropriately transfer the domain naming role and verify forest-wide domain metadata replication.
Incorrect Answers
A:Inspect site-link configuration, ISTG topology, repadmin showrepl and WAN route monitoring. This diagnosis belongs to a different case (Two WAN circuits have different latency, but AD replication favors the slow path because site-link design is incorrect.). Here examine: Inspect forest FSMO ownership, configuration naming context and trusted topology.
B:Use repadmin showrepl and replsummary with DNS, firewall and event log correlation. This diagnosis belongs to a different case (A branch domain controller has stale group memberships while its inbound replication partner reports repeated RPC failures.). Here examine: Inspect forest FSMO ownership, configuration naming context and trusted topology.
C:Review sign-in logs, report-only results, excluded emergency accounts and rollback plan. This diagnosis belongs to a different case (An organization activates a new Conditional Access requirement for all users without testing whether hybrid break-glass administrators can sign in.). Here examine: Inspect forest FSMO ownership, configuration naming context and trusted topology.