An administrator must configure a new Project in the Development tenant of VCF Automation. The requirement is to minimize ongoing management overhead as new developers onboard. Which four steps should be taken? (Choose four.)
A.
Log in to the Development tenant as a Project Administrator.
B.
Assign at least one Cloud Zone to the Project.
C.
Assign both Project Administrators and Project Members to the Project using Active Directory Users.
D.
Create a new Project.
E.
Assign at least one Namespace to the Project.
F.
Log in to the Development tenant as an Organization Administrator.
G.
Assign both Project Administrators and Project Members to the Project using Active Directory Groups.
According to the VCF Automation 9.0 Guide, project creation requires administrative login at the tenant level: “To create a new project, log in as a Project Administrator of that tenant.” . After creation, projects must be mapped to Cloud Zones to determine compute placement. The document also emphasizes: “For scalable user management, assign groups from Active Directory to roles within projects rather than individual users.” This reduces management overhead as new members join.
Namespaces are not mandatory unless Kubernetes Supervisor is being integrated, which is not required in this scenario. Likewise, logging in as an Organization Administrator (F) is not needed for tenant-level project creation. Therefore, the correct steps are: Log in as Project Admin (A), Create a Project (D), Assign a Cloud Zone (B), and Use Active Directory Groups for membership (G). This ensures minimal ongoing administrative effort.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit