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

Question 420

At Pinebrook Container Platform, the team supports Windows container images and host runtimes and must pin supported OS and image versions with auditable deployment. The original incident is: A Windows Server container image starts on a developer PC but repeatedly exits on the production container host with a different build. The evidence is: Container runtime messages identify host-image Windows kernel build incompatibility under process isolation. 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: 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.
  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: 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:

Container runtime messages identify host-image Windows kernel build incompatibility under process isolation. The paired remediation and acceptance test for Pinebrook Container Platform 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 check is meaningful because success requires that the image starts predictably in the approved runtime while the host remains on its supported maintenance baseline.

Incorrect Answers

A:

At Pinebrook Container Platform, the option couples 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. Its test does not independently demonstrate that the image starts predictably in the approved runtime while the host remains on its supported maintenance baseline. The deciding case evidence is that container runtime messages identify host-image Windows kernel build incompatibility under process isolation.

C:

The alternative combined step is 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 relevant Pinebrook Container Platform evidence is that container runtime messages identify host-image Windows kernel build incompatibility under process isolation. Closure must validate that the image starts predictably in the approved runtime while the host remains on its supported maintenance baseline, rather than a different symptom.

D:

The paired remediation states 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. It does not test correction of the Pinebrook Container Platform condition: Container runtime messages identify host-image Windows kernel build incompatibility under process isolation. The outcome to verify is that the image starts predictably in the approved runtime while the host remains on its supported maintenance baseline.

Question 421

At Harborview Virtual Networking, the team supports Hyper-V virtual switches and host adapters and must keep guest network reachability aligned with approved host paths. Confirmed original fault: Two Windows Server container hosts launch the same named image tag but execute different application dependencies. Supporting diagnostic evidence: Image digests differ across hosts because the floating tag was republished between deployments. 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. Pin the approved immutable image digest and control build promotion, signing and vulnerability verification.
  3. Validate the retired-outline lab's supported product version and configure compatible node prerequisites in a nonproduction environment.
  4. Right-size the supported managed disk tier and VM throughput budget to observed workload performance requirements.

Explanation

Correct Answer

B:

Image digests differ across hosts because the floating tag was republished between deployments. The appropriate scoped response for Harborview Virtual Networking is to pin the approved immutable image digest and control build promotion, signing and vulnerability verification. Container tags are mutable references and reproducible workloads should identify verified image artifacts. A separate test should confirm that both hosts run the same approved digest and reproducible application tests pass after redeployment.

Incorrect Answers

A:

That alternative would validate host attestation and authorized guardian or key protector configuration before moving the protected workload. For Harborview Virtual Networking, that does not follow the diagnostic finding that image digests differ across hosts because the floating tag was republished between deployments. The relevant principle is that container tags are mutable references and reproducible workloads should identify verified image artifacts.

C:

The issue at Harborview Virtual Networking is that two Windows Server container hosts launch the same named image tag but execute different application dependencies. Acting to validate the retired-outline lab's supported product version and configure compatible node prerequisites in a nonproduction environment would not correct the evidenced cause. The most relevant clue is that image digests differ across hosts because the floating tag was republished between deployments.

D:

That alternative would right-size the supported managed disk tier and VM throughput budget to observed workload performance requirements. It misses the condition observed at Harborview Virtual Networking: Image digests differ across hosts because the floating tag was republished between deployments. The recommended correction addresses the observed condition directly.

Question 422

At Harborview Virtual Networking, the team supports Hyper-V virtual switches and host adapters and must keep guest network reachability aligned with approved host paths. A reported incident states: Two Windows Server container hosts launch the same named image tag but execute different application dependencies. 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. Image digests differ across hosts because the floating tag was republished between deployments.
  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. Effective NSG rules or route tables on the VM NIC deny the required traffic though the guest IP configuration looks normal.

Explanation

Correct Answer

A:

