Answer-first summary for fast verification
Answer: In the Cloud Shell, navigate to the directory containing app.yaml and execute 'gcloud app deploy app.yaml'.
The correct action is to use 'gcloud app deploy app.yaml' to deploy the new version to App Engine. This is because the application was manually deployed, making Cloud Build irrelevant for this scenario. 'gcloud app browse' is used to check if the app is running, not for deployment. For more details, refer to the documentation on deploying from Cloud Source Repositories to 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 hasn't been updated. What's the next step?
A
Ensure the Cloud Build Service Account has permissions to deploy to App Engine
B
In the Cloud Shell, navigate to the directory containing app.yaml and execute 'gcloud app browse'.
C
Verify the Cloud Build trigger is correctly configured and push the update again.
D
In the Cloud Shell, navigate to the directory containing app.yaml and execute 'gcloud app deploy app.yaml'.
No comments yet.