A DevOps team wants to be able to work on the same source code repository. The team has the following requirements for their development workflow and repository access controls:
Only team members can clone the repository and create new branches.
A production-ready code state should be isolated from any untested code changes.
Code changes should be approved by another team member before merging to the production-ready master branch. All code change approvals must have an audit record. New team members can quickly modify code. Which combination of actions will these requirements? (Choose three.)

Question

A DevOps team wants to be able to work on the same source code repository. The team has the following requirements for their development workflow and repository access controls:

Only team members can clone the repository and create new branches.

A production-ready code state should be isolated from any untested code changes.

Code changes should be approved by another team member before merging to the production-ready master branch. All code change approvals must have an audit record. New team members can quickly modify code. Which combination of actions will these requirements? (Choose three.)

Juan Gonzalez · Accepted Answer

Check out the master branch and develop new features locally on a feature branch to keep the production-ready code isolated. Ask team members to review the changes before committing the changes locally.

Juan Gonzalez · Accepted Answer

Create an AWS CodeCommit repository and an IAM group with permissions to read/write changes to the repository. Add new team members to this group.

Juan Gonzalez · Accepted Answer

Create an AWS CodeCommit repository and an IAM role with permissions to read/write changes to the repository. Attach this IAM role to a single IAM user. Ensure each member of the team uses this IAM user. Provide new team members the credentials to this IAM user.

Juan Gonzalez · Answer

Create a local feature branch from the master branch for new features. Commit the new code and push the changes to the feature branch in the repository.

Juan Gonzalez · Answer

Create a pull request so other team members can review the code changes. Implement any suggestions, pull any additional changes from the master branch, and push to the feature branch again. Merge the master branch with the feature branch.

Juan Gonzalez · Answer

Create a pull request so other team members can review the code changes. Implement any suggestions, pull any additional changes from the master branch, resolve any conflicts, and push to the feature branch again. Merge the feature branch with the master branch.

Question list

List of questions

Question 1

(0)

Question 2

(0)

Question 3

(0)

Question 4

(0)

Question 5

(0)

Question 6

(0)

Question 7

(0)

Question 8

(0)

Question 9

(0)

Question 10

(0)

Related questions

Question 120 - DOP-C01 discussion

Suggested answer: A, B, C

0 comments