At Harborview Virtual Networking, the selected observation is that image digests differ across hosts because the floating tag was republished between deployments. That evidence distinguishes the reported failure, where two Windows Server container hosts launch the same named image tag but execute different application dependencies. Container tags are mutable references and reproducible workloads should identify verified image artifacts.

Incorrect Answers

B:

The suggested evidence is that port mapping and NAT inspection show the service port is not published on the reachable Windows container host interface. In the Harborview Virtual Networking case, the actual distinguishing finding is that image digests differ across hosts because the floating tag was republished between deployments. Container tags are mutable references and reproducible workloads should identify verified image artifacts.

C:

At Harborview Virtual Networking, The alternative observation about the deployment error identifies a zone SKU capacity or quota limitation, not a guest Windows failure would not isolate the relevant problem. The diagnostic clue is that image digests differ across hosts because the floating tag was republished between deployments. This is the clue that bears on two Windows Server container hosts launch the same named image tag but execute different application dependencies.

D:

An unrelated diagnosis would involve: Effective NSG rules or route tables on the VM NIC deny the required traffic though the guest IP configuration looks normal. The incident at Harborview Virtual Networking is that two Windows Server container hosts launch the same named image tag but execute different application dependencies. The decisive finding instead is that image digests differ across hosts because the floating tag was republished between deployments.

Question 423

At Harborview Virtual Networking, the team supports Hyper-V virtual switches and host adapters and must keep guest network reachability aligned with approved host paths. Observed issue: Two Windows Server container hosts launch the same named image tag but execute different application dependencies. Investigation found: Image digests differ across hosts because the floating tag was republished between deployments. The proposed repair is: Pin the approved immutable image digest and control build promotion, signing and vulnerability verification. Which independently observable result best verifies resolution of the stated Windows Server problem?

  1. Both hosts run the same approved digest and reproducible application tests pass after redeployment.
  2. An application-level recovery rehearsal restores consistent data while separately maintained services retain their intended transaction state.
  3. A test VM reaches the correct subnet and gateway while the Hyper-V host retains its dedicated management path.
  4. A named authorized operator connects through Bastion while direct internet RDP is still denied.

Explanation

Correct Answer

A:

At Harborview Virtual Networking, verifying that both hosts run the same approved digest and reproducible application tests pass after redeployment would establish the relevant recovery outcome. The earlier evidence was that image digests differ across hosts because the floating tag was republished between deployments. Container tags are mutable references and reproducible workloads should identify verified image artifacts.

Incorrect Answers

B:

The alternative test result is that an application-level recovery rehearsal restores consistent data while separately maintained services retain their intended transaction state. It does not prove recovery of the Harborview Virtual Networking failure, where two Windows Server container hosts launch the same named image tag but execute different application dependencies. A relevant acceptance result would show that both hosts run the same approved digest and reproducible application tests pass after redeployment.

C:

The alternative validation would show that a test VM reaches the correct subnet and gateway while the Hyper-V host retains its dedicated management path. For Harborview Virtual Networking, that is insufficient to establish that both hosts run the same approved digest and reproducible application tests pass after redeployment. The original diagnostic finding is that image digests differ across hosts because the floating tag was republished between deployments.

D:

At Harborview Virtual Networking, a test showing that a named authorized operator connects through Bastion while direct internet RDP is still denied would not confirm the needed outcome. The check must demonstrate that both hosts run the same approved digest and reproducible application tests pass after redeployment. It must address the failure, where two Windows Server container hosts launch the same named image tag but execute different application dependencies.

Question 424

At Harborview Virtual Networking, the team supports Hyper-V virtual switches and host adapters and must keep guest network reachability aligned with approved host paths. The administrator observes: Two Windows Server container hosts launch the same named image tag but execute different application dependencies. The distinguishing clue is: Image digests differ across hosts because the floating tag was republished between deployments. 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. Virtual networking reachability depends on coherent virtual switch, physical adapter and VLAN configuration.
  3. Container tags are mutable references and reproducible workloads should identify verified image artifacts.
  4. Container networking isolates endpoints unless reachable service ports and routes are explicitly designed.

