A remote ranger station has low bandwidth. Staff want Blast Extreme for the Horizon session. Where does the operator set that preference at associate depth?
Select an answer to reveal the explanation.
Short Explanation
Protocol preference is a knob on the ranger's Horizon Client, like picking speaker vs headset on a desk phone — not an NSX shaper and not DRS. Set Blast in Client session options. Distributed Firewall packet marks do not choose the display protocol.
Full Explanation
When a remote ranger station has low bandwidth and staff want Blast Extreme for the Horizon session, the operator sets that preference at associate depth in Horizon Client session settings on the ranger station by choosing Blast as the protocol preference. Protocol preference is a Client-side session setting in this scope. Low-bandwidth ranger sites standardize on Blast through Client settings so field staff do not wait on network redesign tickets for basic protocol choice. NSX traffic-shaping profiles on the ranger VLAN are network engineering controls, not the associate Client protocol preference setting. A new Distributed Firewall rule that marks Blast packets does not select Blast inside Horizon Client. vSphere DRS automation level for the ranger cluster does not choose the display protocol for a user session. Exam caveat: Associate-depth Blast preference is configured in Horizon Client session settings, not by redesigning NSX or DRS. Operational check: On a ranger-station Client, open session settings, select Blast Extreme as the preferred protocol, reconnect, and confirm the session reports Blast. Document the collection source and timestamp in the municipal ticket so the next operator can continue without rework.