Microsoft AZ-800 Practice Test 41 - Prepaway
Practice Exams:

Pass Microsoft AZ-800 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium Bundle
$29.98
$79.99 $109.97

AZ-800 Premium Bundle


  • Premium File 311 Questions & Answers. Last update: Nov 12, 2026
  • Training Course 150 Lectures
  • Study Guide 430 Pages

Microsoft AZ-800 Practice Test 41

Question 400

At Cedarline Hyper-V Engineering, the team supports high-density Windows Server VM hosts and storage and must maintain resource isolation and workload-consistent recovery. The original incident is: A running virtual machine cannot live migrate between hosts of different processor generations even though both hosts see shared storage. The evidence is: Migration precheck reports processor instruction set incompatibility and the hosts use different CPU feature levels. A recovery is acceptable only with an appropriately scoped change and independently observable proof. Which paired action and verification most appropriately correct and confirm this Windows Server issue?

  1. Action: Bind the switch to the approved physical path and validate VLAN configuration and host management connectivity. Evidence of success: A test VM reaches the correct subnet and gateway while the Hyper-V host retains its dedicated management path.
  2. Action: Right-size the supported managed disk tier and VM throughput budget to observed workload performance requirements. Evidence of success: Representative write latency and throughput meet acceptance thresholds with stable disk throttling counters.
  3. Action: Assess supported processor compatibility settings and host capabilities before scheduling a controlled live migration. Evidence of success: A test workload moves between the designated hosts while preserving connectivity and required VM features.
  4. Action: Correct only the intended NIC/subnet route and NSG rules to permit designated directory services. Evidence of success: A controlled directory query from the VM succeeds and negative probes to unrelated restricted networks fail.

Explanation

Correct Answer

C:

This proposed change-and-check pair is tied to the Cedarline Hyper-V Engineering fault: Action: Assess supported processor compatibility settings and host capabilities before scheduling a controlled live migration. Evidence of success: A test workload moves between the designated hosts while preserving connectivity and required VM features. The diagnostic basis is that migration precheck reports processor instruction set incompatibility and the hosts use different CPU feature levels. The outcome must show that a test workload moves between the designated hosts while preserving connectivity and required VM features.

Incorrect Answers

A:

The alternative combined step is Action: Bind the switch to the approved physical path and validate VLAN configuration and host management connectivity. Evidence of success: A test VM reaches the correct subnet and gateway while the Hyper-V host retains its dedicated management path. The relevant Cedarline Hyper-V Engineering evidence is that migration precheck reports processor instruction set incompatibility and the hosts use different CPU feature levels. Closure must validate that a test workload moves between the designated hosts while preserving connectivity and required VM features, rather than a different symptom.

B:

The paired remediation states Action: Right-size the supported managed disk tier and VM throughput budget to observed workload performance requirements. Evidence of success: Representative write latency and throughput meet acceptance thresholds with stable disk throttling counters. It does not test correction of the Cedarline Hyper-V Engineering condition: Migration precheck reports processor instruction set incompatibility and the hosts use different CPU feature levels. The outcome to verify is that a test workload moves between the designated hosts while preserving connectivity and required VM features.

D:

The paired proposal is Action: Correct only the intended NIC/subnet route and NSG rules to permit designated directory services. Evidence of success: A controlled directory query from the VM succeeds and negative probes to unrelated restricted networks fail. For Cedarline Hyper-V Engineering, it fails to establish an intervention and check for the documented issue, where a running virtual machine cannot live migrate between hosts of different processor generations even though both hosts see shared storage. Successful closure requires that a test workload moves between the designated hosts while preserving connectivity and required VM features.

Question 401

At Summit Virtual Security, the team supports protected Hyper-V guests and operational migration and must maintain guarded-host trust and change-safe mobility. Confirmed original fault: A shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. Supporting diagnostic evidence: Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. A bounded change is required. Which appropriately scoped Windows Server or hybrid administration correction most directly addresses this specific failure?

  1. Select a supported compatible image and host version or an appropriate supported Hyper-V isolation configuration.
  2. Validate host attestation and authorized guardian or key protector configuration before moving the protected workload.
  3. Pin the approved immutable image digest and control build promotion, signing and vulnerability verification.
  4. Correct only the intended NIC/subnet route and NSG rules to permit designated directory services.