Explanation

Correct Answer

C:

The appropriate mechanism for Harborview Virtual Networking is that container tags are mutable references and reproducible workloads should identify verified image artifacts. This explains the recorded clue: Image digests differ across hosts because the floating tag was republished between deployments. It accounts for the reported failure, where two Windows Server container hosts launch the same named image tag but execute different application dependencies.

Incorrect Answers

A:

The alternate technical explanation says that dynamic memory capacity must be engineered against both guest demand and available physical host resources. It is not the mechanism identified by the Harborview Virtual Networking record: Image digests differ across hosts because the floating tag was republished between deployments. Container tags are mutable references and reproducible workloads should identify verified image artifacts.

B:

The case at Harborview Virtual Networking is that two Windows Server container hosts launch the same named image tag but execute different application dependencies. The offered principle, virtual networking reachability depends on coherent virtual switch, physical adapter and VLAN configuration, would not explain this observed failure. The relevant mechanism is that container tags are mutable references and reproducible workloads should identify verified image artifacts.

D:

The alternative principle is that container networking isolates endpoints unless reachable service ports and routes are explicitly designed. For Harborview Virtual Networking, it does not explain why image digests differ across hosts because the floating tag was republished between deployments. The applicable causal rule is that container tags are mutable references and reproducible workloads should identify verified image artifacts.

Question 425

At Harborview Virtual Networking, the team supports Hyper-V virtual switches and host adapters and must keep guest network reachability aligned with approved host paths. The original incident is: Two Windows Server container hosts launch the same named image tag but execute different application dependencies. The evidence is: Image digests differ across hosts because the floating tag was republished between deployments. 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: 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.
  3. 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.
  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

D:

This proposed change-and-check pair is tied to the Harborview Virtual Networking fault: 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 diagnostic basis is that image digests differ across hosts because the floating tag was republished between deployments. The outcome must show that both hosts run the same approved digest and reproducible application tests pass after redeployment.

Incorrect Answers

A:

This offered change and proof, 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, would leave the Harborview Virtual Networking case unverified. The actual recorded fault is that two Windows Server container hosts launch the same named image tag but execute different application dependencies. A meaningful check requires that both hosts run the same approved digest and reproducible application tests pass after redeployment.

B:

The alternative combined step is 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. The relevant Harborview Virtual Networking evidence is that image digests differ across hosts because the floating tag was republished between deployments. Closure must validate that both hosts run the same approved digest and reproducible application tests pass after redeployment, rather than a different symptom.

C:

The paired remediation states 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. It does not test correction of the Harborview Virtual Networking condition: Image digests differ across hosts because the floating tag was republished between deployments. The outcome to verify is that both hosts run the same approved digest and reproducible application tests pass after redeployment.

Question 426

At Pinebrook Container Platform, the team supports Windows container images and host runtimes and must pin supported OS and image versions with auditable deployment. Confirmed original fault: Two Windows Server container hosts launch the same named image tag but execute different application dependencies. Supporting diagnostic evidence: Image digests differ across hosts because the floating tag was republished between deployments. A bounded change is required. Which appropriately scoped Windows Server or hybrid administration correction most directly addresses this specific failure?

  1. Bind the switch to the approved physical path and validate VLAN configuration and host management connectivity.
  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. Configure the supported NAT or appropriate virtual network port publication and a narrowly scoped firewall path.

Explanation

Correct Answer

C:

The available evidence is that image digests differ across hosts because the floating tag was republished between deployments. Pinebrook Container Platform needs to pin the approved immutable image digest and control build promotion, signing and vulnerability verification. Container tags are mutable references and reproducible workloads should identify verified image artifacts. Confirmation would be that both hosts run the same approved digest and reproducible application tests pass after redeployment.

Incorrect Answers

A:

