Answer-first summary for fast verification
Answer: 1. Ensure all permissions in the role have a ‘supported‘ support level. 2. Set the role stage to ALPHA during permission testing.
**A is correct** because custom roles feature a launch stage, indicated by the `stage` property, which helps track the role's readiness for widespread use. Setting the stage to ALPHA signifies the role is under development or testing, or includes permissions for services/features not yet public, making it unsuitable for widespread use at this stage. **B is incorrect** as BETA indicates limited testing or permissions for not generally available services/features, which doesn't ensure all permissions are ‘supported‘ for production. **C and D are incorrect** because permissions with a ‘testing’ status may not be fully supported for custom roles, risking production stability. The correct approach combines ‘supported‘ permissions with an ALPHA stage for initial testing. [Learn more about custom roles and permissions support](https://cloud.google.com/iam/docs/custom-roles-permissions-support).
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
At a leading tech firm specializing in global CRM solutions hosted on GCP, a project requires the creation of a custom IAM role for a specific use case. The role's permissions must be production-ready, and the security team needs to monitor its status, acknowledging it's the first version with potential future updates. What is the best approach?
A
B
C
D
No comments yet.