Microsoft AZ-800 Practice Test 45 - 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 45

Question 440

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 Windows container application listens internally yet external client traffic cannot reach it from the campus network. The evidence is: Port mapping and NAT inspection show the service port is not published on the reachable Windows container host interface. 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: 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.
  2. Action: Pin the approved immutable image digest and control build promotion, signing and vulnerability verification. Evidence of success: Both hosts run the same approved digest and reproducible application tests pass after redeployment.
  3. Action: Evaluate availability-zone or region resilience requirements and implement the authorized redundancy architecture. Evidence of success: A planned failure experiment demonstrates the application meets the intended fault-domain availability target.
  4. Action: Configure the supported NAT or appropriate virtual network port publication and a narrowly scoped firewall path. Evidence of success: A designated client reaches the published service while unapproved container ports remain inaccessible.

Explanation

Correct Answer

D:

Port mapping and NAT inspection show the service port is not published on the reachable Windows container host interface. The paired remediation and acceptance test for Summit Virtual Security is Action: Configure the supported NAT or appropriate virtual network port publication and a narrowly scoped firewall path. Evidence of success: A designated client reaches the published service while unapproved container ports remain inaccessible. The check is meaningful because success requires that a designated client reaches the published service while unapproved container ports remain inaccessible.

Incorrect Answers

A:

That action and check pair is 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. It does not connect both parts to the actual Summit Virtual Security clue: Port mapping and NAT inspection show the service port is not published on the reachable Windows container host interface. The acceptance test needs to show that a designated client reaches the published service while unapproved container ports remain inaccessible.

B:

The paired proposal is Action: Pin the approved immutable image digest and control build promotion, signing and vulnerability verification. Evidence of success: Both hosts run the same approved digest and reproducible application tests pass after redeployment. For Summit Virtual Security, it fails to establish an intervention and check for the documented issue, where a Windows container application listens internally yet external client traffic cannot reach it from the campus network. Successful closure requires that a designated client reaches the published service while unapproved container ports remain inaccessible.

C:

At Summit Virtual Security, the option couples action: Evaluate availability-zone or region resilience requirements and implement the authorized redundancy architecture. Evidence of success: A planned failure experiment demonstrates the application meets the intended fault-domain availability target. Its test does not independently demonstrate that a designated client reaches the published service while unapproved container ports remain inaccessible. The deciding case evidence is that port mapping and NAT inspection show the service port is not published on the reachable Windows container host interface.

Question 441

At Northgate Azure Compute, the team supports Windows Server VMs across Azure networks and zones and must validate capacity, networking and approved management channels. Confirmed original fault: A hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. Supporting diagnostic evidence: Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. A bounded change is required. Which appropriately scoped Windows Server or hybrid administration correction most directly addresses this specific failure?

  1. Validate host attestation and authorized guardian or key protector configuration before moving the protected workload.
  2. Use a supported Linux-capable runtime such as an approved WSL2 Linux execution environment or separate Linux nodes.
  3. Restore the supported approved Bastion subnet, routing and private RDP access path without opening public RDP.
  4. Correct only the intended NIC/subnet route and NSG rules to permit designated directory services.

Explanation

Correct Answer

B:

At Northgate Azure Compute, the relevant observation is that runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. The direct correction is to use a supported Linux-capable runtime such as an approved WSL2 Linux execution environment or separate Linux nodes. Container images and hosts must agree on operating system and execution isolation capabilities. Verify that the workload runs on the compatible Linux platform without bypassing host support policy.

Incorrect Answers

A:

The failure at Northgate Azure Compute is that a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. That does not call for validate host attestation and authorized guardian or key protector configuration before moving the protected workload. The case evidence instead establishes that runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform.

C:

That alternative would restore the supported approved Bastion subnet, routing and private RDP access path without opening public RDP. For Northgate Azure Compute, that does not follow the diagnostic finding that runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. The relevant principle is that container images and hosts must agree on operating system and execution isolation capabilities.

D:

Proposing to correct only the intended NIC/subnet route and NSG rules to permit designated directory services does not fit the evidence at Northgate Azure Compute: Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. That would not resolve the original failure: a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer.

Question 442