Proposing to bind the switch to the approved physical path and validate VLAN configuration and host management connectivity does not fit the evidence at Pinebrook Container Platform: Image digests differ across hosts because the floating tag was republished between deployments. That would not resolve the original failure: two Windows Server container hosts launch the same named image tag but execute different application dependencies.

B:

The issue at Pinebrook Container Platform is that two Windows Server container hosts launch the same named image tag but execute different application dependencies. Acting to validate host attestation and authorized guardian or key protector configuration before moving the protected workload would not correct the evidenced cause. The most relevant clue is that image digests differ across hosts because the floating tag was republished between deployments.

D:

The failure at Pinebrook Container Platform is that two Windows Server container hosts launch the same named image tag but execute different application dependencies. That does not call for configure the supported NAT or appropriate virtual network port publication and a narrowly scoped firewall path. The case evidence instead establishes that image digests differ across hosts because the floating tag was republished between deployments.

Question 427

At Pinebrook Container Platform, the team supports Windows container images and host runtimes and must pin supported OS and image versions with auditable deployment. A reported incident states: Two Windows Server container hosts launch the same named image tag but execute different application dependencies. 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. Image digests differ across hosts because the floating tag was republished between deployments.
  2. Migration precheck reports processor instruction set incompatibility and the hosts use different CPU feature levels.
  3. Container runtime messages identify host-image Windows kernel build incompatibility under process isolation.
  4. Effective NSG rules or route tables on the VM NIC deny the required traffic though the guest IP configuration looks normal.

Explanation

Correct Answer

A:

The relevant observation is that image digests differ across hosts because the floating tag was republished between deployments. It is directly relevant to Pinebrook Container Platform because two Windows Server container hosts launch the same named image tag but execute different application dependencies. Container tags are mutable references and reproducible workloads should identify verified image artifacts.

Incorrect Answers

B:

At Pinebrook Container Platform, The alternative observation about migration precheck reports processor instruction set incompatibility and the hosts use different CPU feature levels would not isolate the relevant problem. The diagnostic clue is that image digests differ across hosts because the floating tag was republished between deployments. This is the clue that bears on two Windows Server container hosts launch the same named image tag but execute different application dependencies.

C:

An unrelated diagnosis would involve: Container runtime messages identify host-image Windows kernel build incompatibility under process isolation. The incident at Pinebrook Container Platform is that two Windows Server container hosts launch the same named image tag but execute different application dependencies. The decisive finding instead is that image digests differ across hosts because the floating tag was republished between deployments.

D:

This observation, effective NSG rules or route tables on the VM NIC deny the required traffic though the guest IP configuration looks normal, does not match the evidence in the Pinebrook Container Platform record. Instead, the record shows that image digests differ across hosts because the floating tag was republished between deployments. Container tags are mutable references and reproducible workloads should identify verified image artifacts.

Question 428

At Pinebrook Container Platform, the team supports Windows container images and host runtimes and must pin supported OS and image versions with auditable deployment. Observed issue: Two Windows Server container hosts launch the same named image tag but execute different application dependencies. Investigation found: Image digests differ across hosts because the floating tag was republished between deployments. The proposed repair is: Pin the approved immutable image digest and control build promotion, signing and vulnerability verification. Which independently observable result best verifies resolution of the stated Windows Server problem?

  1. The shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts.
  2. Both hosts run the same approved digest and reproducible application tests pass after redeployment.
  3. The replacement capacity is provisioned successfully and the application passes a controlled functional check.
  4. A named authorized operator connects through Bastion while direct internet RDP is still denied.

Explanation

Correct Answer

B:

At Pinebrook Container Platform, the selected verification result is that both hosts run the same approved digest and reproducible application tests pass after redeployment. This checks recovery of the reported issue, where two Windows Server container hosts launch the same named image tag but execute different application dependencies. Container tags are mutable references and reproducible workloads should identify verified image artifacts.

Incorrect Answers

A:

The alternative test result is that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts. It does not prove recovery of the Pinebrook Container Platform failure, where two Windows Server container hosts launch the same named image tag but execute different application dependencies. A relevant acceptance result would show that both hosts run the same approved digest and reproducible application tests pass after redeployment.

