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

Question 490

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: Two related Windows Server virtual machines are placed in one availability set and the team assumes a complete availability-zone outage is covered. The evidence is: Deployment metadata confirms both VMs share the same zone and only fault/update-domain distribution is configured. 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: 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.
  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: 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.
  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

A:

The case at Northgate Azure Compute requires both correction and evidence for the same fault. The proposed pair 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. It addresses the finding that deployment metadata confirms both VMs share the same zone and only fault/update-domain distribution is configured and tests whether a planned failure experiment demonstrates the application meets the intended fault-domain availability target.

Incorrect Answers

B:

The paired remediation states 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. It does not test correction of the Northgate Azure Compute condition: Deployment metadata confirms both VMs share the same zone and only fault/update-domain distribution is configured. The outcome to verify is that a planned failure experiment demonstrates the application meets the intended fault-domain availability target.

C:

That action and check pair is 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 connect both parts to the actual Northgate Azure Compute clue: Deployment metadata confirms both VMs share the same zone and only fault/update-domain distribution is configured. The acceptance test needs to show that a planned failure experiment demonstrates the application meets the intended fault-domain availability target.

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 Northgate Azure Compute, it fails to establish an intervention and check for the documented issue, where two related Windows Server virtual machines are placed in one availability set and the team assumes a complete availability-zone outage is covered. Successful closure requires that a planned failure experiment demonstrates the application meets the intended fault-domain availability target.

Question 491

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: An engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. Supporting diagnostic evidence: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. 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. 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. Evaluate availability-zone or region resilience requirements and implement the authorized redundancy architecture.

Explanation

Correct Answer

C:

For Northgate Azure Compute, the decisive clue is that bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. The matching control change is to restore the supported approved Bastion subnet, routing and private RDP access path without opening public RDP. Bastion eliminates a public VM management entry point but still requires private network reachability and access policy. The correct result is that that a named authorized operator connects through Bastion while direct internet RDP is still denied.

Incorrect Answers

A:

The issue at Northgate Azure Compute is that an engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. Acting to set workload-tested dynamic memory startup, minimum and maximum values while accounting for host contention would not correct the evidenced cause. The most relevant clue is that bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC.

B:

That alternative would use a supported Linux-capable runtime such as an approved WSL2 Linux execution environment or separate Linux nodes. It misses the condition observed at Northgate Azure Compute: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. The recommended correction addresses the observed condition directly.

D:

At Northgate Azure Compute, proposing to evaluate availability-zone or region resilience requirements and implement the authorized redundancy architecture would not address the recorded evidence: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. The case instead needs an intervention related to an engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. Bastion eliminates a public VM management entry point but still requires private network reachability and access policy.

Question 492

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: An engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. 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. The external Hyper-V virtual switch is bound to a host adapter that does not connect to the authorized uplink VLAN.
  2. Cluster diagnostics show the target node lacks a supported Windows container runtime or required cluster networking components.
  3. Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC.
  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

C:

At Northgate Azure Compute, the distinguishing evidence is: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. It is directly connected to an engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. Bastion eliminates a public VM management entry point but still requires private network reachability and access policy.

Incorrect Answers

A:

At Northgate Azure Compute, The alternative observation about the external Hyper-V virtual switch is bound to a host adapter that does not connect to the authorized uplink VLAN would not isolate the relevant problem. The diagnostic clue is that bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. This is the clue that bears on an engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address.

B:

An unrelated diagnosis would involve: Cluster diagnostics show the target node lacks a supported Windows container runtime or required cluster networking components. The incident at Northgate Azure Compute is that an engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. The decisive finding instead is that bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC.

D:

For Northgate Azure Compute, the proposed observation is that effective NSG rules or route tables on the VM NIC deny the required traffic though the guest IP configuration looks normal. It would not distinguish the identified failure, where an engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. The meaningful clue is that bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC.

Question 493

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: An engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. Investigation found: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. The proposed repair is: Restore the supported approved Bastion subnet, routing and private RDP access path without opening public RDP. 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. A named authorized operator connects through Bastion while direct internet RDP is still denied.
  3. Both hosts run the same approved digest and reproducible application tests pass after redeployment.
  4. A designated client reaches the published service while unapproved container ports remain inaccessible.

Explanation

Correct Answer

B:

The proof must establish that a named authorized operator connects through Bastion while direct internet RDP is still denied. That directly tests the observed condition at Northgate Azure Compute: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. Bastion eliminates a public VM management entry point but still requires private network reachability and access policy.

Incorrect Answers

A:

The alternative validation would show that the shielded guest boots only on approved attested hosts and remains blocked on untrusted test hosts. For Northgate Azure Compute, that is insufficient to establish that a named authorized operator connects through Bastion while direct internet RDP is still denied. The original diagnostic finding is that bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC.

C:

That verification is that both hosts run the same approved digest and reproducible application tests pass after redeployment. The Northgate Azure Compute acceptance criterion is instead that a named authorized operator connects through Bastion while direct internet RDP is still denied. The recorded causal clue is that bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC.

D:

