A PaaS Provider wants to start offering private cloud solutions to its customers. It has tasked its internal team of cloud architects with recommending an architectural design that supports the new…

Question

Options

• ASingle-tenant
• BDefault tenant-managed multitenancy
• CIndividual tenant-managed multitenancy
• DMultiple individual vRealize Automation deployments

• A
  19% (8)
• B
  5% (2)
• C
  67% (29)
• D
  9% (4)

Explanation

Individual tenant-managed multitenancy (C) is correct because it allows a single, centralized VMware Cloud Management Platform (vRealize Automation) to host multiple isolated tenant environments, where each customer independently manages their own private cloud - satisfying both the "private cloud per customer" and "centralized platform" requirements simultaneously.

Why the distractors fail:

• A (Single-tenant): One platform serves one customer only - the provider would need separate deployments per customer, destroying centralization.
• B (Default tenant-managed multitenancy): The provider's admin manages tenant resources on behalf of customers; customers don't get autonomous control over their own private cloud, which undermines the "private cloud" offering.
• D (Multiple individual vRA deployments): Directly contradicts the goal of leveraging the existing centralized platform - spinning up separate vRA instances per customer is operationally expensive and abandons the unified management layer.

Memory tip: Anchor on the two constraints in the question - centralized platform (rules out D and A) + customers manage their own environment (rules out B). "Individual tenant-managed" = one platform, many self-governing tenants. If customers have the keys to their own space in a shared building, that's individual tenant management.

No community discussion yet for this question.