1Y0-371 · Question #105
Scenario: A Citrix Engineer is designing a XenMobile Enterprise solution to support approximately 30,000 device connections. The environment must be able to sustain the failure of one node in a…
The correct answer is C. Four. See the full explanation below for the reasoning.
Question
Scenario: A Citrix Engineer is designing a XenMobile Enterprise solution to support approximately 30,000 device connections. The environment must be able to sustain the failure of one node in a cluster at any given time for redundancy and maintenance purposes. Each server's specifications include four vCPUs and 16 GB of RAM. What is the minimum number of XenMobile Servers that the engineer should recommend as part of this cluster?
Options
- ATwo
- BThree
- CFour
- DFive
How the community answered
(57 responses)- A14% (8)
- B7% (4)
- C75% (43)
- D4% (2)
Community Discussion
8
Jovan I.Apr 25, 2026The correct answer is C, four nodes. With 4 vCPUs and 16 GB of RAM per server, each XenMobile node in this spec tier handles up to 10,000 device connections, so covering 30,000 connections at full capacity requires three nodes minimum. The requirement to survive the loss of any single node without degrading service is straight N+1 logic, meaning you need one additional node sitting ready to absorb that lost capacity, which puts you at four total. If you try to run this on three nodes and one goes down, the remaining two are carrying 15,000 connections each, which blows past the per-node ceiling and you will see enrollment failures and session drops before you even finish reading the alert.
Isolde G.Apr 26, 2026Solid N+1 walkthrough, and worth flagging for anyone studying the hybrid path that once you migrate that workload to Citrix Endpoint Management on Citrix Cloud the node count math shifts entirely to Citrix-managed infrastructure, so the capacity planning question on the exam becomes about connector redundancy and zone placement rather than raw node arithmetic.
Orla P.May 6, 2026Three looks right at first glance because 30,000 connections divided by 10,000 per node gets you there, but the question says the cluster must sustain the loss of one node and still carry the full load, so you need that fourth server as your N+1 buffer, which puts you firmly at C, Four.
Jovan I.May 6, 2026Orla has the N+1 logic right, but the real constraint to call out is that each surviving node after a failure must still stay below its rated 10,000-connection ceiling, so the math is ceil(30,000 / 10,000) plus one redundant node, not just a loose buffer.
Hiroshi T.May 20, 2026Thought B was enough until I checked the sizing guide: 4 nodes handles 30k with one spare.
Jovan I.May 21, 2026Four nodes gets you the N+1 headroom but watch your SSL throughput per node at that session count, because the spare does not help you if the active three are already CPU-bound on handshakes before the fourth even kicks in.
Isolde G.May 12, 2026Four is right. At roughly 10,000 device connections per node with those specs, you need four nodes so that when one drops for maintenance or fails, the remaining three can still carry the full 30,000-connection load without degrading the environment.
Jovan I.May 14, 2026Solid N+1 math, though I would double-check whether that 10,000-connection ceiling is a platform license limit or the actual SSL TPS ceiling on your hardware, because those two numbers rarely match and the lower one is the real governor when you start shedding a node.