1V0-642 · Question #7
Which component of VMware Horizon acts as a broker for client connections, providing authentication to users and directing incoming desktop requests from users to View virtualized desktops?
The correct answer is D. View Connection Server. https://pubs.vmware.com/horizon-7-view/index.jsp?topic=% 2Fcom.vmware.view.integration.doc%2FGUID-345AF3E0-A69A-4307-AFC6- CB97CE99AA60.html
Question
Which component of VMware Horizon acts as a broker for client connections, providing authentication to users and directing incoming desktop requests from users to View virtualized desktops?
Options
- AView Client
- BView Administrator
- CView Composer
- DView Connection Server
How the community answered
(19 responses)- A21% (4)
- B5% (1)
- C5% (1)
- D68% (13)
Explanation
https://pubs.vmware.com/horizon-7-view/index.jsp?topic=% 2Fcom.vmware.view.integration.doc%2FGUID-345AF3E0-A69A-4307-AFC6- CB97CE99AA60.html
Topics
Community Discussion
11The answer is D, View Connection Server. That is the piece our senior showed me first because it sits in the middle of everything, it handles user authentication and then routes each client session to the right virtual desktop, which is exactly what a broker does.
D is your answer. The View Connection Server is the central broker in Horizon that handles user authentication and routes incoming connection requests to the appropriate virtual desktops, which is literally its whole job in the architecture.
Carlos is right that connection brokering is the VCS core job, but worth noting it also enforces access policies and entitlements before any routing happens, so authentication alone undersells what it is actually doing.
Kept thinking View Administrator until "broker" and "directs requests" locked it to Connection Server.
Same trap I fell into, though what finally clicked for me was remembering that the Connection Server is the one that actually handles the PCoIP or Blast protocol negotiation, not just brokering which desktop you get.
View Connection Server is the core brokering component here, handling authentication and directing client sessions to the right virtual desktop pool. When you think through the traffic flow, do you have a clear picture of where View Composer fits in that same flow, and whether it touches live session routing at all or operates strictly during provisioning?
View Composer is strictly a provisioning-time component that talks to vCenter to create and manage linked-clone pools, so it is completely out of the live session routing path, which stays between the client, Security Server or UAG, and Connection Server.
I actually glanced at B first because "authentication" made me think of an admin-facing management tool, but then I read the stem again, specifically the phrase "directing incoming desktop requests," and that brokering function lives in D. View Connection Server is the broker that sits between the client and the virtual desktop, handling both auth and session routing, and once you key on "broker" in the stem, the other three options eliminate themselves fast.
Saw this exact question on my 1V0-642 and almost second-guessed myself because View Administrator kept pulling my attention since I spend half my day in that console, but the broker function is squarely on View Connection Server, which handles auth and routes desktop requests to the right pod. Remember it this way: Connection Server is the front door, Administrator is the key ring you use after you are already inside.
Clock is ticking so let me be direct: A, View Client, is the piece that sits between you and the desktop, handling your authentication handshake and routing you to the right virtualized session, which is exactly what "broker for client connections" describes. Do not overthink the word "broker" here, it is a quick-win question and the client component is the one touching your credentials and your connection, so lock in A and move on.
Brenda, the View Client is the endpoint piece on your machine, but it is the Connection Server, option D, that actually brokers the connection by handling authentication and directing you to the correct desktop pool or session. The word "broker" in the question maps directly to Connection Server's role in the Horizon architecture.