At Northgate Azure Compute, the team supports Windows Server VMs across Azure networks and zones and must validate capacity, networking and approved management channels. A reported incident states: A hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. 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. Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform.
  2. Port mapping and NAT inspection show the service port is not published on the reachable Windows container host interface.
  3. The deployment error identifies a zone SKU capacity or quota limitation, not a guest Windows failure.
  4. Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC.

Explanation

Correct Answer

A:

At Northgate Azure Compute, the distinguishing evidence is: Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. It is directly connected to a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. Container images and hosts must agree on operating system and execution isolation capabilities.

Incorrect Answers

B:

For Northgate Azure Compute, the proposed observation is that port mapping and NAT inspection show the service port is not published on the reachable Windows container host interface. It would not distinguish the identified failure, where a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. The meaningful clue is that runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform.

C:

The observation offered is that the deployment error identifies a zone SKU capacity or quota limitation, not a guest Windows failure. It does not substantiate the reported Northgate Azure Compute failure, where a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. The directly relevant diagnostic record is that runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform.

D:

The suggested evidence is that bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. In the Northgate Azure Compute case, the actual distinguishing finding is that runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. Container images and hosts must agree on operating system and execution isolation capabilities.

Question 443

At Northgate Azure Compute, the team supports Windows Server VMs across Azure networks and zones and must validate capacity, networking and approved management channels. Observed issue: A hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. Investigation found: Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. The proposed repair is: Use a supported Linux-capable runtime such as an approved WSL2 Linux execution environment or separate Linux nodes. Which independently observable result best verifies resolution of the stated Windows Server problem?

  1. The workload runs on the compatible Linux platform without bypassing host support policy.
  2. An application-level recovery rehearsal restores consistent data while separately maintained services retain their intended transaction state.
  3. The shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts.
  4. A designated client reaches the published service while unapproved container ports remain inaccessible.

Explanation

Correct Answer

A:

For Northgate Azure Compute, the offered check would demonstrate that the workload runs on the compatible Linux platform without bypassing host support policy. It evaluates the actual failure, where a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. Container images and hosts must agree on operating system and execution isolation capabilities.

Incorrect Answers

B:

This check suggests that an application-level recovery rehearsal restores consistent data while separately maintained services retain their intended transaction state. It does not test the resolution criterion for Northgate Azure Compute, namely that the workload runs on the compatible Linux platform without bypassing host support policy. Container images and hosts must agree on operating system and execution isolation capabilities.

C:

The option would validate that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts. That does not establish correction of the Northgate Azure Compute issue, where a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. The meaningful proof is that the workload runs on the compatible Linux platform without bypassing host support policy.

D:

The alternative test result is that a designated client reaches the published service while unapproved container ports remain inaccessible. It does not prove recovery of the Northgate Azure Compute failure, where a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. A relevant acceptance result would show that the workload runs on the compatible Linux platform without bypassing host support policy.

Question 444

At Northgate Azure Compute, the team supports Windows Server VMs across Azure networks and zones and must validate capacity, networking and approved management channels. The administrator observes: A hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. The distinguishing clue is: Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. 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. Dynamic memory capacity must be engineered against both guest demand and available physical host resources.
  2. Container images and hosts must agree on operating system and execution isolation capabilities.
  3. Live migration must account for processor compatibility as well as network and shared storage prerequisites.
  4. Azure VM sizing depends on both subscription constraints and physical regional or zonal SKU availability.

Explanation

Correct Answer

B:

The engineering rationale is that container images and hosts must agree on operating system and execution isolation capabilities. It is relevant at Northgate Azure Compute because runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. The failure to explain is that a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer.

Incorrect Answers

A:

This offered mechanism, dynamic memory capacity must be engineered against both guest demand and available physical host resources, does not match the specific recorded failure at Northgate Azure Compute, where a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. The relevant principle is that container images and hosts must agree on operating system and execution isolation capabilities.

C:

The alternate technical explanation says that live migration must account for processor compatibility as well as network and shared storage prerequisites. It is not the mechanism identified by the Northgate Azure Compute record: Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. Container images and hosts must agree on operating system and execution isolation capabilities.

D:

The case at Northgate Azure Compute is that a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. The offered principle, azure VM sizing depends on both subscription constraints and physical regional or zonal SKU availability, would not explain this observed failure. The relevant mechanism is that container images and hosts must agree on operating system and execution isolation capabilities.

