Question 20
In the Beacon IT Solutions pilot environment, a controlled verification is required for: A deployment team gives session hosts public IPs for outbound AVD service traffic even though security policy forbids inbound internet exposure. What evidence best demonstrates that the reported AVD issue is resolved?
Explanation
Correct Answer
New session hosts register and users connect while no session host VM has a directly reachable public IP address. This is an independently observable result of the targeted change: Design session-host egress through controlled NAT or firewall routing and permit required Azure Virtual Desktop service endpoints without public host IPs. It closes the specific Beacon IT Solutions failure: A deployment team gives session hosts public IPs for outbound AVD service traffic even though security policy forbids inbound internet exposure.
Incorrect Answers
A representative logon surge and video meeting run coexist without the VPN link reaching sustained utilization or unacceptable jitter. This is evidence for a DIFFERENT remediation: Plan capacity against observed high-percentile bandwidth and bursty sign-ins, incorporating headroom for concurrent Microsoft Teams meetings. That remediation addresses: An acquired branch connects through an undersized VPN and the team projects total desktop bandwidth using only average traffic per connected user. It does not establish resolution of the Beacon IT Solutions problem: A deployment team gives session hosts public IPs for outbound AVD service traffic even though security policy forbids inbound internet exposure. The required outcome here is: New session hosts register and users connect while no session host VM has a directly reachable public IP address.
A session host resolves the correct private storage endpoint and mounts the profile share without using a public DNS answer. This is evidence for a DIFFERENT remediation: Configure and test DNS resolution for the session host subnet with conditional forwarding or private DNS integration matching the storage endpoints. That remediation addresses: Session hosts in a hub-and-spoke deployment cannot resolve private file share names because the spoke VNet uses a DNS server without the needed forwarders. It does not establish resolution of the Beacon IT Solutions problem: A deployment team gives session hosts public IPs for outbound AVD service traffic even though security policy forbids inbound internet exposure. The required outcome here is: New session hosts register and users connect while no session host VM has a directly reachable public IP address.
Connection-status telemetry shows Multipath enabled and an induced UDP path failure falls back without an avoidable session disconnect. This is evidence for a DIFFERENT remediation: Use supported Windows App versions and RDP Shortpath connectivity so built-in RDP Multipath can maintain and switch viable transport paths. That remediation addresses: Users on mobile networks report abrupt reconnects when their best UDP route degrades; engineers assume RDP Multipath requires a separate custom agent. It does not establish resolution of the Beacon IT Solutions problem: A deployment team gives session hosts public IPs for outbound AVD service traffic even though security policy forbids inbound internet exposure. The required outcome here is: New session hosts register and users connect while no session host VM has a directly reachable public IP address.