This check suggests that a designated client reaches the published service while unapproved container ports remain inaccessible. It does not test the resolution criterion for Northgate Azure Compute, namely that a named authorized operator connects through Bastion while direct internet RDP is still denied. Bastion eliminates a public VM management entry point but still requires private network reachability and access policy.

Question 494

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: An engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. The distinguishing clue is: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. 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 tags are mutable references and reproducible workloads should identify verified image artifacts.
  2. Container networking isolates endpoints unless reachable service ports and routes are explicitly designed.
  3. Bastion eliminates a public VM management entry point but still requires private network reachability and access policy.
  4. Availability sets and availability zones mitigate different infrastructure failure scopes.

Explanation

Correct Answer

C:

At Northgate Azure Compute, the key technical rule is that bastion eliminates a public VM management entry point but still requires private network reachability and access policy. The evidence is that bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. This links the observed failure to its underlying cause.

Incorrect Answers

A:

The alternative rule states that container tags are mutable references and reproducible workloads should identify verified image artifacts. It does not account for the Northgate Azure Compute evidence: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. The case turns on the mechanism that bastion eliminates a public VM management entry point but still requires private network reachability and access policy.

B:

The alternative principle is that container networking isolates endpoints unless reachable service ports and routes are explicitly designed. For Northgate Azure Compute, it does not explain why bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. The applicable causal rule is that bastion eliminates a public VM management entry point but still requires private network reachability and access policy.

D:

At Northgate Azure Compute, the reported clue is that bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. The principle of availability sets and availability zones mitigate different infrastructure failure scopes does not explain that finding. The appropriate explanation is that bastion eliminates a public VM management entry point but still requires private network reachability and access policy.

Question 495

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: An engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. The evidence is: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. 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: 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.
  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: 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.
  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:

That intervention and proof go together at Northgate Azure Compute: 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. The relevant root finding is that bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. It is closed only when a named authorized operator connects through Bastion while direct internet RDP is still denied.

Incorrect Answers

B:

That action and check pair 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. It does not connect both parts to the actual Northgate Azure Compute clue: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. The acceptance test needs to show that a named authorized operator connects through Bastion while direct internet RDP is still denied.

C:

The paired proposal is 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. For Northgate Azure Compute, it fails to establish an intervention and check for the documented issue, where an engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. Successful closure requires that a named authorized operator connects through Bastion while direct internet RDP is still denied.

D:

At Northgate Azure Compute, the option couples 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. Its test does not independently demonstrate that a named authorized operator connects through Bastion while direct internet RDP is still denied. The deciding case evidence is that bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC.

Question 496

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: An engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. Supporting diagnostic evidence: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. A bounded change is required. Which appropriately scoped Windows Server or hybrid administration correction most directly addresses this specific failure?

  1. Use application-aware recovery, production checkpoints where supported, and documented guest backup semantics rather than assuming any checkpoint is a full backup.
  2. Bind the switch to the approved physical path and validate VLAN configuration and host management connectivity.
  3. Correct only the intended NIC/subnet route and NSG rules to permit designated directory services.
  4. Restore the supported approved Bastion subnet, routing and private RDP access path without opening public RDP.

Explanation

Correct Answer

D:

At Cedarline Hyper-V Engineering, bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. The fitting correction is to restore the supported approved Bastion subnet, routing and private RDP access path without opening public RDP. Bastion eliminates a public VM management entry point but still requires private network reachability and access policy. The acceptance check is that a named authorized operator connects through Bastion while direct internet RDP is still denied.

Incorrect Answers

A:

That alternative would use application-aware recovery, production checkpoints where supported, and documented guest backup semantics rather than assuming any checkpoint is a full backup. It misses the condition observed at Cedarline Hyper-V Engineering: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. The recommended correction addresses the observed condition directly.

B:

The failure at Cedarline Hyper-V Engineering is that an engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. That does not call for bind the switch to the approved physical path and validate VLAN configuration and host management connectivity. The case evidence instead establishes that bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC.

C:

At Cedarline Hyper-V Engineering, proposing to correct only the intended NIC/subnet route and NSG rules to permit designated directory services would not address the recorded evidence: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. The case instead needs an intervention related to an engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. Bastion eliminates a public VM management entry point but still requires private network reachability and access policy.

Question 497

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: An engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. 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. Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC.
  2. VM memory pressure metrics show sustained paging and ballooning against an undersized assigned minimum and available host memory.
  3. The external Hyper-V virtual switch is bound to a host adapter that does not connect to the authorized uplink VLAN.
  4. Port mapping and NAT inspection show the service port is not published on the reachable Windows container host interface.

Explanation

Correct Answer

A:

The reported issue at Cedarline Hyper-V Engineering is that an engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. The offered observation of bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC identifies the relevant fault rather than an unrelated symptom. Bastion eliminates a public VM management entry point but still requires private network reachability and access policy.

Incorrect Answers

B:

This observation, vM memory pressure metrics show sustained paging and ballooning against an undersized assigned minimum and available host memory, does not match the evidence in the Cedarline Hyper-V Engineering record. Instead, the record shows that bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. Bastion eliminates a public VM management entry point but still requires private network reachability and access policy.