Explanation

Correct Answer

B:

The available evidence is that host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. Summit Virtual Security needs to validate host attestation and authorized guardian or key protector configuration before moving the protected workload. Shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access. Confirmation would be that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts.

Incorrect Answers

A:

The issue at Summit Virtual Security is that a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. Acting to select a supported compatible image and host version or an appropriate supported Hyper-V isolation configuration would not correct the evidenced cause. The most relevant clue is that host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host.

C:

The failure at Summit Virtual Security is that a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. That does not call for pin the approved immutable image digest and control build promotion, signing and vulnerability verification. The case evidence instead establishes that host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host.

D:

At Summit Virtual Security, proposing to correct only the intended NIC/subnet route and NSG rules to permit designated directory services would not address the recorded evidence: Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. The case instead needs an intervention related to a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. Shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access.

Question 402

At Summit Virtual Security, the team supports protected Hyper-V guests and operational migration and must maintain guarded-host trust and change-safe mobility. A reported incident states: A shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. Before changing the environment, the team must distinguish among plausible technical causes. Which observation most decisively distinguishes this specific Windows Server failure from other problems?

  1. Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host.
  2. Port mapping and NAT inspection show the service port is not published on the reachable Windows container host interface.
  3. Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform.
  4. Deployment metadata confirms both VMs share the same zone and only fault/update-domain distribution is configured.

Explanation

Correct Answer

A:

For Summit Virtual Security, this is the discriminating finding: Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. It accounts for the reported problem, where a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. Shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access.

Incorrect Answers

B:

An unrelated diagnosis would involve: Port mapping and NAT inspection show the service port is not published on the reachable Windows container host interface. The incident at Summit Virtual Security is that a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. The decisive finding instead is that host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host.

C:

This observation, runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform, does not match the evidence in the Summit Virtual Security record. Instead, the record shows that host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. Shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access.

D:

For Summit Virtual Security, the proposed observation is that deployment metadata confirms both VMs share the same zone and only fault/update-domain distribution is configured. It would not distinguish the identified failure, where a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. The meaningful clue is that host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host.

Question 403

At Summit Virtual Security, the team supports protected Hyper-V guests and operational migration and must maintain guarded-host trust and change-safe mobility. Observed issue: A shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. Investigation found: Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. The proposed repair is: Validate host attestation and authorized guardian or key protector configuration before moving the protected workload. Which independently observable result best verifies resolution of the stated Windows Server problem?

  1. An application-level recovery rehearsal restores consistent data while separately maintained services retain their intended transaction state.
  2. The guest starts and sustains representative application load without pathological memory pressure or exhausting host capacity.
  3. Representative write latency and throughput meet acceptance thresholds with stable disk throttling counters.
  4. The shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts.

Explanation

Correct Answer

D:

The verification signal is that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts. It connects the proposed correction to the recorded diagnostic clue at Summit Virtual Security: Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. Shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access.

Incorrect Answers

A:

The alternative validation would show that an application-level recovery rehearsal restores consistent data while separately maintained services retain their intended transaction state. For Summit Virtual Security, that is insufficient to establish that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts. The original diagnostic finding is that host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host.

B:

At Summit Virtual Security, a test showing that the guest starts and sustains representative application load without pathological memory pressure or exhausting host capacity would not confirm the needed outcome. The check must demonstrate that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts. It must address the failure, where a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh.

C:

That verification is that representative write latency and throughput meet acceptance thresholds with stable disk throttling counters. The Summit Virtual Security acceptance criterion is instead that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts. The recorded causal clue is that host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host.

Question 404

