1Y0-A20 · Question #115
Scenario: An entire Shift of workers arrives at the office at 09:00 AM. Two thousand users turn on their thin client terminals and launch a line of business application within a ten-minute…
The correct answer is B. Configure a Pre-launch application to be started for users before they arrive. See the full explanation below for the reasoning.
Question
Scenario: An entire Shift of workers arrives at the office at 09:00 AM. Two thousand users turn on their thin client terminals and launch a line of business application within a ten-minute timeframe. The resultant traffic is so intense that it takes 15-20 minutes until everybody is able to start working. How can the administrator prevent this issue from affecting the user experience?
Options
- AImplement a NetScaler load balancer to distribute the XML traffic
- BConfigure a Pre-launch application to be started for users before they arrive.
- CUpgrade the XenApp farm database server to a cluster with real time replication.
- DConfigure additional zone data collectors to manage the numerous concurrent logins.
How the community answered
(24 responses)- A8% (2)
- B83% (20)
- C4% (1)
- D4% (1)
Community Discussion
7
Prof. SaraJun 26, 2026The answer is B. Pre-launch spins up ICA sessions before users physically arrive, so when that 09:00 wave hits, the XenApp farm is not scrambling to authenticate and initialize 2,000 sessions simultaneously, it is simply handing off sessions that are already warm and waiting, which eliminates the login storm entirely.
Bao N.Jun 20, 2026B is right, though "before they arrive" should say "before logon" - pre-launch sessions warm up ICA before the storm hits.
Wesley A.Jun 26, 2026D pulled me in hard the first time, but Pre-launch solves the startup delay, not zone load.
Bao N.Jun 27, 2026Pre-launch handles that initial session spin-up lag, but if your zone files are heavy you still eat the load time after the handoff, so pairing it with a lean zone config is where the real gains show up.
Giselle K.Jun 26, 2026B is right, pre-launch warms the session before users even log in.
Lena V.Jun 26, 2026Saw almost this exact wording on my exam, the "storm" scenario is a classic Citrix gotcha designed to make you reach for infrastructure answers when the real fix is session pre-launch, which spins up sessions ahead of time so users hit a warm session instead of a cold queue at 09:00. I almost picked A out of habit but caught myself, because load balancing the XML traffic does nothing when the bottleneck is the session initialization pile-up itself.
Bao N.Jun 29, 2026Pre-launch helps for sure, but don't sleep on Session Lingering either, because keeping idle sessions warm after disconnect covers the stragglers who log back in mid-morning and still hit that cold-start delay.