3V0-32.23 · Question #18
A customer will use their vRealize Automation solution to provision and manage both production and development workloads. During workshops, the customer has communicated the following information…
The correct answer is A. Add the Application Owners and Infrastructure Operators groups to the production project. C. Define a Cloud Assembly project for production and another for development. D. Define an instance limit for projects using the development Cloud Zone. Three design pillars address the stated requirements: environment separation (C), production access control (A), and development throttling (D). Creating separate Cloud Assembly projects for production and development (C) is the foundational design decision - projects are the…
Question
A customer will use their vRealize Automation solution to provision and manage both production and development workloads. During workshops, the customer has communicated the following information about the environment:
- The production and development workloads are deployed to separate
vCenter Servers.
- Three different user groups have been identified for access to the
solution: Application Developers, Application Owners, and Infrastructure Operators The customer has communicated the following requirements:
- Only Application Owners and Infrastructure Operators may be permitted
to deploy production workloads.
- A limit should be applied to the number of development workloads
concurrently deployed by each user type.
- Application Owners must not be able to view or modify another user's
deployment(s). In addition to the creation of separate Production and Development Cloud Zones, which three design decisions meet the requirements? (Choose three.)
Options
- AAdd the Application Owners and Infrastructure Operators groups to the production project.
- BDefine a Cloud Assembly project for each user group.
- CDefine a Cloud Assembly project for production and another for development.
- DDefine an instance limit for projects using the development Cloud Zone.
- EDefine a priority of 0 for the production Cloud Zone in the project used by Application Developers.
- FThe deployment sharing option should be turned off for the Application Owners project.
How the community answered
(27 responses)- A78% (21)
- B4% (1)
- E7% (2)
- F11% (3)
Explanation
Three design pillars address the stated requirements: environment separation (C), production access control (A), and development throttling (D).
Creating separate Cloud Assembly projects for production and development (C) is the foundational design decision - projects are the primary boundary in vRA for applying different cloud zones, user memberships, and policies per environment. Adding only Application Owners and Infrastructure Operators to the production project (A) enforces the access restriction without touching Application Developers, who are simply absent from that project. Defining instance limits on the development Cloud Zone within each project (D) directly caps concurrent development workloads per project, satisfying the per-user-type limit requirement.
Why the distractors fail:
- B (project per user group) splits on the wrong axis - environment separation (prod vs. dev) must come first; user grouping is handled via project membership, not separate projects.
- E (priority 0 for production Cloud Zone in App Developers project) is a placement preference, not an access gate - priority controls where vRA prefers to place workloads, not who is permitted to deploy there.
- F (deployment sharing off for "Application Owners project") references a project that doesn't exist in the C design; the production project contains both Application Owners and Infrastructure Operators, so F describes a structure that contradicts C.
Memory tip: Think ACD = Access → Compartmentalize → Deploy-limit - first gate who enters production (A), then wall off the environments (C), then throttle what development users can spin up (D).
Topics
Community Discussion
No community discussion yet for this question.