Answer-first summary for fast verification
Answer: 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
The correct answer is C. The behavior of the application taking a longer time to load was not observed before the update, implying the issue originates from the recent changes. Rolling back to a known good release ensures that the application runs smoothly for users while minimizing downtime. Stackdriver Trace and Logging are useful tools to diagnose performance issues, and it's best practice to conduct this diagnostic in a development, test, or staging environment to avoid impacting production. Option A is incorrect because the issue is not likely with the ISP. Option B is less practical as it involves opening a support ticket and rolling back without immediate diagnostics. Option D, while valid, involves re-deploying the problematic release during quieter periods, potentially disrupting service further.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
Your customer has a Google App Engine application that was recently updated. Some users are now reporting that the application takes approximately 30 seconds to load, an issue that was not present before the update. What strategy should you take to address this performance issue?
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 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 Stackdriver Trace and Logging to diagnose the problem