Answer-first summary for fast verification
Answer: Navigate to the directory containing app.yaml in Cloud Shell and execute `gcloud app deploy app.yaml`.
Options A and D are not applicable since the application was manually deployed, making Cloud Build irrelevant for this scenario. Option B is incorrect because `gcloud app browse` is used to check if the app is running, not to deploy updates. The correct action is Option C: executing `gcloud app deploy app.yaml` in the directory where app.yaml is located will deploy the new version to App Engine. Reference: [Google Cloud Source Repositories Documentation](https://cloud.google.com/source-repositories/docs/integrating-with-app-engine).
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
As a member of the SRE team for a data-processing company, you're managing an application manually deployed to App Engine. The application's source code is in Cloud Source Repositories. A new version has been developed, tested, and approved for production deployment. After pushing the code update to the repository, you notice the old version remains unchanged. What's your next step?
A
Verify the Cloud Build trigger is correctly configured and attempt the update push again.
B
Navigate to the directory containing app.yaml in Cloud Shell and execute gcloud app browse.
C
Navigate to the directory containing app.yaml in Cloud Shell and execute gcloud app deploy app.yaml.
D
Confirm the Cloud Build Service Account has the necessary permissions for App Engine deployment.
No comments yet.