Question 445

At Northgate Azure Compute, the team supports Windows Server VMs across Azure networks and zones and must validate capacity, networking and approved management channels. The original incident is: A hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. The evidence is: Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. 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: 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.
  2. 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.
  3. 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.
  4. Action: Pin the approved immutable image digest and control build promotion, signing and vulnerability verification. Evidence of success: Both hosts run the same approved digest and reproducible application tests pass after redeployment.

Explanation

Correct Answer

A:

At Northgate Azure Compute, the offered pair combines a relevant intervention with proof: 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. It responds to the evidence that runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. A successful result should establish that the workload runs on the compatible Linux platform without bypassing host support policy.

Incorrect Answers

B:

At Northgate Azure Compute, 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 workload runs on the compatible Linux platform without bypassing host support policy. The deciding case evidence is that runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform.

C:

This offered change and proof, 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, would leave the Northgate Azure Compute case unverified. The actual recorded fault is that a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. A meaningful check requires that the workload runs on the compatible Linux platform without bypassing host support policy.

D:

The alternative combined step is Action: Pin the approved immutable image digest and control build promotion, signing and vulnerability verification. Evidence of success: Both hosts run the same approved digest and reproducible application tests pass after redeployment. The relevant Northgate Azure Compute evidence is that runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. Closure must validate that the workload runs on the compatible Linux platform without bypassing host support policy, rather than a different symptom.

Question 446

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 hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. Supporting diagnostic evidence: Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. A bounded change is required. Which appropriately scoped Windows Server or hybrid administration correction most directly addresses this specific failure?

  1. Use a supported Linux-capable runtime such as an approved WSL2 Linux execution environment or separate Linux nodes.
  2. Bind the switch to the approved physical path and validate VLAN configuration and host management connectivity.
  3. Select a supported compatible image and host version or an appropriate supported Hyper-V isolation configuration.
  4. Restore the supported approved Bastion subnet, routing and private RDP access path without opening public RDP.

Explanation

Correct Answer

A:

At Summit Virtual Security, the relevant observation is that runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. The direct correction is to use a supported Linux-capable runtime such as an approved WSL2 Linux execution environment or separate Linux nodes. Container images and hosts must agree on operating system and execution isolation capabilities. Verify that the workload runs on the compatible Linux platform without bypassing host support policy.

Incorrect Answers

B:

That alternative would bind the switch to the approved physical path and validate VLAN configuration and host management connectivity. For Summit Virtual Security, that does not follow the diagnostic finding that runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. The relevant principle is that container images and hosts must agree on operating system and execution isolation capabilities.

C:

Proposing to select a supported compatible image and host version or an appropriate supported Hyper-V isolation configuration does not fit the evidence at Summit Virtual Security: Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. That would not resolve the original failure: a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer.

D:

The issue at Summit Virtual Security is that a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. Acting to restore the supported approved Bastion subnet, routing and private RDP access path without opening public RDP would not correct the evidenced cause. The most relevant clue is that runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform.

Question 447

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 hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. 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. Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform.
  2. Migration precheck reports processor instruction set incompatibility and the hosts use different CPU feature levels.
  3. Cluster diagnostics show the target node lacks a supported Windows container runtime or required cluster networking components.
  4. Azure disk metrics show throttling at the assigned disk IOPS or throughput limit while processor counters remain normal.

Explanation

Correct Answer

A:

This observation is the appropriate evidence for Summit Virtual Security: Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. It explains the problem, where a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. Container images and hosts must agree on operating system and execution isolation capabilities.

Incorrect Answers

B:

The observation offered is that migration precheck reports processor instruction set incompatibility and the hosts use different CPU feature levels. It does not substantiate the reported Summit Virtual Security failure, where a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. The directly relevant diagnostic record is that runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform.

C:

The suggested evidence is that cluster diagnostics show the target node lacks a supported Windows container runtime or required cluster networking components. In the Summit Virtual Security case, the actual distinguishing finding is that runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. Container images and hosts must agree on operating system and execution isolation capabilities.

D:

At Summit Virtual Security, The alternative observation about azure disk metrics show throttling at the assigned disk IOPS or throughput limit while processor counters remain normal would not isolate the relevant problem. The diagnostic clue is that runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. This is the clue that bears on a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer.

