Practice Test 1 | Google Cloud Certified Professional Cloud Architect | Dumps | Mock Test
Your customer is receiving reports that their recently updated Google App Engine application is taking approximately 30 seconds to load for some of their users. This behavior was not reported before the update. What strategy should you take?
A. Work with your ISP to diagnose the problem.
B. Open a support ticket to ask for network capture and flow data to diagnose the problem, then roll back your application.
C. Roll back to an earlier known good release initially, then use Operations Suite (formerly Stackdriver) Trace and logging to diagnose the problem in a development/test/staging environment.
D. Roll back to an earlier known good release, then push the release again at a quieter period to investigate. Then use Operations Suite (formerly Stackdriver) Trace and logging to diagnose the problem.
Correct Answer C
Explanation
A – You ISP normally won’t help in this level. Also, the problem most likely is caused by recent update. The good approach is to rollback first and then investigate later. Similarly, this also apply to answer B.
To investigate this kind of issue, use Operations Suite (formerly Stackdriver) Trace and logging to diagnose the bottleneck
C and D have something in common for both “use Operations Suite (formerly Stackdriver) Trace and logging”, either in test/dev or in production environment and “Roll back to an earlier known good release”. At this moment, only the “earlier known good release” version starts receiving traffic.
The difference lines between C’s “to diagnose the problem in a development/test/staging environment.” and D’s “then push the release again at a quieter period to investigate”.
If you want to debug in production environments, “then push the release again at a quieter period to investigate” is not necessary – you can simply switch “default” version or split the traffic between the “earlier known good release” version and the new problem version.
Essentially D’s “then push the release again at a quieter period to investigate” disqualifies itself as good answer – the default would be the new pushed version (the one with problem) starts receiving traffic “at a quieter period”, and the slow loading users may not present. But with answer C in development/test/staging environment, you can arbitrarily load those suffering users if you know them or simulate production load to reveal the problem users and then do further investigation.
So, C is the correct answer: First, rollback to “the earlier known good release” and then use the test/dev/staging envs to investigate.
Additional Resource
https://cloud.google.com/appengine/docs/flexible/python/testing-and-deploying-your-app
Testing and Deploying your Application
Comments are closed, but trackbacks and pingbacks are open.