Question 390A Hyper-V host has redundant uplinks but the team uses mismatched NIC teaming settings on switch ports. If this condition remains unresolved, which direct operational or security risk follows? Misconfiguration may leave required Linux tooling unusable. Uplink misconfiguration could create loops or connectivity loss. Unexpected recalls could delay critical workflows during poor connectivity. Policy changes might hide an actual connectivity fault. ExplanationCorrect Answer B:Uplink misconfiguration could create loops or connectivity loss. This is the direct remaining operational, security, or availability consequence of the stated problem. The corrective action would be: Configure a supported host teaming or switch embedded teaming design. Supporting principle: NIC redundancy requires compatible teaming and upstream switching assumptions.Incorrect Answers A:WSL integration depends on enabled platform components and isolation settings. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Uplink misconfiguration could create loops or connectivity loss. C:Tiering moves cold data while retaining a usable synchronized namespace. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Uplink misconfiguration could create loops or connectivity loss. D:Directory synchronization relies on approved network endpoints and healthy agents. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Uplink misconfiguration could create loops or connectivity loss.
Question 391Two DHCP servers serve the same location without a defined failover relationship or lease coordination. The proposed correction is: Configure a supported DHCP failover relationship with appropriate scope ownership. Which technical principle best supports that correction? Automatic private addressing indicates the expected DHCP lease was not received. Tiering moves cold data while retaining a usable synchronized namespace. DHCP high availability requires synchronized lease state. Synchronized file servers still require healthy local volume capacity. ExplanationCorrect Answer C:DHCP high availability requires synchronized lease state. This principle explains why the proposed response is appropriate: Configure a supported DHCP failover relationship with appropriate scope ownership. In this situation, confirm success by checking: During a planned server outage clients continue receiving nonconflicting leases.Incorrect Answers A:Automatic private addressing indicates the expected DHCP lease was not received. This does not establish the proposed intervention. The governing principle here is: DHCP high availability requires synchronized lease state. Apply it by: Configure a supported DHCP failover relationship with appropriate scope ownership. B:Tiering moves cold data while retaining a usable synchronized namespace. This does not establish the proposed intervention. The governing principle here is: DHCP high availability requires synchronized lease state. Apply it by: Configure a supported DHCP failover relationship with appropriate scope ownership. D:Synchronized file servers still require healthy local volume capacity. This does not establish the proposed intervention. The governing principle here is: DHCP high availability requires synchronized lease state. Apply it by: Configure a supported DHCP failover relationship with appropriate scope ownership.
Question 392An Azure VM is replicated across regions but application teams never test DNS and endpoint failover. If this condition remains unresolved, which direct operational or security risk follows? Memory starvation could crash an otherwise healthy service. A replicated guest could be healthy yet inaccessible after disaster. Users may encounter failed sign-on despite healthy backend servers. The application could still run out of guest filesystem space. ExplanationCorrect Answer B:A replicated guest could be healthy yet inaccessible after disaster. This is the direct remaining operational, security, or availability consequence of the stated problem. The corrective action would be: Run a coordinated application failover test including DNS and client routing. Supporting principle: Recoverability depends on service endpoints as well as VM replicas.Incorrect Answers A:Dynamic Memory balances host use against guest minimum working-set needs. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A replicated guest could be healthy yet inaccessible after disaster. C:Reverse proxy authentication requires a supported trusted identity path. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A replicated guest could be healthy yet inaccessible after disaster. D:Virtual disk capacity changes and guest partition growth are separate operations. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A replicated guest could be healthy yet inaccessible after disaster.
Question 393A remote site deploys a domain controller before its site subnet exists in Active Directory Sites and Services. The proposed correction is: Associate the site's IP subnet with the correct AD DS site object. Which technical principle best supports that correction? Client connectivity requires accurate DHCP network options beyond address allocation. Client locator behavior depends on matching network subnets to directory sites. The site locator uses subnet membership to select nearby directory services. Kubernetes worker connectivity depends on consistent node and network setup. ExplanationCorrect Answer B:Client locator behavior depends on matching network subnets to directory sites. This principle explains why the proposed response is appropriate: Associate the site's IP subnet with the correct AD DS site object. In this situation, confirm success by checking: Clients in the new subnet discover the intended local controller.Incorrect Answers A:Client connectivity requires accurate DHCP network options beyond address allocation. This does not establish the proposed intervention. The governing principle here is: Client locator behavior depends on matching network subnets to directory sites. Apply it by: Associate the site's IP subnet with the correct AD DS site object. C:The site locator uses subnet membership to select nearby directory services. This does not establish the proposed intervention. The governing principle here is: Client locator behavior depends on matching network subnets to directory sites. Apply it by: Associate the site's IP subnet with the correct AD DS site object. D:Kubernetes worker connectivity depends on consistent node and network setup. This does not establish the proposed intervention. The governing principle here is: Client locator behavior depends on matching network subnets to directory sites. Apply it by: Associate the site's IP subnet with the correct AD DS site object.
Question 394A distribution center moves subnets but leaves them assigned to the old AD DS site. The proposed correction is: Correct subnet-to-site mappings and verify domain controller selection. Which technical principle best supports that correction? The site locator uses subnet membership to select nearby directory services. Client locator behavior depends on matching network subnets to directory sites. Cloud virtual NIC addresses must be valid and unique in their subnet. Subnet boundaries must be consistent across addressing and routing systems. ExplanationCorrect Answer A:The site locator uses subnet membership to select nearby directory services. This principle explains why the proposed response is appropriate: Correct subnet-to-site mappings and verify domain controller selection. In this situation, confirm success by checking: Newly moved endpoints resolve to the geographically appropriate site.Incorrect Answers B:Client locator behavior depends on matching network subnets to directory sites. This does not establish the proposed intervention. The governing principle here is: The site locator uses subnet membership to select nearby directory services. Apply it by: Correct subnet-to-site mappings and verify domain controller selection. C:Cloud virtual NIC addresses must be valid and unique in their subnet. This does not establish the proposed intervention. The governing principle here is: The site locator uses subnet membership to select nearby directory services. Apply it by: Correct subnet-to-site mappings and verify domain controller selection. D:Subnet boundaries must be consistent across addressing and routing systems. This does not establish the proposed intervention. The governing principle here is: The site locator uses subnet membership to select nearby directory services. Apply it by: Correct subnet-to-site mappings and verify domain controller selection.
Question 395A build pipeline stores a container registry password in a plain-text Docker build argument. If this condition remains unresolved, which direct operational or security risk follows? Directory queries and credentials could be exposed to interception. Deleting the last known-good image could prolong outage recovery. Downstream users of the image could recover service credentials. Management credentials or commands could reach an impostor. ExplanationCorrect Answer C:Downstream users of the image could recover service credentials. This is the direct remaining operational, security, or availability consequence of the stated problem. The corrective action would be: Use a supported secret injection method that avoids persisting tokens into image layers. Supporting principle: Build-time credentials must not be embedded in distributable layers.Incorrect Answers A:Directory authentication traffic should be protected in transit. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Downstream users of the image could recover service credentials. B:Image lifecycle management must preserve recoverability of deployed workloads. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Downstream users of the image could recover service credentials. D:Remote shell trust requires identifying the intended server before privileged operations. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Downstream users of the image could recover service credentials.
Question 396A hybrid Azure Files workload uses a public endpoint despite an approved private connectivity requirement. If this condition remains unresolved, which direct operational or security risk follows? Branch traffic could fail or attempt the public endpoint. Traffic could reach unready instances and fail. Sensitive file traffic could traverse an unapproved route. Full local storage could interrupt uploads and file operations. ExplanationCorrect Answer C:Sensitive file traffic could traverse an unapproved route. This is the direct remaining operational, security, or availability consequence of the stated problem. The corrective action would be: Configure private endpoint connectivity and corresponding DNS resolution. Supporting principle: Private file services depend on secure paths and correct private name resolution.Incorrect Answers A:Private endpoint resolution requires consistent paths across connected networks. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Sensitive file traffic could traverse an unapproved route. B:Container process liveness differs from application readiness. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Sensitive file traffic could traverse an unapproved route. D:Synchronized file servers still require healthy local volume capacity. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Sensitive file traffic could traverse an unapproved route.
Question 397A restore plan proposes rolling back a domain controller VM snapshot from months ago without checking safe recovery policy. The proposed correction is: Use Microsoft-supported AD DS restore or recovery procedures rather than arbitrary old snapshot rollback. Which technical principle best supports that correction? Remote access addressing must be unique and authorization-aware. Name-resolution forwarding graphs must terminate at an authoritative answer. Directory restoration needs replication-aware consistency and authoritative recovery decisions. Scheduled site-link replication balances consistency against constrained WAN capacity. ExplanationCorrect Answer C:Directory restoration needs replication-aware consistency and authoritative recovery decisions. This principle explains why the proposed response is appropriate: Use Microsoft-supported AD DS restore or recovery procedures rather than arbitrary old snapshot rollback. In this situation, confirm success by checking: The restored directory state synchronizes without obsolete object versions or replication errors.Incorrect Answers A:Remote access addressing must be unique and authorization-aware. This does not establish the proposed intervention. The governing principle here is: Directory restoration needs replication-aware consistency and authoritative recovery decisions. Apply it by: Use Microsoft-supported AD DS restore or recovery procedures rather than arbitrary old snapshot rollback. B:Name-resolution forwarding graphs must terminate at an authoritative answer. This does not establish the proposed intervention. The governing principle here is: Directory restoration needs replication-aware consistency and authoritative recovery decisions. Apply it by: Use Microsoft-supported AD DS restore or recovery procedures rather than arbitrary old snapshot rollback. D:Scheduled site-link replication balances consistency against constrained WAN capacity. This does not establish the proposed intervention. The governing principle here is: Directory restoration needs replication-aware consistency and authoritative recovery decisions. Apply it by: Use Microsoft-supported AD DS restore or recovery procedures rather than arbitrary old snapshot rollback.
Question 398A project grants a universal group write access in many domains without ownership review. The proposed correction is: Map resource ownership and enforce appropriate delegated group and ACL boundaries. Which technical principle best supports that correction? Privileged remote access should expire when the task authorization ends. Authorization is the combined outcome of group scope and resource permissions. Azure governance applies through resource hierarchy and tags. Group Policy processing follows link order, scope, inheritance, and filtering. ExplanationCorrect Answer B:Authorization is the combined outcome of group scope and resource permissions. This principle explains why the proposed response is appropriate: Map resource ownership and enforce appropriate delegated group and ACL boundaries. In this situation, confirm success by checking: Test accounts can modify only their assigned domain resources.Incorrect Answers A:Privileged remote access should expire when the task authorization ends. This does not establish the proposed intervention. The governing principle here is: Authorization is the combined outcome of group scope and resource permissions. Apply it by: Map resource ownership and enforce appropriate delegated group and ACL boundaries. C:Azure governance applies through resource hierarchy and tags. This does not establish the proposed intervention. The governing principle here is: Authorization is the combined outcome of group scope and resource permissions. Apply it by: Map resource ownership and enforce appropriate delegated group and ACL boundaries. D:Group Policy processing follows link order, scope, inheritance, and filtering. This does not establish the proposed intervention. The governing principle here is: Authorization is the combined outcome of group scope and resource permissions. Apply it by: Map resource ownership and enforce appropriate delegated group and ACL boundaries.
Question 399A domain administrator edits a central store policy template on one controller without coordinating updates. The proposed correction is: Maintain versioned approved ADMX templates and distribute via supported central store workflow. Which technical principle best supports that correction? Private endpoint resolution requires consistent paths across connected networks. Kubernetes worker connectivity depends on consistent node and network setup. Centralized policy definitions should be consistent across administrators. GPO delivery relies on consistent SYSVOL replication state. ExplanationCorrect Answer C:Centralized policy definitions should be consistent across administrators. This principle explains why the proposed response is appropriate: Maintain versioned approved ADMX templates and distribute via supported central store workflow. In this situation, confirm success by checking: Multiple consoles show the same approved policy definitions.Incorrect Answers A:Private endpoint resolution requires consistent paths across connected networks. This does not establish the proposed intervention. The governing principle here is: Centralized policy definitions should be consistent across administrators. Apply it by: Maintain versioned approved ADMX templates and distribute via supported central store workflow. B:Kubernetes worker connectivity depends on consistent node and network setup. This does not establish the proposed intervention. The governing principle here is: Centralized policy definitions should be consistent across administrators. Apply it by: Maintain versioned approved ADMX templates and distribute via supported central store workflow. D:GPO delivery relies on consistent SYSVOL replication state. This does not establish the proposed intervention. The governing principle here is: Centralized policy definitions should be consistent across administrators. Apply it by: Maintain versioned approved ADMX templates and distribute via supported central store workflow.
Question 400A data center decommissions a domain controller by deleting its virtual machine before demotion. After this proposed change — Properly demote the controller and validate directory metadata and DNS cleanup. — which observation most directly confirms it worked? Inventory reports distinct VM IDs and independent management operations. Repadmin and directory inventory no longer report the removed controller. A simulated controller shutdown leaves sign-in and directory queries available. Several test guests each report their allocated GPU capacity. ExplanationCorrect Answer B:Repadmin and directory inventory no longer report the removed controller. This is the closest operational evidence for the proposed remediation: Properly demote the controller and validate directory metadata and DNS cleanup. It tests the principle: Domain controller retirement must remove service identity and replication references.Incorrect Answers A:Virtual machine lifecycle relies on unique metadata identities. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Repadmin and directory inventory no longer report the removed controller. C:Directory availability depends on replicated controllers rather than one physical host. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Repadmin and directory inventory no longer report the removed controller. D:GPU partitioning and direct device assignment provide different allocation models. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Repadmin and directory inventory no longer report the removed controller.