Exam Professional Cloud Architect topic 1 question 13 discussion

C is the answer

Key word: This behavior was not reported before the update A - Not Correct as it was working before with same ISP B - New code update caused an issue- why to open support ticket C - I agree with C D - This requires downtime and live prod affected too

1. Prioritize User Experience: Rolling back to a stable version quickly minimizes user impact and restores the application to a functional state. This should be the immediate first step. 2. Controlled Environment: Diagnosing the issue in a development/test/staging environment allows you to investigate without affecting real users. You can reproduce the problem, gather data, and test potential solutions safely. 3. Powerful Diagnostic Tools: Stackdriver Trace helps you pinpoint performance bottlenecks by tracing requests across your application. Stackdriver Logging provides detailed logs to understand application behavior and identify errors.

C is correct

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? Here the application (our code) is updated and only some users are facing lantecy (Cloud Trace) issue. The issue is not with ISP (A), Not an issue with Google (B). Rollback must be done as mitigation, but testing should be done in Non-Prod environments (C), not on prod environment (D). Hence C is correct answer.

I'm going for C. While D may be "better" in case this is an issue that only occurs in production, I think that keeping the disruption at minimum would be the best practice, which D would not really do. Plus, if the problem is load related, having this released at a quieter period may not surface the problem either.

Although it sounds like the right answer to do network tracing in stg again, this may be a network pass-through related issue and it is felt that the problem may not be reproduced if not checked in a prod environment.

Although it sounds like the right answer to do network tracing in stg again, this may be a network pass-through related issue and it is felt that the problem may not be reproduced if not checked in a prod environment.

should be C

C is the answer

Option C is also a valid strategy in this scenario. Rolling back to an earlier known good release initially and using Stackdriver Trace and Logging to diagnose the problem in a development/test/staging environment can help diagnose the issue without impacting production users. However, the reason why option D may be a better approach is that it allows for investigation during a quieter period, which can reduce the impact of any issues that may occur during the investigation. Rolling back to a known good release and then pushing the release again at a quieter period can help to ensure that users are not impacted during the investigation.

ok for C

C is the correct answer

C is perfect to troubleshoot latency issues with app

C. Roll back to an earlier known good release initially, then use Stackdriver Trace and Logging to diagnose the problem in a development/test/staging environment A and B are not relevant D - no IT manager will ever allow re-deployment of erroneous code in production, even in a quiet period...!

correct answer is C use the standard practise

How come everyone is agreeing to C!! In option C after rollback, the investigation will happen only on the earlier good release. Whereas in option D, all the troubleshooting will happen on current/problematic build. Option D should be the right option as it resolves the issue in short term and provides room for further investigation without downtime.