C:

At Pinebrook Container Platform, a test showing that the replacement capacity is provisioned successfully and the application passes a controlled functional check would not confirm the needed outcome. The check must demonstrate that both hosts run the same approved digest and reproducible application tests pass after redeployment. It must address the failure, where two Windows Server container hosts launch the same named image tag but execute different application dependencies.

D:

That verification is that a named authorized operator connects through Bastion while direct internet RDP is still denied. The Pinebrook Container Platform acceptance criterion is instead that both hosts run the same approved digest and reproducible application tests pass after redeployment. The recorded causal clue is that image digests differ across hosts because the floating tag was republished between deployments.

Question 429

At Pinebrook Container Platform, the team supports Windows container images and host runtimes and must pin supported OS and image versions with auditable deployment. The administrator observes: Two Windows Server container hosts launch the same named image tag but execute different application dependencies. The distinguishing clue is: Image digests differ across hosts because the floating tag was republished between deployments. 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. Container images and hosts must agree on operating system and execution isolation capabilities.
  2. Azure VM storage throughput is constrained by both disk service limits and VM size capabilities.
  3. Container tags are mutable references and reproducible workloads should identify verified image artifacts.
  4. Availability sets and availability zones mitigate different infrastructure failure scopes.

Explanation

Correct Answer

C:

The selected principle is that container tags are mutable references and reproducible workloads should identify verified image artifacts. It fits the Pinebrook Container Platform case because image digests differ across hosts because the floating tag was republished between deployments. The reported failure is that two Windows Server container hosts launch the same named image tag but execute different application dependencies.

Incorrect Answers

A:

The case at Pinebrook Container Platform is that two Windows Server container hosts launch the same named image tag but execute different application dependencies. The offered principle, container images and hosts must agree on operating system and execution isolation capabilities, would not explain this observed failure. The relevant mechanism is that container tags are mutable references and reproducible workloads should identify verified image artifacts.

B:

The alternative rule states that azure VM storage throughput is constrained by both disk service limits and VM size capabilities. It does not account for the Pinebrook Container Platform evidence: Image digests differ across hosts because the floating tag was republished between deployments. The case turns on the mechanism that container tags are mutable references and reproducible workloads should identify verified image artifacts.

D:

This offered mechanism, availability sets and availability zones mitigate different infrastructure failure scopes, does not match the specific recorded failure at Pinebrook Container Platform, where two Windows Server container hosts launch the same named image tag but execute different application dependencies. The relevant principle is that container tags are mutable references and reproducible workloads should identify verified image artifacts.

Question 430

At Pinebrook Container Platform, the team supports Windows container images and host runtimes and must pin supported OS and image versions with auditable deployment. The original incident is: Two Windows Server container hosts launch the same named image tag but execute different application dependencies. The evidence is: Image digests differ across hosts because the floating tag was republished between deployments. 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 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.
  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: 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: 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:

That intervention and proof go together at Pinebrook Container Platform: 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 root finding is that image digests differ across hosts because the floating tag was republished between deployments. It is closed only when both hosts run the same approved digest and reproducible application tests pass after redeployment.

Incorrect Answers

A:

The alternative combined step 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. The relevant Pinebrook Container Platform evidence is that image digests differ across hosts because the floating tag was republished between deployments. Closure must validate that both hosts run the same approved digest and reproducible application tests pass after redeployment, rather than a different symptom.

C:

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 Pinebrook Container Platform clue: Image digests differ across hosts because the floating tag was republished between deployments. The acceptance test needs to show that both hosts run the same approved digest and reproducible application tests pass after redeployment.

D:

The paired proposal is 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. For Pinebrook Container Platform, it fails to establish an intervention and check for the documented issue, where two Windows Server container hosts launch the same named image tag but execute different application dependencies. Successful closure requires that both hosts run the same approved digest and reproducible application tests pass after redeployment.

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