C:

For Cedarline Hyper-V Engineering, the proposed observation is that the external Hyper-V virtual switch is bound to a host adapter that does not connect to the authorized uplink VLAN. It would not distinguish the identified failure, where an engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. The meaningful clue is that bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC.

D:

The observation offered is that port mapping and NAT inspection show the service port is not published on the reachable Windows container host interface. It does not substantiate the reported Cedarline Hyper-V Engineering failure, where an engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. The directly relevant diagnostic record is that bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC.

Question 498

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: An engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. Investigation found: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. The proposed repair is: Restore the supported approved Bastion subnet, routing and private RDP access path without opening public RDP. Which independently observable result best verifies resolution of the stated Windows Server problem?

  1. A named authorized operator connects through Bastion while direct internet RDP is still denied.
  2. The guest starts and sustains representative application load without pathological memory pressure or exhausting host capacity.
  3. The replacement capacity is provisioned successfully and the application passes a controlled functional check.
  4. A controlled directory query from the VM succeeds and negative probes to unrelated restricted networks fail.

Explanation

Correct Answer

A:

The proof must establish that a named authorized operator connects through Bastion while direct internet RDP is still denied. That directly tests the observed condition at Cedarline Hyper-V Engineering: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. Bastion eliminates a public VM management entry point but still requires private network reachability and access policy.

Incorrect Answers

B:

That verification is that the guest starts and sustains representative application load without pathological memory pressure or exhausting host capacity. The Cedarline Hyper-V Engineering acceptance criterion is instead that a named authorized operator connects through Bastion while direct internet RDP is still denied. The recorded causal clue is that bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC.

C:

This check suggests that the replacement capacity is provisioned successfully and the application passes a controlled functional check. It does not test the resolution criterion for Cedarline Hyper-V Engineering, namely that a named authorized operator connects through Bastion while direct internet RDP is still denied. Bastion eliminates a public VM management entry point but still requires private network reachability and access policy.

D:

The option would validate that a controlled directory query from the VM succeeds and negative probes to unrelated restricted networks fail. That does not establish correction of the Cedarline Hyper-V Engineering issue, where an engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. The meaningful proof is that a named authorized operator connects through Bastion while direct internet RDP is still denied.

Question 499

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: An engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. The distinguishing clue is: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. 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. Live migration must account for processor compatibility as well as network and shared storage prerequisites.
  2. Shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access.
  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

C:

The engineering rationale is that bastion eliminates a public VM management entry point but still requires private network reachability and access policy. It is relevant at Cedarline Hyper-V Engineering because bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. The failure to explain is that an engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address.

Incorrect Answers

A:

The alternative principle is that live migration must account for processor compatibility as well as network and shared storage prerequisites. For Cedarline Hyper-V Engineering, it does not explain why bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. The applicable causal rule is that bastion eliminates a public VM management entry point but still requires private network reachability and access policy.

B:

This offered mechanism, shielded VM protection relies on the host guardian and attestation chain rather than ordinary hypervisor administrator access, does not match the specific recorded failure at Cedarline Hyper-V Engineering, where an engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. The relevant principle is that bastion eliminates a public VM management entry point but still requires private network reachability and access policy.

D:

The alternate technical explanation says that container images and hosts must agree on operating system and execution isolation capabilities. It is not the mechanism identified by the Cedarline Hyper-V Engineering record: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. Bastion eliminates a public VM management entry point but still requires private network reachability and access policy.

Question 500

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: An engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. The evidence is: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. 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: 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.
  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: Choose an approved available size or placement strategy and check quota, feature, disk and networking compatibility first. Evidence of success: The replacement capacity is provisioned successfully and the application passes a controlled functional check.

Explanation

Correct Answer

C:

The documented issue at Cedarline Hyper-V Engineering is that an engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. The selected combined action and test 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. Its verification aligns with the required outcome: A named authorized operator connects through Bastion while direct internet RDP is still denied.

Incorrect Answers

A:

That action and check pair 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. It does not connect both parts to the actual Cedarline Hyper-V Engineering clue: Bastion session diagnostics identify a missing effective route or network policy between the Bastion subnet and the VM's private NIC. The acceptance test needs to show that a named authorized operator connects through Bastion while direct internet RDP is still denied.

B:

The paired proposal 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. For Cedarline Hyper-V Engineering, it fails to establish an intervention and check for the documented issue, where an engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. Successful closure requires that a named authorized operator connects through Bastion while direct internet RDP is still denied.

D:

This offered change and proof, action: Choose an approved available size or placement strategy and check quota, feature, disk and networking compatibility first. Evidence of success: The replacement capacity is provisioned successfully and the application passes a controlled functional check, would leave the Cedarline Hyper-V Engineering case unverified. The actual recorded fault is that an engineer launches Azure Bastion but cannot connect to the intended Windows VM through its private address. A meaningful check requires that a named authorized operator connects through Bastion while direct internet RDP is still denied.

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