Free VMware 2V0-13.25 Actual Exam Questions - Question 15 Discussion
operates independently and requires dedicated development environments.
Requirement: Provide self-service provisioning through VCF Automation.
Which two design decisions should be included? (Choose two.)
Option B and C, because separate ADs need distinct tenants for proper segregation.
B, C. Since each business unit has its own AD, it makes the most sense to map each tenant to its dedicated AD instance (B), keeping authentication clean and isolated. And creating a tenant per business unit (C) aligns with their independent operation and isolation needs. Projects are more for organizing workloads inside tenants, so using tenants for separation here feels right.
B/C? Each unit’s separate AD fits better at the tenant level (B), and creating a tenant per business unit (C) keeps things isolated and clean. Projects feel too granular for this scope.
Maybe B and C. Since each unit has its own AD, it’s cleaner to assign each tenant its dedicated AD instance rather than mixing them. Separate tenants (C) match the independent operation requirement well.
D imo, projects are usually for organizing workloads inside a tenant, not for isolating whole business units. So having separate tenants (C) and using their own ADs (B) fits better here.
C imo, tenants are meant to isolate different business units, so each should get its own tenant. That way, the environments and permissions stay clean and separated. B also makes sense because the question says each unit has its own AD instance and operates independently, so using their dedicated AD per tenant keeps things straightforward without forcing all units onto a shared directory. This avoids potential security or management issues if everything was tied to one corporate AD.
Makes sense to keep the AD separate since units are independent, so B fits. Also, tenants are good for isolation, so C seems solid here.
It’s B and C, since each unit needs separate AD and independent tenants for isolation.
B C imo, each unit keeps its own AD and gets its own tenant for isolation.
It’s C and D for me. Creating a tenant for each business unit (C) aligns with their independence, and setting up a project per unit (D) helps organize development environments within those tenants. Using projects allows better resource segregation without mixing everything under one tenant. Also, since projects can be tied to specific AD instances, it makes sense to separate them like this rather than trying to configure all ADs directly at the tenant level. This way, they maintain autonomy while still leveraging VCF Automation’s structure efficiently.
It’s C and B. Having a tenant per business unit fits their independence, and using their own AD instance for auth keeps user management simple without forcing a central directory.
D. Creating a project per business unit makes sense since projects are designed to manage resources and permissions within a tenant. Since the units already have separate AD instances, it’s more practical to have tenants per unit (C) and then manage resources inside those tenants via projects (D). That keeps things organized and aligns with the independent operation requirement. Using projects for each unit also fits better with the self-service provisioning goal by isolating development environments clearly.
Makes sense to me that each business unit needs its own VCF Automation tenant (C) since they’re independent and have separate ADs. Also, sticking with their dedicated AD instances for authentication (B) avoids any potential conflicts or confusion from using a shared corporate AD. This way, each business unit keeps control and isolation over their own environments and users.
It’s B and C for me. Since each business unit has its own AD, using their dedicated AD instance (B) avoids the complexity of syncing or forcing everyone into a corporate AD. Plus, creating a separate tenant per business unit (C) aligns with that separation, giving each unit control and isolation. Options like D or E feel off because projects are generally smaller scopes inside tenants, and you want auth tied to the tenant level, not project. So splitting by tenant and AD makes the most sense here.
Maybe C and B. Separate ADs mean separate tenants for clean separation, so each unit manages its own users and environments without overlap.
Definitely C and B. Each business unit needs its own VCF Automation tenant and should use its own AD instance to keep them independent.