At Summit Virtual Security, the team supports protected Hyper-V guests and operational migration and must maintain guarded-host trust and change-safe mobility. The administrator observes: A shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. The distinguishing clue is: Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. The team wants a causal explanation, not a generic remedy. Which Windows Server, identity, network, compute or storage principle best explains the identified failure?

  1. Shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access.
  2. Hyper-V checkpoints capture VM state and are not substitutes for workload-consistent backups or distributed transaction recovery.
  3. Windows Kubernetes host readiness depends on matched runtime, networking and supported product versions.
  4. Azure virtual machine connectivity is enforced by effective cloud NIC and subnet controls in addition to guest settings.

Explanation

Correct Answer

A:

The appropriate mechanism for Summit Virtual Security is that shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access. This explains the recorded clue: Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. It accounts for the reported failure, where a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh.

Incorrect Answers

B:

The alternative principle is that hyper-V checkpoints capture VM state and are not substitutes for workload-consistent backups or distributed transaction recovery. For Summit Virtual Security, it does not explain why host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. The applicable causal rule is that shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access.

C:

This offered mechanism, windows Kubernetes host readiness depends on matched runtime, networking and supported product versions, does not match the specific recorded failure at Summit Virtual Security, where a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. The relevant principle is that shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access.

D:

At Summit Virtual Security, the reported clue is that host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. The principle of azure virtual machine connectivity is enforced by effective cloud NIC and subnet controls in addition to guest settings does not explain that finding. The appropriate explanation is that shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access.

Question 405

At Summit Virtual Security, the team supports protected Hyper-V guests and operational migration and must maintain guarded-host trust and change-safe mobility. The original incident is: A shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. The evidence is: Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. A recovery is acceptable only with an appropriately scoped change and independently observable proof. Which paired action and verification most appropriately correct and confirm this Windows Server issue?

  1. Action: Set workload-tested dynamic memory startup, minimum and maximum values while accounting for host contention. Evidence of success: The guest starts and sustains representative application load without pathological memory pressure or exhausting host capacity.
  2. Action: Validate host attestation and authorized guardian or key protector configuration before moving the protected workload. Evidence of success: The shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts.
  3. Action: Use a supported Linux-capable runtime such as an approved WSL2 Linux execution environment or separate Linux nodes. Evidence of success: The workload runs on the compatible Linux platform without bypassing host support policy.
  4. Action: Restore the supported approved Bastion subnet, routing and private RDP access path without opening public RDP. Evidence of success: A named authorized operator connects through Bastion while direct internet RDP is still denied.

Explanation

Correct Answer

B:

This proposed change-and-check pair is tied to the Summit Virtual Security fault: Action: Validate host attestation and authorized guardian or key protector configuration before moving the protected workload. Evidence of success: The shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts. The diagnostic basis is that host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. The outcome must show that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts.

Incorrect Answers

A:

The paired remediation states Action: Set workload-tested dynamic memory startup, minimum and maximum values while accounting for host contention. Evidence of success: The guest starts and sustains representative application load without pathological memory pressure or exhausting host capacity. It does not test correction of the Summit Virtual Security condition: Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. The outcome to verify is that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts.

C:

The paired proposal is Action: Use a supported Linux-capable runtime such as an approved WSL2 Linux execution environment or separate Linux nodes. Evidence of success: The workload runs on the compatible Linux platform without bypassing host support policy. For Summit Virtual Security, it fails to establish an intervention and check for the documented issue, where a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. Successful closure requires that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts.

D:

At Summit Virtual Security, the option couples action: Restore the supported approved Bastion subnet, routing and private RDP access path without opening public RDP. Evidence of success: A named authorized operator connects through Bastion while direct internet RDP is still denied. Its test does not independently demonstrate that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts. The deciding case evidence is that host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host.

Question 406

At Cedarline Hyper-V Engineering, the team supports high-density Windows Server VM hosts and storage and must maintain resource isolation and workload-consistent recovery. Confirmed original fault: A shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. Supporting diagnostic evidence: Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. A bounded change is required. Which appropriately scoped Windows Server or hybrid administration correction most directly addresses this specific failure?

  1. Set workload-tested dynamic memory startup, minimum and maximum values while accounting for host contention.
  2. Evaluate availability-zone or region resilience requirements and implement the authorized redundancy architecture.
  3. Restore the supported approved Bastion subnet, routing and private RDP access path without opening public RDP.
  4. Validate host attestation and authorized guardian or key protector configuration before moving the protected workload.

