2V0-32.24 Question 102
Select 2You are tasked with configuring access control for a team of administrators in your organization using vRealize Operations, vRealize Log Insight, and vRealize Suite Lifecycle Manager. The team requires permissions to monitor the health of the infrastructure, troubleshoot logs, and manage deployments without having access to modify or delete core configurations. Which approach should you take to configure RBAC across these tools?
- A
Assign the 'Administrator' role in vRealize Operations, 'Super Admin' role in vRealize Log Insight, and 'System Administrator' role in vRealize Suite Lifecycle Manager.
- B
Assign the 'ReadOnly' role in vRealize Operations, 'Viewer' role in vRealize Log Insight, and 'Viewer' role in vRealize Suite Lifecycle Manager.
- C
Create a custom role in vRealize Operations with permissions for health monitoring, assign the 'User' role in vRealize Log Insight, and the 'Deployer' role in vRealize Suite Lifecycle Manager.
- D
Assign the 'PowerUser' role in vRealize Operations, 'Admin' role in vRealize Log Insight, and 'Organization Owner' role in vRealize Suite Lifecycle Manager.
- E
Assign the 'Permissions Administrator' role in vRealize Suite Lifecycle Manager and delegate specific RBAC tasks to the team.
Show answer and explanation
Correct answers: B, C
Explanation
Configuring RBAC in vRealize Operations, vRealize Log Insight, and vRealize Suite Lifecycle Manager requires careful alignment with the team's responsibilities. The correct approach is to grant permissions that meet the requirements, monitoring, troubleshooting logs, and managing deployments, without providing unnecessary access that could lead to accidental modifications in the environment. Option 2 aligns with monitoring and troubleshooting, while Option 3 provides a more tailored approach for deployment management.
- A. Incorrect.
This option grants excessive permissions (e.g., 'Administrator' and 'Super Admin') which go beyond the team's requirements of monitoring, troubleshooting logs, and managing deployments without modifying core configurations.
- B. Correct.
This option provides basic viewing permissions ('ReadOnly' and 'Viewer') that align with the team's need to monitor and troubleshoot, but it lacks the ability to manage deployments, which is required in the scenario.
- C. Correct.
This option allows for a tailored RBAC setup. A custom role in vRealize Operations can limit permissions to health monitoring, the 'User' role in vRealize Log Insight enables log troubleshooting, and the 'Deployer' role in vRealize Suite Lifecycle Manager allows deployment management without access to core configurations.
- D. Incorrect.
This option assigns permissions ('PowerUser', 'Admin', 'Organization Owner') that are too broad and exceed the team's specific needs, potentially introducing risks by providing access to modify or delete core configurations.
- E. Incorrect.
The 'Permissions Administrator' role in vRealize Suite Lifecycle Manager is meant for managing RBAC itself, not for day-to-day infrastructure monitoring, log troubleshooting, or deployment tasks.