Microsoft AZ-800 Practice Test 47
Question 460
Which Windows Server or hybrid infrastructure principle BEST explains this case? A domain controller's database is corrupted, but the site still has two healthy writable replicas.
- AD DS domain join requires correct domain location and machine-account secure channel setup.
- AD DS recovery depends on consistent directory replication identity and supported system-state procedures.
- Managed service accounts differ from ordinary users in allowed host use and password administration.
- Federation trust depends on correct token-signing certificate material and relying-party metadata.
Explanation
Correct Answer
B:AD DS recovery depends on consistent directory replication identity and supported system-state procedures. Apply: Validate replication health and a supported rebuild or restore strategy rather than copying live database files between DCs.
Incorrect Answers
A:This principle corresponds to another condition (A Windows Server join to an on-premises domain fails although the server can reach the public internet.). The decisive principle for this case is: AD DS recovery depends on consistent directory replication identity and supported system-state procedures.
C:This principle corresponds to another condition (A single-host scheduled service needs a managed password but its owner mistakenly proposes a human interactive account.). The decisive principle for this case is: AD DS recovery depends on consistent directory replication identity and supported system-state procedures.
D:Federation trust depends on correct token-signing certificate material and relying-party metadata. This principle corresponds to another condition (Cloud sign-ins fail when a federation service signing certificate expires without a coordinated rollover.). The decisive principle for this case is: AD DS recovery depends on consistent directory replication identity and supported system-state procedures.
Question 461
Which Windows Server or hybrid infrastructure principle BEST explains this case? A fleet is onboarded to Azure Arc but its environment tags are inconsistent, making policy assignments target the wrong group.
- Azure tags and resource groups drive management organization but do not confer on-premises authentication privileges.
- Extension deployment for Arc-enabled machines follows Arc resource providers rather than arbitrary native VM assumptions.
- Azure Update Manager can assess and schedule updates for eligible Arc-enabled servers using the Azure Connected Machine agent.
- Azure-native VMs and Arc-enabled external servers are different Azure management resource types.
Explanation
Correct Answer
A:Azure tags and resource groups drive management organization but do not confer on-premises authentication privileges. Apply: Define and enforce consistent Azure resource tag assignments and appropriate policy scoping for Arc machine resources.
Incorrect Answers
B:This principle corresponds to another condition (A hybrid Windows Server needs an approved monitoring extension but the deployment was targeted only to Azure-native VMs.). The decisive principle for this case is: Azure tags and resource groups drive management organization but do not confer on-premises authentication privileges.
C:This principle corresponds to another condition (On-premises Arc servers are patched manually despite a requirement to coordinate a monthly supported maintenance window.). The decisive principle for this case is: Azure tags and resource groups drive management organization but do not confer on-premises authentication privileges.
D:This principle corresponds to another condition (A Windows Server already running as an Azure IaaS virtual machine is mistakenly onboarded with the Connected Machine agent as if it were on premises.). The decisive principle for this case is: Azure tags and resource groups drive management organization but do not confer on-premises authentication privileges.
Question 462
Which TWO claims correctly identify the intervention and evidence for the following hybrid issue? A privileged account continues inheriting unsafe OU permissions despite a hardened administrative design.
- Verification: Privileged objects retain the approved protected permissions even when ordinary OU ACLs change.
- Action: Review protected account behavior and AdminSDHolder-associated ACL controls with an authorized security administrator.
- Verification: Only the intended active connector exports directory changes while standby is ready for failover.
- Unsafe shortcut: Remove all security ACLs from AdminSDHolder so every privileged account inherits unrestricted rights.
- Action: Adjust supported OU and domain filtering in the sync configuration and verify deletion impacts before applying.
Explanation
Correct Answers
A:Verification: Privileged objects retain the approved protected permissions even when ordinary OU ACLs change. Protected group membership and SDProp can change how inheritance applies to privileged AD objects.
B:Action: Review protected account behavior and AdminSDHolder-associated ACL controls with an authorized security administrator. Protected group membership and SDProp can change how inheritance applies to privileged AD objects.
Incorrect Answers
C:This evidence belongs to another problem (A migration introduces a second Microsoft Entra Connect server but both are configured as active sync exporters.).
D:Unsafe shortcut: Remove all security ACLs from AdminSDHolder so every privileged account inherits unrestricted rights. Protected group membership and SDProp can change how inheritance applies to privileged AD objects. Safer action: Review protected account behavior and AdminSDHolder-associated ACL controls with an authorized security administrator.
E:This applies to a different case (A pilot should synchronize one department but Entra Connect unexpectedly exports disabled lab accounts from another OU.). Use: Review protected account behavior and AdminSDHolder-associated ACL controls with an authorized security administrator.
Question 463
After the approved correction, which result would BEST establish success? A VM's data volume is nearly full even after its Hyper-V host virtual disk was expanded.
- Both virtual disk capacity and the guest filesystem report the approved larger usable size.
- Authorized administrators connect to private VMs without adding a public IP or opening internet-facing RDP.
- The intended Linux workload runs under a supported environment while Windows containers continue on their compatible runtime.
- Repository and image scans find no static database password while the app authenticates through an approved secret path.
Explanation
Correct Answer
A:Both virtual disk capacity and the guest filesystem report the approved larger usable size. Appropriate intervention: Expand the VHDX safely, then extend the corresponding guest partition or volume after checking layout and support.
Incorrect Answers
B:This evidence fits a different problem (A VM has no public IP and the team wants secure browser-based RDP without deploying a VPN on each administrator laptop.). For the stated issue, verify: Both virtual disk capacity and the guest filesystem report the approved larger usable size.
C:The intended Linux workload runs under a supported environment while Windows containers continue on their compatible runtime. This evidence fits a different problem (A Windows Server operator assumes every Windows-hosted container is a Linux image even when the runtime is configured for Windows process containers.). For the stated issue, verify: Both virtual disk capacity and the guest filesystem report the approved larger usable size.
D:Repository and image scans find no static database password while the app authenticates through an approved secret path. This evidence fits a different problem (A Windows container image contains a database password in a Dockerfile environment declaration committed to source control.). For the stated issue, verify: Both virtual disk capacity and the guest filesystem report the approved larger usable size.
Question 464
A hybrid administrator must isolate a fault: Two Windows containers need an application-to-database connection, but their network is isolated and an administrator opens host firewall ports at random. Which evidence is MOST useful?
- Inspect docker network settings, HNS endpoints, container DNS and port mapping.
- Inspect build history, image metadata, secret scanning output and runtime secret access.
- Inspect disk SKU, Azure IOPS metrics, latency, VM limits and application load tests.
- Inspect image digest, Dockerfile, container mounts and recreated-instance behavior.
Explanation
Correct Answer
A:Inspect docker network settings, HNS endpoints, container DNS and port mapping. Windows container connectivity depends on container network topology and host networking configuration. Next step: Select the supported HNS network mode and configure intended container connectivity and name resolution.
Incorrect Answers
B:Inspect build history, image metadata, secret scanning output and runtime secret access. This diagnosis belongs to a different case (A Windows container image contains a database password in a Dockerfile environment declaration committed to source control.). Here examine: Inspect docker network settings, HNS endpoints, container DNS and port mapping.
C:This diagnosis belongs to a different case (An Azure Windows Server VM has a critical data disk created with the wrong resilience and performance tier for a database workload.). Here examine: Inspect docker network settings, HNS endpoints, container DNS and port mapping.
D:This diagnosis belongs to a different case (A developer edits live files inside a running container and assumes those changes will persist after the container is replaced by a fresh instance.). Here examine: Inspect docker network settings, HNS endpoints, container DNS and port mapping.
Question 465
Choose the most appropriate correction for the following Windows Server scenario: A remote recovery site is hundreds of milliseconds away and application write latency must remain predictable despite some possible data loss.
- Enable appropriately scoped object access auditing and SACLs with protected event collection and retention.
- Enable supported SMB encryption at share or server scope and verify client compatibility and performance.
- Evaluate asynchronous Storage Replica and document a realistic recovery point objective for the distant site.
- Examine Azure Files share-level role assignment and file/directory ACLs and grant only the missing approved permission.
Explanation
Correct Answer
C:Evaluate asynchronous Storage Replica and document a realistic recovery point objective for the distant site. Asynchronous replication decouples primary write acknowledgment from remote commit at the cost of possible data loss. Verified result: Writes continue on the primary without WAN-round-trip acknowledgment and recovery tests quantify lag.
Incorrect Answers
A: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: Evaluate asynchronous Storage Replica and document a realistic recovery point objective for the distant site.
B:This action addresses a different Windows Server condition (Sensitive SMB shares cross a semi-trusted network, but encryption is disabled because the team assumes NTFS ACLs encrypt traffic.), not the stated case. Correct approach here: Evaluate asynchronous Storage Replica and document a realistic recovery point objective for the distant site.
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: Evaluate asynchronous Storage Replica and document a realistic recovery point objective for the distant site.
Question 466
For the following Windows Server case, which observable outcome verifies the intended fix? A small remote office has no local domain controller, but a nearby site can serve it more reliably than headquarters.
- In-scope identities are provisioned correctly and unsupported synchronization requirements remain documented.
- Remote clients choose the reachable intended controller during planned nearest-site outages.
- Branch logons resolve the intended site-specific domain controller without unnecessary cross-WAN locator requests.
- Branch logons use permitted cached credentials while the RODC cannot originate unauthorized domain directory changes.
Explanation
Correct Answer
B:Remote clients choose the reachable intended controller during planned nearest-site outages. Appropriate intervention: Review site coverage and subnet mappings so an appropriate existing domain controller services the office.
Incorrect Answers
A:This evidence fits a different problem (A small forest needs simplified agent-based user provisioning to Entra ID, but a team assumes Cloud Sync has every feature of Connect Sync.). For the stated issue, verify: Remote clients choose the reachable intended controller during planned nearest-site outages.
C:Branch logons resolve the intended site-specific domain controller without unnecessary cross-WAN locator requests. This evidence fits a different problem (A branch subnet was never assigned to an AD site and client computers choose a distant domain controller across a slow WAN.). For the stated issue, verify: Remote clients choose the reachable intended controller during planned nearest-site outages.
D:This evidence fits a different problem (A lightly staffed branch has a domain controller containing writable directory data even though physical theft risk is high.). For the stated issue, verify: Remote clients choose the reachable intended controller during planned nearest-site outages.
Question 467
Select TWO statements: the suitable action and its verification for this Windows Server case. An organization plans to replace DFS Replication with Azure File Sync but assumes DFS namespaces and data replication are identical services.
- Action: Configure an appropriate private endpoint and private DNS zone integration for the file service, preserving supported name resolution.
- Action: Inventory DFS namespaces, DFSR topology and client paths, then stage a supported migration preserving intended access paths.
- Unsafe shortcut: Remove every DFS namespace link and delete data before testing File Sync endpoints.
- Verification: A test application write reaches the replica within expected behavior, and failover follows approved role transition.
- Verification: Clients reach approved namespace targets and migrated content synchronizes without duplicate conflicting writers.
Explanation
Correct Answers
B:Action: Inventory DFS namespaces, DFSR topology and client paths, then stage a supported migration preserving intended access paths. DFS Namespaces provides logical referrals while DFS Replication and Azure File Sync have distinct data synchronization semantics.
E:Verification: Clients reach approved namespace targets and migrated content synchronizes without duplicate conflicting writers. DFS Namespaces provides logical referrals while DFS Replication and Azure File Sync have distinct data synchronization semantics.
Incorrect Answers
A:This applies to a different case (An enterprise requires private Azure Files access but DNS still resolves the storage account file endpoint to a public IP.).
C:Unsafe shortcut: Remove every DFS namespace link and delete data before testing File Sync endpoints. DFS Namespaces provides logical referrals while DFS Replication and Azure File Sync have distinct data synchronization semantics. Safer action: Inventory DFS namespaces, DFSR topology and client paths, then stage a supported migration preserving intended access paths.
D:Here confirm: Clients reach approved namespace targets and migrated content synchronizes without duplicate conflicting writers.
Question 468
A Windows Server hybrid administrator observes this issue: A domain controller VM is due for a risky update and an operator proposes a standard snapshot as its long-term backup. Which action MOST directly addresses it?
- Use supported application-consistent backup procedures and, for short test rollback, choose production checkpoints only where appropriate.
- Use PowerShell Direct with appropriate guest credentials from the host where supported, then diagnose the virtual network adapter.
- Design supported failover clustering and storage or replication according to the required restart availability model.
- Configure a supported VM scale set autoscaling and health/load-balancer policy for stateless servers.
Explanation
Correct Answer
A:Production checkpoints use guest-aware mechanisms instead of capturing running memory; neither checkpoint type replaces backup.
Incorrect Answers
B:Use PowerShell Direct with appropriate guest credentials from the host where supported, then diagnose the virtual network adapter. This action addresses a different Windows Server condition (A Windows guest has a broken virtual NIC, but an administrator on its Hyper-V host needs to run a recovery command inside it.), not the stated case. Correct approach here: Use supported application-consistent backup procedures and, for short test rollback, choose production checkpoints only where appropriate.
C:This action addresses a different Windows Server condition (A business-critical VM runs on one standalone Hyper-V host, but the team assumes another idle host will automatically fail over the VM.), not the stated case. Correct approach here: Use supported application-consistent backup procedures and, for short test rollback, choose production checkpoints only where appropriate.
D:This action addresses a different Windows Server condition (A Windows web tier must handle predictable bursts, but engineers add VMs manually and forget to enroll new instances in health probes.), not the stated case. Correct approach here: Use supported application-consistent backup procedures and, for short test rollback, choose production checkpoints only where appropriate.
Question 469
A hybrid administrator must isolate a fault: An Arc-connected server must be checked for a required security baseline, but operations confuse onboarding with active compliance assessment. Which evidence is MOST useful?
- Inspect assigned policy definitions, guest configuration extension, compliance details and machine logs.
- Inspect CIM session options, WinRM or RPC endpoints, WMI namespace permissions and event logs.
- Inspect actual Arc resource tags, scope evaluation and policy assignment target list.
- Inspect role capability definitions, session transcript and attempted command-bypass outcomes.
Explanation
Correct Answer
A:Inspect assigned policy definitions, guest configuration extension, compliance details and machine logs. Azure Arc connection supplies management identity; machine configuration policy performs separate guest-setting assessment. Next step: Assign an appropriate Azure Machine Configuration policy and ensure supported extension and guest configuration components are healthy.
Incorrect Answers
B:Inspect CIM session options, WinRM or RPC endpoints, WMI namespace permissions and event logs. This diagnosis belongs to a different case (Get-CimInstance works locally but returns access denied from the authorized remote monitoring host.). Here examine: Inspect assigned policy definitions, guest configuration extension, compliance details and machine logs.
C:This diagnosis belongs to a different case (A fleet is onboarded to Azure Arc but its environment tags are inconsistent, making policy assignments target the wrong group.). Here examine: Inspect assigned policy definitions, guest configuration extension, compliance details and machine logs.
D:Inspect role capability definitions, session transcript and attempted command-bypass outcomes. This diagnosis belongs to a different case (A custom JEA endpoint accidentally reveals arbitrary native command execution through an unrestricted shell command wrapper.). Here examine: Inspect assigned policy definitions, guest configuration extension, compliance details and machine logs.
Question 470
Which principle supports the appropriate response to this legacy AZ-800 administration scenario? An administrator must manage a server outside the domain but cannot use trusted Kerberos to authenticate the target.
- Azure Policy effects differ; audit findings do not by themselves install settings or grant remediation privileges.
- JEA uses constrained PowerShell session configurations and role capabilities for least-privilege administration.
- Extension deployment for Arc-enabled machines follows Arc resource providers rather than arbitrary native VM assumptions.
- Non-domain remoting requires explicit authentication and server identity trust; TLS can protect the remote endpoint.
Explanation
Correct Answer
D:Non-domain remoting requires explicit authentication and server identity trust; TLS can protect the remote endpoint. Apply: Configure a trusted HTTPS WinRM listener and an approved credential approach instead of blindly adding wildcard trusted hosts.
Incorrect Answers
A:This principle corresponds to another condition (Azure Policy flags a Windows Server setting as noncompliant and the team expects every audit policy to fix it automatically.). The decisive principle for this case is: Non-domain remoting requires explicit authentication and server identity trust; TLS can protect the remote endpoint.
B:This principle corresponds to another condition (A helpdesk technician needs to restart one approved service but receives unrestricted local administrator access for that single task.). The decisive principle for this case is: Non-domain remoting requires explicit authentication and server identity trust; TLS can protect the remote endpoint.
C:This principle corresponds to another condition (A hybrid Windows Server needs an approved monitoring extension but the deployment was targeted only to Azure-native VMs.). The decisive principle for this case is: Non-domain remoting requires explicit authentication and server identity trust; TLS can protect the remote endpoint.