You deployed an App Engine application using gcloud app deploy, but it did not deploy to the intended project.
You want to find out why this happened and where the application deployed.
What should you do?
Click on the arrows to vote for the correct answer
A. B. C. D.A.
https://cloud.google.com/endpoints/docs/openapi/troubleshoot-aeflex-deploymentIf you deployed an App Engine application using gcloud app deploy, but it did not deploy to the intended project, there are a few things you can do to troubleshoot the issue.
Option A is the correct answer. You should check the app.yaml file for your application and check project settings. The app.yaml file contains configuration settings for your App Engine application, including the runtime environment, scaling settings, and other options. One of the options in the app.yaml file is the project ID, which specifies the Google Cloud project where the application should be deployed. Make sure that the project ID specified in the app.yaml file matches the intended project ID. If it doesn't match, update the project ID in the app.yaml file and redeploy the application using gcloud app deploy.
Option B is incorrect. The web-application.xml file is not used in App Engine deployments. It is used in Java web applications that are deployed to a Tomcat or Jetty server.
Option C is also incorrect. Deployment Manager is a tool for managing infrastructure deployments, such as virtual machines, networks, and storage buckets. It is not used for deploying App Engine applications.
Option D is not as useful as option A. Running gcloud config list in Cloud Shell will show you the current Google Cloud configuration settings, such as the active project and default region. While this information can be useful, it does not directly help you diagnose why your application did not deploy to the intended project.