Question-40: Users are free to create code on GAE without being distracted by concerns about IT operations and back-end infrastructure since the platform is completely managed. Users are able to construct a variety of apps thanks to the APIs that are pre-installed. Having access to application logs makes it easier to conduct monitoring and troubleshooting in production. Pricing based on the amount of usage. Your client has received feedback that the most current version of their Google App Engine application takes roughly 30 seconds to load for certain of its customers. Before the upgrade, nobody has mentioned exhibiting this behaviour. Which course of action should you take?
A. Consult with your Internet service provider in order to identify the issue.
B. After opening a ticket with support to report the issue and requesting network capture and flow data so the issue can be diagnosed, roll back your application.
C. The first step is to revert to a previous version that was validated and tested, and then you should utilise Stackdriver Trace and Logging to identify the issue in a development, test, or staging environment.
D. Roll back to an earlier release that was known to be good, then try pushing the release again during a period when there is less activity to investigate. The following step is to conduct a diagnostic using Stackdriver Trace and Logging.
Correct Answer

Get All 340 Questions and Answer for Google Professional Cloud Architect

: 3 Explanation: This behavior was not reported before the update Option-1 - Not Correct as it was working before with same ISP Option-2 - New code update caused an issue- why to open support ticket Option-3 - Agree =, Option-4 - This requires downtime and live prod affected too Then use Stackdriver Trace and Logging to diagnose the problem in a development/test/staging environment they are NOT asking us to set up Dev/Text/Stage. Meaning the environment already exists and we have to use it. then use Stackdriver Trace and Logging to diagnose the problem in a development/test/staging environment this is not asking for a set environment either, it just says to diagnose problems in another environment so Option-3. 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 Option-2 are not relevant Option-4 - no IT manager will ever allow re-deployment of erroneous code in production, Option-3 is the ans For all those calling for Option-4 , the option don't tell they will install stackdriver, but will use it to analyze the logs. Then deploying back the faulty code without fixing does not make sense.