Question 448

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 hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. Investigation found: Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. The proposed repair is: Use a supported Linux-capable runtime such as an approved WSL2 Linux execution environment or separate Linux nodes. 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. A designated client reaches the published service while unapproved container ports remain inaccessible.
  3. The replacement capacity is provisioned successfully and the application passes a controlled functional check.
  4. The workload runs on the compatible Linux platform without bypassing host support policy.

Explanation

Correct Answer

D:

At Summit Virtual Security, the selected verification result is that the workload runs on the compatible Linux platform without bypassing host support policy. This checks recovery of the reported issue, where a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. Container images and hosts must agree on operating system and execution isolation capabilities.

Incorrect Answers

A:

This check suggests that the image starts predictably in the approved runtime while the host remains on its supported maintenance baseline. It does not test the resolution criterion for Summit Virtual Security, namely that the workload runs on the compatible Linux platform without bypassing host support policy. Container images and hosts must agree on operating system and execution isolation capabilities.

B:

The option would validate that a designated client reaches the published service while unapproved container ports remain inaccessible. That does not establish correction of the Summit Virtual Security issue, where a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. The meaningful proof is that the workload runs on the compatible Linux platform without bypassing host support policy.

C:

The alternative test result is that the replacement capacity is provisioned successfully and the application passes a controlled functional check. It does not prove recovery of the Summit Virtual Security failure, where a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. A relevant acceptance result would show that the workload runs on the compatible Linux platform without bypassing host support policy.

Question 449

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 hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. The distinguishing clue is: Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. 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. Windows Kubernetes host readiness depends on matched runtime, networking and supported product versions.
  2. Azure VM sizing depends on both subscription constraints and physical regional or zonal SKU availability.
  3. Bastion eliminates a public VM management entry point but still requires private network reachability and access policy.
  4. Container images and hosts must agree on operating system and execution isolation capabilities.

Explanation

Correct Answer

D:

The appropriate mechanism for Summit Virtual Security is that container images and hosts must agree on operating system and execution isolation capabilities. This explains the recorded clue: Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. It accounts for the reported failure, where a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer.

Incorrect Answers

A:

At Summit Virtual Security, the reported clue is that runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. The principle of windows Kubernetes host readiness depends on matched runtime, networking and supported product versions does not explain that finding. The appropriate explanation is that container images and hosts must agree on operating system and execution isolation capabilities.

B:

The alternate technical explanation says that azure VM sizing depends on both subscription constraints and physical regional or zonal SKU availability. It is not the mechanism identified by the Summit Virtual Security record: Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. Container images and hosts must agree on operating system and execution isolation capabilities.

C:

The case at Summit Virtual Security is that a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. The offered principle, bastion eliminates a public VM management entry point but still requires private network reachability and access policy, would not explain this observed failure. The relevant mechanism is that container images and hosts must agree on operating system and execution isolation capabilities.

Question 450

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 hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. The evidence is: Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. 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: 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.
  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: Select a supported compatible image and host version or an appropriate supported Hyper-V isolation configuration. Evidence of success: The image starts predictably in the approved runtime while the host remains on its supported maintenance baseline.
  4. 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.

Explanation

Correct Answer

A:

The documented issue at Summit Virtual Security is that a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. The selected combined action and test 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. Its verification aligns with the required outcome: The workload runs on the compatible Linux platform without bypassing host support policy.

Incorrect Answers

B:

This offered change and proof, 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, would leave the Summit Virtual Security case unverified. The actual recorded fault is that a hybrid team schedules a Linux container workload on a Windows-only container runtime without a supported Linux execution layer. A meaningful check requires that the workload runs on the compatible Linux platform without bypassing host support policy.

C:

The alternative combined step is Action: Select a supported compatible image and host version or an appropriate supported Hyper-V isolation configuration. Evidence of success: The image starts predictably in the approved runtime while the host remains on its supported maintenance baseline. The relevant Summit Virtual Security evidence is that runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. Closure must validate that the workload runs on the compatible Linux platform without bypassing host support policy, rather than a different symptom.

D:

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 Summit Virtual Security condition: Runtime metadata indicates Windows OS images are expected while the selected image declares a Linux platform. The outcome to verify is that the workload runs on the compatible Linux platform without bypassing host support policy.

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