You need to create a custom IAM role for use with a GCP service. All permissions in the role must be suitable for production use. You also want to clearly share with your organization the status of the custom role. This will be the first version of the custom role. What should you do?
To create a custom IAM role for production use in GCP, you should use permissions that have the 'supported' support level, as they are fully supported in custom roles and suitable for production environments. The 'testing' support level permissions are not recommended for production because they can exhibit unexpected behavior. Since this will be the first version of the custom role, the appropriate stage to set is ALPHA to indicate that the role is still being developed or tested and is not yet ready for widespread use.
You need a custom role with permissions supported in prod and you want to publish the status of the role. https://cloud.google.com/iam/docs/custom-roles-permissions-support SUPPORTED The permission is fully supported in custom roles. TESTING The permission is being tested to check its compatibility with custom roles. You can include the permission in custom roles, but you might see unexpected behavior. Not recommended for production use. NOT_SUPPORTED The permission is not supported in custom roles. You can't use TESTING as it is not good for prod. And you need first version which should be ALPHA. Answer should be A.
good job
WAY TO GO. VERY CLEAR EXP INDEED
Correct Answer is (A): Testing and deploying Custom roles include a launch stage, which is stored in the stage property for the role. The launch stage is informational; it helps you keep track of whether each role is ready for widespread use. Each custom role can have one of the following launch stages: Launch stages ALPHA The role is still being developed or tested, or it includes permissions for Google Cloud services or features that are not yet public. It is not ready for widespread use. BETA The role has been tested on a limited basis, or it includes permissions for Google Cloud services or features that are not generally available. GA The role has been widely tested, and all of its permissions are for Google Cloud services or features that are generally available.
Correct Answer is (A): Continuation Support levels for permissions in custom roles You can include many, but not all, Identity and Access Management (IAM) permissions in custom roles. Each permission has one of the following support levels: Support level Description SUPPORTED The permission is fully supported in custom roles. TESTING The permission is being tested to check its compatibility with custom roles. You can include the permission in custom roles, but you might see unexpected behavior. Not recommended for production use. NOT_SUPPORTED The permission is not supported in custom roles. The first version of the Custom Role is ALPHA then suitable to productions all permissions in "Supported"...
ESP_SAP There is a discrepancy between your first post and the second post. Compare these two sentences; 1st POST - ALPHA The role is still being developed or tested, or it includes permissions for Google Cloud services or features that are not yet public. It is not ready for widespread use. 2nd POST - SUPPORTED The permission is fully supported in custom roles. Are you still going to go with A ?
Here ALPHA is for Google cloud feature, only informational. given to identify whether the feature is fully available as a service. and SUPPORTED -- is for a custom role which is supported by Google cloud, meaning any support is provided by Google cloud
A - SUPPORTED -The permission is fully supported in custom roles. role stage, the stage transitions from ALPHA –> BETA –> GA The only option that satisfies “ALPHA” stage with “SUPPORTED” support level is Use permissions in your role that use the SUPPORTED support level for role permissions. Set the role stage to ALPHA while testing the role permissions
A is the correct answer
A is the only right solution.
Its A cause in first place it need to be supported not in testing phase because the question is asking it to be in ready phase secondly then needed to be shared in testing phase
A is correct. Use permissions in your role that use the ג€˜supportedג€™ support level for role permissions. Set the role stage to ALPHA while testing the role permissions.
A is correct
A is right
Use permissions in your role that use the 'supported' support level for role permissions. Set the role stage to ALPHA while testing the role permissions.
It must be suitable for production so Supported permissions only. Plus, it is your first version of the custom role, so you need to check if all is good, then ALPHA.
why not B?
Because ...FIRST VERSION... is ALPHA.
You need a custom role with permissions supported in prod and you want to publish the status of the role. https://cloud.google.com/iam/docs/custom-roles-permissions-support SUPPORTED The permission is fully supported in custom roles.
Answer is A, as you need for production and you dont neeed testing for it and you need first version , so it will be ALPHA , not beta
A is correct answer. https://cloud.google.com/iam/docs/roles-overview#custom-role-supported-permissions https://cloud.google.com/iam/docs/roles-overview#custom-role-testing-deploying
I will go with A
Let's break down the options: A & B: "supported" is the ideal choice for production roles as they are well-tested and documented. BETA is for pre-release features, not initial testing. C: "testing" permissions are unstable and not suited for production. ALPHA stage is for internal testing before even BETA. D: Same issue as option C - "testing" permissions are not for production, and ALPHA is an earlier stage than BETA. Therefore, the most suitable approach is: A. Use permissions in your role that use the 'supported' support level for role permissions. Set the role stage to ALPHA while testing the role permissions.