During a design workshop, the customer provided the following requirement: Business units should not be able to interfere with the operations of a different business unit. As a result of this…

Question

Options

• AEach Tenant must use an embedded VCF Operations orchestrator instance.
• BEach Tenant must use an external VCF Operations orchestrator instance.
• CThe Provider Tenant must use the embedded VCF Operations orchestrator instance.
• DAll Tenants must use a single VCF Operations orchestrator instance.
• EThe Provider Tenant must use an external VCF Operations orchestrator instance.

• A
  11% (5)
• B
  60% (27)
• D
  24% (11)
• E
  4% (2)

Explanation

Per the VMware Cloud Foundation 9.0.1 and 9.0.4 Architecture and Automation Design Guides, VCF Automation enables multi-tenancy by assigning dedicated orchestration instances per organization for secure separation of workflows. The documentation specifies: "The embedded VCF Operations orchestrator is installed by default as part of the Provider Consumption Organization. Each tenant organization that requires workflow autonomy must deploy its own external VCF Operations orchestrator instance." Thus, in a multi-tenant model: The Provider Tenant uses the embedded VCF Operations Orchestrator instance to manage global workflows. Each Tenant Organization must use its own external orchestrator instance for isolation, control, and workflow management. This design ensures logical separation, prevents cross-tenant interference, and aligns with VCF's security and autonomy best practices for service provider and enterprise models.

No community discussion yet for this question.