An organization wants to provide automated self-service IaaS catalog to all departments within the organization. The key stakeholders have asked for the platform to be resilient to component…

Question

Options

• ADeploy single node deployment and use tenants to separate the departments.
• BDeploy single node deployment and use projects to separate the departments.
• CDeploy multi-node deployment and use projects to separate the departments.
• DDeploy multi-node deployment and use tenants to separate the departments.

• A
  3% (1)
• B
  7% (2)
• C
  72% (21)
• D
  17% (5)

Explanation

Option C is correct because it satisfies both business requirements simultaneously: a multi-node deployment eliminates single points of failure, providing the resilience the stakeholders require, while projects allow all departments to share the same underlying infrastructure but maintain isolated visibility and management of their own machines - precisely the logical separation described.

Why the distractors fail:

• A & B (single-node): A single-node deployment is a single point of failure - if that node goes down, the entire platform is unavailable. This directly contradicts the resilience requirement, regardless of how departments are separated.
• D (multi-node + tenants): Multi-node is correct for resilience, but tenants typically represent fully separate, independent deployments or top-level organizational boundaries - not the fine-grained, shared-infrastructure isolation needed for departments within the same organization.

Memory tip: Think "Projects = partitions, Tenants = totally separate." Projects carve up one shared platform (like office suites in one building), while tenants imply distinct, standalone environments (like separate buildings). Pair that with "Multi = More resilient" and you'll lock in the C answer: multi-node for resilience, projects for departmental isolation.

No community discussion yet for this question.