Question 760A branch DHCP server is added but the local router does not relay client broadcasts to its subnet. The proposed correction is: Configure DHCP relay on the required routed interface. Which technical principle best supports that correction? Names alone do not establish unique principals across trust boundaries. Relay access requires application authorization in addition to endpoint availability. Identity connectors need controlled directory privileges. DHCP requests need a supported relay path across Layer 3 boundaries. ExplanationCorrect Answer D:DHCP requests need a supported relay path across Layer 3 boundaries. This principle explains why the proposed response is appropriate: Configure DHCP relay on the required routed interface. In this situation, confirm success by checking: A remote-subnet client obtains a valid lease from the intended server.Incorrect Answers A:Names alone do not establish unique principals across trust boundaries. This does not establish the proposed intervention. The governing principle here is: DHCP requests need a supported relay path across Layer 3 boundaries. Apply it by: Configure DHCP relay on the required routed interface. B:Relay access requires application authorization in addition to endpoint availability. This does not establish the proposed intervention. The governing principle here is: DHCP requests need a supported relay path across Layer 3 boundaries. Apply it by: Configure DHCP relay on the required routed interface. C:Identity connectors need controlled directory privileges. This does not establish the proposed intervention. The governing principle here is: DHCP requests need a supported relay path across Layer 3 boundaries. Apply it by: Configure DHCP relay on the required routed interface.
Question 761A team enables Windows Subsystem for Linux for a support workload without checking supported OS features and security boundaries. The proposed correction is: Validate WSL prerequisites and align container runtime settings with host policy. Which technical principle best supports that correction? WSL integration depends on enabled platform components and isolation settings. Group Policy Preferences require accurate targeting for per-user settings. SMB share caching settings must follow data-handling requirements. Container isolation still depends on host operating system security. ExplanationCorrect Answer A:WSL integration depends on enabled platform components and isolation settings. This principle explains why the proposed response is appropriate: Validate WSL prerequisites and align container runtime settings with host policy. In this situation, confirm success by checking: The supported Linux container launches with expected resource limits.Incorrect Answers B:Group Policy Preferences require accurate targeting for per-user settings. This does not establish the proposed intervention. The governing principle here is: WSL integration depends on enabled platform components and isolation settings. Apply it by: Validate WSL prerequisites and align container runtime settings with host policy. C:SMB share caching settings must follow data-handling requirements. This does not establish the proposed intervention. The governing principle here is: WSL integration depends on enabled platform components and isolation settings. Apply it by: Validate WSL prerequisites and align container runtime settings with host policy. D:Container isolation still depends on host operating system security. This does not establish the proposed intervention. The governing principle here is: WSL integration depends on enabled platform components and isolation settings. Apply it by: Validate WSL prerequisites and align container runtime settings with host policy.
Question 762An organization migrates DFS shares into Azure File Sync without planning namespace links and client paths. After this proposed change — Design DFS Namespace continuity and staged Azure File Sync migration. — which observation most directly confirms it worked? Normal user subnets cannot open RDP while the management bastion succeeds. Contractor account access is limited to the target share. Pilot client mounts work through the approved new path with rollback available. Users reach the new synchronized target through their normal DFS path. ExplanationCorrect Answer D:Users reach the new synchronized target through their normal DFS path. This is the closest operational evidence for the proposed remediation: Design DFS Namespace continuity and staged Azure File Sync migration. It tests the principle: A successful backend migration must preserve clients' approved namespace access.Incorrect Answers A:Remote Desktop access is a privileged management surface requiring network controls. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Users reach the new synchronized target through their normal DFS path. B:Role membership should follow least privilege rather than administrative convenience. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Users reach the new synchronized target through their normal DFS path. C:File service names are operational dependencies for scripts and mappings. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Users reach the new synchronized target through their normal DFS path.
Question 763An Azure Automation runbook edits production services while using a broad organization-level credential. If this condition remains unresolved, which direct operational or security risk follows? Excessive local rights could permit unrelated system changes. A broad group could change unrelated business data. A leaked account key could expose unrelated shares. Compromised automation could control unrelated Azure resources. ExplanationCorrect Answer D:Compromised automation could control unrelated Azure resources. This is the direct remaining operational, security, or availability consequence of the stated problem. The corrective action would be: Use a narrowly scoped runbook identity and protected secret access. Supporting principle: Automated hybrid operations should apply least privilege to non-human principals.Incorrect Answers A:JEA provides task-scoped administration through restricted session capabilities. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Compromised automation could control unrelated Azure resources. B:Authorization is the combined outcome of group scope and resource permissions. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Compromised automation could control unrelated Azure resources. C:File share authentication should use scoped identities instead of broad reusable keys. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Compromised automation could control unrelated Azure resources.
Question 764A team configures password policy through a child OU GPO expecting it to override domain account policy. Which Windows Server administration response most directly addresses this situation? Validate WSL prerequisites and align container runtime settings with host policy. Create approved update schedules and maintenance windows with reboot controls. Place account password policy controls in the supported domain or fine-grained policy mechanism. Apply policy only within the supported managed-domain administration boundary. ExplanationCorrect Answer C:Place account password policy controls in the supported domain or fine-grained policy mechanism. This is the most direct correction for the documented hypothetical Windows Server condition. The governing technical principle is: Domain account policy processing differs from ordinary workstation GPO inheritance. Observable verification: A representative domain user receives the expected password requirement.Incorrect Answers A:WSL integration depends on enabled platform components and isolation settings. That is relevant to a different intervention. For the stated situation, the required action is: Place account password policy controls in the supported domain or fine-grained policy mechanism. The governing reason is: Domain account policy processing differs from ordinary workstation GPO inheritance. B:Patch orchestration must respect service availability commitments. That is relevant to a different intervention. For the stated situation, the required action is: Place account password policy controls in the supported domain or fine-grained policy mechanism. The governing reason is: Domain account policy processing differs from ordinary workstation GPO inheritance. D:Managed-domain policy capabilities differ from forest-owner privileges. That is relevant to a different intervention. For the stated situation, the required action is: Place account password policy controls in the supported domain or fine-grained policy mechanism. The governing reason is: Domain account policy processing differs from ordinary workstation GPO inheritance.
Question 765A team transfers the PDC emulator role without checking which controller currently holds it. If this condition remains unresolved, which direct operational or security risk follows? Every new employee could inherit sensitive access. Sensitive documents could persist on unmanaged laptops. Automated patching could restart critical workloads at peak time. A botched transfer could disrupt time and password-sensitive directory operations. ExplanationCorrect Answer D:A botched transfer could disrupt time and password-sensitive directory operations. This is the direct remaining operational, security, or availability consequence of the stated problem. The corrective action would be: Confirm the current FSMO role owner and plan a clean role transfer to a healthy controller. Supporting principle: FSMO operations require unique reachable role holders and controlled transitions.Incorrect Answers A:New identity provisioning should not propagate unrelated privileges. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A botched transfer could disrupt time and password-sensitive directory operations. B:SMB share caching settings must follow data-handling requirements. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A botched transfer could disrupt time and password-sensitive directory operations. C:Patch orchestration must respect service availability commitments. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A botched transfer could disrupt time and password-sensitive directory operations.
Question 766A shielded VM cannot start after migration because target hosts lack required guarded-fabric trust. After this proposed change — Validate Host Guardian Service and target host attestation before moving the workload. — which observation most directly confirms it worked? The cloud VM resolves the domain SRV records and locates a controller. The protected VM starts on the approved attested destination. The VM gets a valid address and reaches approved endpoints. After reboot the target disk mounts before the database service starts. ExplanationCorrect Answer B:The protected VM starts on the approved attested destination. This is the closest operational evidence for the proposed remediation: Validate Host Guardian Service and target host attestation before moving the workload. It tests the principle: Shielded VMs require trusted host conditions to unlock protected workloads.Incorrect Answers A:AD DS discovery requires appropriate service records and name resolution. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The protected VM starts on the approved attested destination. C:Cloud virtual NIC addresses must be valid and unique in their subnet. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The protected VM starts on the approved attested destination. D:External block storage availability is a prerequisite for dependent services. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The protected VM starts on the approved attested destination.
Question 767A Windows Server file share is exposed over an untrusted WAN using ordinary SMB TCP without transport protection policy. After this proposed change — Use supported SMB over QUIC where appropriate and validate identity and encryption. — which observation most directly confirms it worked? Both UDP and supported TCP DNS tests succeed to designated resolvers. A remote client connects securely without exposing direct SMB TCP ingress. The gateway consistently connects by fully qualified server names. SMB Direct sessions show RDMA use and meet throughput expectations. ExplanationCorrect Answer B:A remote client connects securely without exposing direct SMB TCP ingress. This is the closest operational evidence for the proposed remediation: Use supported SMB over QUIC where appropriate and validate identity and encryption. It tests the principle: SMB over QUIC carries authenticated encrypted file traffic over QUIC for supported systems.Incorrect Answers A:DNS forwarding cannot operate when network paths block the required protocol. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A remote client connects securely without exposing direct SMB TCP ingress. C:Management tools rely on authenticated endpoints resolved to intended hosts. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A remote client connects securely without exposing direct SMB TCP ingress. D:SMB Direct depends on compatible NIC, network, and host configuration. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A remote client connects securely without exposing direct SMB TCP ingress.
Question 768A GPO change is made without a backup or indication of who approved its settings. Which Windows Server administration response most directly addresses this situation? Use a pilot OU, compare resultant policy, and stage rollout after approval. Update subnet documentation, IPAM, scopes, and routing in a coordinated change. Export a versioned GPO backup and record the authorized change before rollout. Align IPAM role-based access with delegated change duties. ExplanationCorrect Answer C:Export a versioned GPO backup and record the authorized change before rollout. This is the most direct correction for the documented hypothetical Windows Server condition. The governing technical principle is: Directory policy changes need traceability and supported rollback. Observable verification: A restoration rehearsal recovers the exact earlier policy version.Incorrect Answers A:Policy changes should be tested against representative workloads before broad enforcement. That is relevant to a different intervention. For the stated situation, the required action is: Export a versioned GPO backup and record the authorized change before rollout. The governing reason is: Directory policy changes need traceability and supported rollback. B:Subnet boundaries must be consistent across addressing and routing systems. That is relevant to a different intervention. For the stated situation, the required action is: Export a versioned GPO backup and record the authorized change before rollout. The governing reason is: Directory policy changes need traceability and supported rollback. D:IPAM security roles separate visibility from network configuration authority. That is relevant to a different intervention. For the stated situation, the required action is: Export a versioned GPO backup and record the authorized change before rollout. The governing reason is: Directory policy changes need traceability and supported rollback.
Question 769A newly created domain has no configured site placement for its controllers, though applications require local access. Which Windows Server administration response most directly addresses this situation? Repair SYSVOL replication and compare policy-version consistency across controllers. Update namespace folder targets and test referrals from each site. Monitor filesystem metadata and file count constraints alongside capacity. Assign controllers to appropriate AD sites and monitor client referrals. ExplanationCorrect Answer D:Assign controllers to appropriate AD sites and monitor client referrals. This is the most direct correction for the documented hypothetical Windows Server condition. The governing technical principle is: Multi-domain service placement should follow logical site boundaries. Observable verification: Clients discover suitable controllers without unexpected cross-region traffic.Incorrect Answers A:GPO metadata and SYSVOL content must converge for successful processing. That is relevant to a different intervention. For the stated situation, the required action is: Assign controllers to appropriate AD sites and monitor client referrals. The governing reason is: Multi-domain service placement should follow logical site boundaries. B:DFS Namespace abstracts client paths but depends on current backend targets. That is relevant to a different intervention. For the stated situation, the required action is: Assign controllers to appropriate AD sites and monitor client referrals. The governing reason is: Multi-domain service placement should follow logical site boundaries. C:Storage health involves filesystem structures as well as raw bytes. That is relevant to a different intervention. For the stated situation, the required action is: Assign controllers to appropriate AD sites and monitor client referrals. The governing reason is: Multi-domain service placement should follow logical site boundaries.
Question 770An AKS on Windows Server deployment has worker nodes with no compatible networking plugin configuration. Which Windows Server administration response most directly addresses this situation? Align AKS worker prerequisites and a supported container networking configuration. Align supported IKE and IPsec algorithms and lifetimes across peers. Apply a supported container host update policy and validate workload compatibility. Install the supported extension and confirm configuration-assignment reporting. ExplanationCorrect Answer A:Align AKS worker prerequisites and a supported container networking configuration. This is the most direct correction for the documented hypothetical Windows Server condition. The governing technical principle is: Kubernetes worker connectivity depends on consistent node and network setup. Observable verification: Pods reach cluster services and each required worker becomes Ready.Incorrect Answers B:IPsec peers must negotiate compatible proposals before carrying traffic. That is relevant to a different intervention. For the stated situation, the required action is: Align AKS worker prerequisites and a supported container networking configuration. The governing reason is: Kubernetes worker connectivity depends on consistent node and network setup. C:Container isolation still depends on host operating system security. That is relevant to a different intervention. For the stated situation, the required action is: Align AKS worker prerequisites and a supported container networking configuration. The governing reason is: Kubernetes worker connectivity depends on consistent node and network setup. D:Machine configuration compliance requires a reachable agent and extension runtime. That is relevant to a different intervention. For the stated situation, the required action is: Align AKS worker prerequisites and a supported container networking configuration. The governing reason is: Kubernetes worker connectivity depends on consistent node and network setup.