Free Google Associate Cloud Engineer Actual Exam Questions - Question 9 Discussion
intended project. You want to find out why this happened and where the application deployed. What
should you do?
A vs D? The app.yaml usually doesn’t specify the project, it mostly deals with app settings like runtime, handlers, etc. The actual project used depends on your gcloud config or the --project flag during deploy. So checking your active gcloud config with gcloud config list (D) makes more sense to figure out which project was targeted when deploying. If you accidentally had a different project active, that’d explain where it went.
A imo, because the app.yaml file usually contains the project ID or settings that tie the app to a specific project. If that’s misconfigured, it could explain why the app deployed somewhere unexpected. Checking config alone (like in D) tells you the environment but not what’s defined in your app’s config files. It’s worth verifying both, but the root cause might be in the project settings inside app.yaml.
D imo, since you wanna confirm which project your gcloud is pointed at during deploy.
Makes sense to check the active project setting first since gcloud uses that for deploys unless overridden. D is the quickest way to confirm where the deploy went.
D. The quickest way to see which project gcloud is currently set to deploy to is by running gcloud config list. It shows the active project that the CLI uses unless overridden by a flag.
Maybe A too, since app.yaml usually has the project info if it’s specified there.
D/B? I think D is the best choice because gcloud config list shows the current active project, which often causes confusion if you don’t specify --project explicitly. But I’m also wondering if checking the app.yaml file (A) might help since it could have some project-specific settings that might affect deployment. The other options don’t seem related to app engine deployment targets. So mainly D, but a quick look at app.yaml wouldn’t hurt either to rule out any misconfigurations there.
Maybe D because gcloud config list actually shows the active project you’re using when deploying. Without that, it’s hard to tell where your app went. The other options don’t really track the deployment target.
D, the app.yaml won’t show which project you deployed to, gcloud config list should reveal it.