2V0-16.25 · Question #57
The security team requests the ability to log into VMware vCenter and review datacenter, cluster and network configurations. The following details are provided: - The security team is not authorized…
The correct answer is D. Create a group for the security team, add the users to the group, and assign the group the Read-. Option D is correct because it satisfies both requirements simultaneously: creating individual user accounts ensures each person logs in with unique credentials, grouping them simplifies administration, and assigning the Read-Only role to the group ensures members can view…
Question
The security team requests the ability to log into VMware vCenter and review datacenter, cluster and network configurations. The following details are provided:
- The security team is not authorized to make any changes to the
environment.
- Each user must login with unique credentials.
What steps should the administrator perform to grant access to the security team?
Options
- AShare the password for '[email protected] ' with the security team.
- BCreate a security user, assign the user the Read-Only role, share the credentials with the security
- CCreate a group for the security team, add the users to the group, and assign the group the
- DCreate a group for the security team, add the users to the group, and assign the group the Read-
How the community answered
(21 responses)- B5% (1)
- D95% (20)
Explanation
Option D is correct because it satisfies both requirements simultaneously: creating individual user accounts ensures each person logs in with unique credentials, grouping them simplifies administration, and assigning the Read-Only role to the group ensures members can view configurations without making changes.
Why the distractors fail:
- A violates both requirements - sharing
[email protected]gives full administrative privileges (not read-only) and means everyone uses the same credentials, not unique ones. - B fails the unique credentials requirement - creating a single shared "security user" means the entire team shares one account, making individual accountability impossible.
- C is likely identical in structure to D but assigns a role other than Read-Only (e.g., Administrator or a custom role), which would permit changes the security team is explicitly not authorized to make.
Memory tip: Think of the two constraints as a checklist - "Who?" (unique credentials → individual accounts in a group) and "What?" (no changes → Read-Only role). Any answer that breaks either rule is wrong. Groups + Read-Only is the VMware best practice for granting least-privilege access to multiple users efficiently.
Topics
Community Discussion
No community discussion yet for this question.