Exam AWS DevOps Engineer Professional topic 1 question 70 discussion

the correct answer is A

The answer should be C because of below line in the question: "allow Developers to automatically deploy to both environments when code is changed in the repository". Option A does not talk about deployment.

using the main branch for both production and test code can lead to issues with tracking changes and version control. It can also make it difficult to deploy code automatically to the correct environment. That's why the answer is A and not C.

B and D are eliminated, will make chaos. C is an incomplete version of A. If we do not use CodeCommit, we should combine different env files to different branches, like test, staging, prod....

A) Explains the branching strategy

Correct answer is A. There is nothing that suggests that the code needs to be deployed simultaneously in both environments. It just says automatically to both environments. That doesn't mean the pull request from a feature branch needs to be created against both test and prod at the same time. What A will enable us to do is have the feature engineer submit a pull request into the test branch and have the admin user of the tear branch review and approve the pull request. This should automatically start the deployment into the test environment. Once the code is full tested by the QA resource in the test environment, they will initiate a pull request into the Prod environment. The prod environment admin user will review and approve the pull request at which point the code will be automatically deployment to the Prod environment. With C on the other hand submitting a pull request from the feature branch to the master branch will result in triggering the deployment via both pipelines at the same time which means the code will be deployed into production before testing it in the test environment successfully.

I'll go with A

Answer is A ,as per the question you have to eploy new version of code for testing

C. It cannot be A because you make the same PR to both branches at the same time ONLY when you need a hotfix to prod and test env. In real world you develop in one branch and when you need a release you merge all the dev branch to prod branch (or create a new version from dev branch if you need to support multiple versions). But you NEVER EVER make PRs to both dev and prod branches during development. If you both branches are always the same - why do you need 2 branches ? If your master and testing branches differ then at some point you will have conflicts. Only C makes sense.

With a different test branch, there is no way to know if the same code is deployed to two different environments.

I choice A The difference between A and C is that C uses master branch for the production and testing environment, A uses different branches for the production and testing environment. The better way is A. B,D S3 is not good choice for team working.

Honestly a prefer 3 different branches, A option Event with the C option different pipelines, which event is triggering the pipeline, when i push the commit in the test/prod branch bad idea, manual trigger? not too devOps at least, another type of trigger maybe add more complexity.

different codepipelines for the same branch seems normal

I'll go with A. for those choosing C: So, do you want deploy do production without testing first? what warranties you that the code is functional and its not broken? Yeah, keep deploying untested code to production...its a genius strategy

Correct Answer: C

A is correct

Agreed with A