A solutions architect of an IT company is considering to use CodeStar for a new project that needs high scalability and availability.More importantly, he prefers utilizing its powerful management features so that he could control the whole project status including team membership.
The team that is working on this project contains 3 developers and 1 UI designer.
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer - D.
One key feature of CodeStar is that you could Add Team Members to an AWS CodeStar Project.
If you have the owner role in an AWS CodeStar project or have the AWSCodeStarFullAccess policy applied to your IAM user, you can add other IAM users to the project team.
This is a simple process that applies an AWS CodeStar role (owner, contributor, or viewer) to the user.
These roles are per-project and can be customized.
Benefits of AWS CodeStar roles and team membership include:
You do not have to manually configure permissions in IAM for your team members.
You can easily change a team member's level of access to a project.
Users can access project dashboards in the AWS CodeStar console only if they are team members.
User access to a project is defined by role.
And details please refer to.
https://docs.aws.amazon.com/codestar/latest/userguide/how-to-add-team-member.html.Option A is incorrect: Because there is no role of Moderator in CodeStar.
For read-only access, the role of Viewer is needed.
Option B and C are incorrect: For CodeStar, the proper method to manage team membership is to use its “Team members” dashboard or CLI to allocate roles.
Option A suggests adding the developers as Contributors, the UI designer as a Viewer, and the Scrum master as a Moderator on the "Team Members" page in the CodeStar management console. This option is partially correct. Contributors can push changes to the code repository, while Viewers can only read the code. Moderators can manage the team, create new resources, and update project settings. However, it is not clear whether the Scrum master needs moderator access, and if the UI designer needs only read-only access. Thus, this option may not be the best fit for the team.
Option B suggests attaching relevant CodeStar policies to each IAM user in the IAM console, such as the policy for the solutions architect who is the admin. The policy allows full access to CodeStar resources. While this policy grants the admin complete control over CodeStar resources, it does not specify the appropriate access levels for the other team members. Thus, this option is not the best fit for the team.
Option C suggests attaching relevant CodeStar policies to each IAM user in the IAM console, such as the policy for the admin. The policy allows creating, associating, and updating team members and projects, as well as deleting projects. This policy grants the admin a high level of control over CodeStar resources, but it also specifies the appropriate access levels for the other team members, such as the ability to associate, disassociate, or update team members. Thus, this option is a good fit for the team.
Option D suggests adding the developers as Contributors, the UI designer as a Viewer, and the Scrum master as a Viewer on the "Team Members" page in the CodeStar management console. This option is not the best fit for the team since the Scrum master may require a higher access level than Viewer to manage the project status.
In summary, Option C is the most appropriate choice since it grants the admin a high level of control over CodeStar resources, while also specifying the appropriate access levels for the other team members.