Two Connection Servers share a load-balancer VIP so 311 never bookmarks a single hostname that dies. What networking idea is that?
Select an answer to reveal the explanation.
Short Explanation
One VIP for two brokers is like one published phone number that rings whichever clerk is on duty. Load balancing spreads 311 connections and hides a dead hostname. A CDN or an NSX lab is not that VIP.
Full Explanation
Two Connection Servers sharing a load-balancer VIP so 311 never bookmarks a single dying hostname is load balancing for broker connections and broker HA support. In municipal EUC terms, treat the endpoint as a window into city systems when the architecture says so, not as the system of record for the files or apps in the stem. Distractor concept: A CDN caching Blast frames at a branch is not broker VIP load balancing. Distractor concept: An NSX Tier-0 gateway is not a prerequisite that defines the VIP concept here. Distractor concept: SSL inspection on the core switch does not replace the need for more than one broker. Exam caveat: VIP in front of brokers = load balancing/HA for Connection Server access. Operational check: Point clients at the VIP, stop one broker, and confirm launches continue without a single hard-coded hostname. Record the chosen control and the rejected failure modes in the civic change ticket or runbook so on-call staff and auditors share the same rationale after the next maintenance window. Re-validate after personnel or image changes that the same control still meets the city's continuity, security, and support expectations for this service. Helpdesk coaching tip aligned to the conversational brief: One VIP for two brokers is like one published phone number that rings whichever clerk is on duty. Load balancing spreads 311 connections and hides a dead hostname. A CDN or an NSX lab is not that VIP.