Exam Professional Cloud Architect topic 11 question 9 discussion

C- I would run the same test suite in cloud) to see what breaks

Question mention that "end-to-end tests covering 100% of their endpoints", "ensure that the move to the cloud does not introduce any new bugs", and "additional testing methods should the *developers* employ to *prevent an outage*" A - Not Correct. Developer can debug the problem, but cannot *prevent* the outage. B - Correct. Developers are responsible for writing unit tests. They already have end-to-end tests for *endpoints* but nothing mentioned about the unit tests. Cloud will auto-scale but you need to define your auto-scaling configuration (desired count, max count etc) and production scale load test will help you to configure the auto-scaling policies C - Not Correct. They already have end-to-end test. Running it on staging environment will not prevent an outage D - Not Correct. Answers says "an impact the new release causes to latency" but question ask for preventing an outage and so this one is ruled out

D they already has 100% covering end-to-end testing, that means unit tests was finished before this so, additional test remains canary in production environment

B is testing scale, C is testing the code is working as intended in the cloud. the question is for bugs, not for scale. It should be C, but I understand why everyone goes for B. Neurodivergents will go for C.

Note the ask "prevent an outage". One of the way to test outage scenarios is through load testing. Option B covers this where as option C only covers checking the intended behaviour.

Testing pipeline: Unit ---- Integration --- end-to-end If choose B, add additional unit tests. It should be continue to do Integrationt test and end-to-end test. But it just has a unit test, then go to produciton scale load test. C should be better, becasue it has finished end-to-end tests before, so for move to the cloud, it should be test the end-to-end in cloud preproduction enviroment to check whethere it's also working fine on cloud. https://cloud.google.com/architecture/building-production-ready-data-pipelines-using-dataflow-developing-and-testing#end-to-end_tests

vote B

end-to-end is already present, go for additional tests

It should be B as for all those going with C if you do all staging you will still leave out the performance test that scales the application which is covered in B that means even if the application works well but will not scale properly will lead to an outage, which we are asked to prevent.

B. They should add additional unit tests and production scale load tests on their cloud staging environment.

Answer is B

Answer is B (but C... uff... is also possible, but as the question says end-to-end is already done)

B is ok

Question asks about "ADDITIONAL testing methods". B adds production scale load tests. C should also be executed in a new cloud env but this question dosn't ask for this. In real life serious projects, B and C are mandatory (end to end and perf tests). Should be B.

Should be B Reasoning: They already had end-to-end contract tests coverage for all their service(s) endpoints. So, additionally they should add unit test coverage and perform prod load tests in staging environment which will help find out performance related issues before deploying it to production.

Obviously C. Yes they have end-to-end tests on prem with 100% coverage, however this hasn't been tested in the cloud yet.

B vs C B sounds right other than additional "unit" test. C is nothing wrong but not mentioning load. I will throw a dime to decide which to choose.