1Y0-A26 · Question #149
Scenario: An administrator noticed that a new patch has been released and plans to apply the patch to a host in a resource pool. High availability is NOT enabled in the resource pool. Which…
The correct answer is B. Update the pool master and reboot. Exam Questions, Study Guides, Practice Tests. Lead the way to help you pass any IT Certification exams, 100% Pass Guaranteed or Full Refund. Especially Cisco, Microsoft, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan…
Question
Scenario: An administrator noticed that a new patch has been released and plans to apply the patch to a host in a resource pool. High availability is NOT enabled in the resource pool. Which configuration must the administrator make before applying the patch to the host?
Options
- AUpdate XenCenter and reboot.
- BUpdate the pool master and reboot.
- CUpdate XenServer Tools and reboot.
- DUpdate secondary servers and reboot.
How the community answered
(38 responses)- A5% (2)
- B82% (31)
- C3% (1)
- D11% (4)
Explanation
Exam Questions, Study Guides, Practice Tests. Lead the way to help you pass any IT Certification exams, 100% Pass Guaranteed or Full Refund. Especially Cisco, Microsoft, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan: First Test, First Pass. Help you to pass any IT Certification exams at the first try. You can reach us at any of the email addresses listed below. Any problems about IT certification or our products, you could rely upon us, we will give you satisfactory answers in 24 hours.
Topics
Community Discussion
5
Ola B.Oct 18, 2025The correct answer is B, update the pool master and reboot. In a XenServer resource pool, the pool master is the coordinator for all pool-wide operations, and patching must always start there before you touch any secondary host. If you try to patch a secondary host while the pool master is on an older version, you can end up with version mismatches that break pool communication and cause real headaches. The fact that HA is not enabled actually makes this more important to get right procedurally, since you have no automatic failover to catch mistakes, so spin up a test pool if you want to see this sequence play out yourself before exam day.
Imani T.Oct 28, 2025I kept second-guessing myself toward D because secondary servers felt like the logical first step when HA is off and you are patching piece by piece, but then I remembered that the pool master controls the metadata and patch coordination for the whole pool, so if you patch a host without the master being updated first you are basically asking for version mismatch headaches that can tank your whole resource pool.
Toby R.Oct 30, 2025Exactly right on the master-first order, and the one thing I'd add is the exam also wanted you to know you need to evacuate the pool master's VMs to other hosts before you patch it, so that detail about sequencing goes a level deeper than just which host goes first.
Toby R.Oct 24, 2025This one tripped me up at first because I was thinking about the VMs and workloads, but the exam is really testing whether you know the hierarchy of how patches get applied in a pool. The pool master is the authoritative node that all the other hosts coordinate through, so if you patch a secondary host before the master is at the same level, you're asking for version mismatch problems that can destabilize the whole pool. B is right because that update-and-reboot of the pool master has to happen first, and the lack of HA in the scenario is there to make sure you're not distracted thinking about VM failover protection before maintenance. What I kept wondering though, and never felt like I got a clean answer on, is whether there is a hard technical block that prevents you from applying a patch to a secondary host before the master is updated, or is it just that the pool will behave unpredictably and Citrix simply documents it as the required sequence?
Ola B.Oct 24, 2025Citrix does not physically block you from patching a secondary out of order, it just leaves you with a pool in an unsupported state where XenCenter or XAPI can throw version mismatch errors and your toolstack coordination becomes unreliable, so the sequence is enforced by documented best practice and the real-world fallout rather than a hard gate.