A user attempts to deploy a catalog item into a vSphere Namespace in a VMware Cloud Foundation (VCF) Automation Organization for All Apps. The catalog item will not deploy into zone3. The following…

Question

Options

• AThe user does not have Project Advanced User role for the vSphere Namespace.
• BThe vSphere Namespace is assigned the default large vSphere Namespace Class.
• CThe vSphere Namespace does not include zone3.
• DThe user does not have the Project User role for the vSphere Namespace.

• A
  7% (4)
• B
  4% (2)
• C
  76% (42)
• D
  13% (7)

Explanation

In VMware Cloud Foundation (VCF) Automation for All Apps, a vSphere Namespace can span multiple Supervisor Zones. However, workloads--including catalog item deployments--can only be deployed into zones that are explicitly assigned to that Namespace. The user in the scenario successfully deploys into zone1 and zone2, which confirms that those zones are correctly associated with the Namespace. The failure to deploy into zone3, while deployments into the other zones work, strongly indicates that zone3 is not part of the Namespace configuration. This behavior matches how Supervisor Zones function: A zone must be added to the Namespace in Supervisor configuration. If the zone is not associated, VCF Automation will not present it as an eligible deployment location, and deployment into that zone fails.

No community discussion yet for this question.