1Y0-205 · Question #24
What are two methods of configuring AutoScale to power on machines as needed? (Choose two.)
The correct answer is C. Schedule-Based D. Load-Based. AutoScale can be configured using a schedule-based method, where machines power on/off according to defined time schedules, and a load-based method, where machines are powered on/off dynamically in response to user demand and load conditions. These two methods ensure resource…
Question
What are two methods of configuring AutoScale to power on machines as needed? (Choose two.)
Options
- ADesktop-Based
- BServer-Based
- CSchedule-Based
- DLoad-Based
- EHost-Based
How the community answered
(55 responses)- A2% (1)
- B4% (2)
- C87% (48)
- E7% (4)
Explanation
AutoScale can be configured using a schedule-based method, where machines power on/off according to defined time schedules, and a load-based method, where machines are powered on/off dynamically in response to user demand and load conditions. These two methods ensure resource optimization while maintaining user experience.
Topics
Community Discussion
6
Samuel O.Feb 14, 2026Schedule-Based and Load-Based are your two AutoScale power management methods, C and D. Schedule-Based fires up machines on a calendar you define ahead of time, which is great when you know your peak hours, while Load-Based watches actual resource demand and spins up desktops reactively when thresholds get hit.
Giovanna H.Feb 17, 2026Good summary of those two, Samuel, but the blueprint also expects you to recognize a third option, Schedule and Load-Based, which combines both triggers so the delivery group can respect your calendar windows while still reacting dynamically to demand spikes within them, and that hybrid mode tends to show up in scenario questions on the CCA-V.
Lena V.Feb 27, 2026Saw this exact one, panicked, then remembered: AutoScale uses Schedule-Based and Load-Based, nothing else.
Giovanna H.Feb 5, 2026This maps to the Manage and Monitor Citrix Virtual Apps and Desktops blueprint section, specifically the AutoScale topic under workload management. The two configuration methods are Schedule-Based, which powers machines on and off according to a defined time window you set in advance, and Load-Based, which reacts dynamically to user demand by spinning up additional machines when session concurrency crosses your defined threshold. A clean mnemonic for this is SL, for "Set it or Let it react," meaning you either schedule the capacity ahead of time or let load drive the decision. The other options describe delivery groups or hosting types, not AutoScale triggering methods, so eliminate them first by asking yourself whether the option describes a timing or demand signal. When I sat the 1Y0-205 I flagged this one and came back to it, because Desktop-Based in option A felt tempting since we had been configuring desktop delivery groups all week in the lab. I almost talked myself into it. What pulled me back was remembering that AutoScale documentation specifically names Schedule-Based and Load-Based as the two power management strategies, and none of the other distractors appear in the AutoScale configuration wizard at all. Once I visualized the Studio console and the two tabs you actually click through when setting AutoScale up, C and D were obvious and I marked them without second-guessing.
Ola B.Mar 3, 2026I spun up a XenDesktop lab last month just to test this exact scenario and I kept seeing Host-Based come up when configuring power management under AutoScale, so I am going with E and D as my two picks because the host connection is literally what AutoScale uses to know which hypervisor to talk to when it needs to wake a machine.
Samuel O.Mar 4, 2026Ola, the lab experience makes sense but AutoScale's power management needs two things locked in, which are a power management scheme (C) and the host connection (D), because the scheme is what actually defines the schedules and thresholds that tell AutoScale when to act, not just which hypervisor to contact.