A Cloud Engineer is using Google Cloud Deployment Manager templates stored in a central administrative project named `admin-ops-project` to provision VPC networks and Compute Engine instances into a newly created target project named `finance-workload-prod`. The engineer executes the following command from the Google Cloud CLI:
`gcloud deployment-manager deployments create workload-deployment --config=vpc_vm.yaml --project=finance-workload-prod`
The command fails with an error stating that `deploymentmanager.googleapis.com` is disabled or has not been used in project `finance-workload-prod`. The engineer confirms that the Cloud Deployment Manager API is already enabled in `admin-ops-project`. What should the engineer do to resolve this issue?
- Enable the Cloud Deployment Manager API in the target project finance-workload-prod.Cevap
- BRe-run the command with the --project flag set to admin-ops-project so Deployment Manager consumes the API enabled in that project.
- CGrant the primitive Owner role to the Deployment Manager service account at the parent Folder level so API enablement is inherited.
- DAppend the --enable-apis flag to the gcloud deployment-manager deployments create command to automatically enable missing APIs during deployment execution.