Explanation

Correct Answer

D:

At Cedarline Hyper-V Engineering, host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. The fitting correction is to validate host attestation and authorized guardian or key protector configuration before moving the protected workload. Shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access. The acceptance check is that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts.

Incorrect Answers

A:

That alternative would set workload-tested dynamic memory startup, minimum and maximum values while accounting for host contention. It misses the condition observed at Cedarline Hyper-V Engineering: Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. The recommended correction addresses the observed condition directly.

B:

The failure at Cedarline Hyper-V Engineering is that a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. That does not call for evaluate availability-zone or region resilience requirements and implement the authorized redundancy architecture. The case evidence instead establishes that host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host.

C:

At Cedarline Hyper-V Engineering, proposing to restore the supported approved Bastion subnet, routing and private RDP access path without opening public RDP would not address the recorded evidence: Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. The case instead needs an intervention related to a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. Shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access.

Question 407

At Cedarline Hyper-V Engineering, the team supports high-density Windows Server VM hosts and storage and must maintain resource isolation and workload-consistent recovery. A reported incident states: A shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. Before changing the environment, the team must distinguish among plausible technical causes. Which observation most decisively distinguishes this specific Windows Server failure from other problems?

  1. Migration precheck reports processor instruction set incompatibility and the hosts use different CPU feature levels.
  2. Container runtime messages identify host-image Windows kernel build incompatibility under process isolation.
  3. Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host.
  4. Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform.

Explanation

Correct Answer

C:

This observation is the appropriate evidence for Cedarline Hyper-V Engineering: Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. It explains the problem, where a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. Shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access.

Incorrect Answers

A:

An unrelated diagnosis would involve: Migration precheck reports processor instruction set incompatibility and the hosts use different CPU feature levels. The incident at Cedarline Hyper-V Engineering is that a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. The decisive finding instead is that host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host.

B:

This observation, container runtime messages identify host-image Windows kernel build incompatibility under process isolation, does not match the evidence in the Cedarline Hyper-V Engineering record. Instead, the record shows that host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. Shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access.

D:

The observation offered is that runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. It does not substantiate the reported Cedarline Hyper-V Engineering failure, where a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. The directly relevant diagnostic record is that host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host.

Question 408

At Cedarline Hyper-V Engineering, the team supports high-density Windows Server VM hosts and storage and must maintain resource isolation and workload-consistent recovery. Observed issue: A shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. Investigation found: Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. The proposed repair is: Validate host attestation and authorized guardian or key protector configuration before moving the protected workload. Which independently observable result best verifies resolution of the stated Windows Server problem?

  1. The image starts predictably in the approved runtime while the host remains on its supported maintenance baseline.
  2. The shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts.
  3. The workload runs on the compatible Linux platform without bypassing host support policy.
  4. The replacement capacity is provisioned successfully and the application passes a controlled functional check.

Explanation

Correct Answer

B:

For Cedarline Hyper-V Engineering, the offered check would demonstrate that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts. It evaluates the actual failure, where a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. Shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access.

Incorrect Answers

A:

At Cedarline Hyper-V Engineering, a test showing that the image starts predictably in the approved runtime while the host remains on its supported maintenance baseline would not confirm the needed outcome. The check must demonstrate that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts. It must address the failure, where a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh.

C:

This check suggests that the workload runs on the compatible Linux platform without bypassing host support policy. It does not test the resolution criterion for Cedarline Hyper-V Engineering, namely that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts. Shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access.

D:

The option would validate that the replacement capacity is provisioned successfully and the application passes a controlled functional check. That does not establish correction of the Cedarline Hyper-V Engineering issue, where a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. The meaningful proof is that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts.

Question 409

At Cedarline Hyper-V Engineering, the team supports high-density Windows Server VM hosts and storage and must maintain resource isolation and workload-consistent recovery. The administrator observes: A shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. The distinguishing clue is: Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. The team wants a causal explanation, not a generic remedy. Which Windows Server, identity, network, compute or storage principle best explains the identified failure?

  1. Shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access.
  2. Container networking isolates endpoints unless reachable service ports and routes are explicitly designed.
  3. Azure VM storage throughput is constrained by both disk service limits and VM size capabilities.
  4. Bastion eliminates a public VM management entry point but still requires private network reachability and access policy.

Explanation

Correct Answer

A:

The selected principle is that shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access. It fits the Cedarline Hyper-V Engineering case because host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. The reported failure is that a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh.

Incorrect Answers

B:

This offered mechanism, container networking isolates endpoints unless reachable service ports and routes are explicitly designed, does not match the specific recorded failure at Cedarline Hyper-V Engineering, where a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. The relevant principle is that shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access.

C:

At Cedarline Hyper-V Engineering, the reported clue is that host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. The principle of azure VM storage throughput is constrained by both disk service limits and VM size capabilities does not explain that finding. The appropriate explanation is that shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access.

D:

The alternate technical explanation says that bastion eliminates a public VM management entry point but still requires private network reachability and access policy. It is not the mechanism identified by the Cedarline Hyper-V Engineering record: Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. Shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access.

Question 410

At Cedarline Hyper-V Engineering, the team supports high-density Windows Server VM hosts and storage and must maintain resource isolation and workload-consistent recovery. The original incident is: A shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. The evidence is: Host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. A recovery is acceptable only with an appropriately scoped change and independently observable proof. Which paired action and verification most appropriately correct and confirm this Windows Server issue?

  1. Action: Validate host attestation and authorized guardian or key protector configuration before moving the protected workload. Evidence of success: The shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts.
  2. Action: Use application-aware recovery, production checkpoints where supported, and documented guest backup semantics rather than assuming any checkpoint is a full backup. Evidence of success: An application-level recovery rehearsal restores consistent data while separately maintained services retain their intended transaction state.
  3. Action: Bind the switch to the approved physical path and validate VLAN configuration and host management connectivity. Evidence of success: A test VM reaches the correct subnet and gateway while the Hyper-V host retains its dedicated management path.
  4. Action: Validate the retired-outline lab's supported product version and configure compatible node prerequisites in a nonproduction environment. Evidence of success: A test Windows container pod reaches Ready state on a supported node with known compatible runtime and network configuration.

Explanation

Correct Answer

A:

This proposed change-and-check pair is tied to the Cedarline Hyper-V Engineering fault: Action: Validate host attestation and authorized guardian or key protector configuration before moving the protected workload. Evidence of success: The shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts. The diagnostic basis is that host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host. The outcome must show that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts.

Incorrect Answers

B:

The paired proposal is Action: Use application-aware recovery, production checkpoints where supported, and documented guest backup semantics rather than assuming any checkpoint is a full backup. Evidence of success: An application-level recovery rehearsal restores consistent data while separately maintained services retain their intended transaction state. For Cedarline Hyper-V Engineering, it fails to establish an intervention and check for the documented issue, where a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. Successful closure requires that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts.

C:

At Cedarline Hyper-V Engineering, the option couples action: Bind the switch to the approved physical path and validate VLAN configuration and host management connectivity. Evidence of success: A test VM reaches the correct subnet and gateway while the Hyper-V host retains its dedicated management path. Its test does not independently demonstrate that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts. The deciding case evidence is that host guardian attestation fails or the required key protector is not trusted by the new guarded fabric host.

D:

This offered change and proof, action: Validate the retired-outline lab's supported product version and configure compatible node prerequisites in a nonproduction environment. Evidence of success: A test Windows container pod reaches Ready state on a supported node with known compatible runtime and network configuration, would leave the Cedarline Hyper-V Engineering case unverified. The actual recorded fault is that a shielded VM cannot start on a replacement Hyper-V host after an unplanned hardware refresh. A meaningful check requires that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts.

Administering Windows Server Hybrid Core Infrastructure (AZ-800) Practice Tests