A cloud engineer needs to enable the Secret Manager API (`secretmanager.googleapis.com`) for a newly created Google Cloud project named `security-vault-prod` using the `gcloud` CLI, ensuring that the target environment is configured before enablement and verified afterward. Place the administrative steps in the correct chronological sequence from start to finish.
- 1Set the active `gcloud` configuration to target the `security-vault-prod` project.
- 2List enabled APIs in the project to verify that `secretmanager.googleapis.com` is not already enabled.
- 3Execute the enablement command for `secretmanager.googleapis.com`.
- 4Filter the list of enabled services to confirm that `secretmanager.googleapis.com` displays an state of enabled.
Cevap
The correct operational sequence is: 1) Set the active `gcloud` project context to `security-vault-prod`, 2) Inspect currently enabled APIs to check state, 3) Execute the `gcloud services enable` command for `secretmanager.googleapis.com`, and 4) Verify successful activation by filtering enabled services.
The standard sequence for API management requires initializing the target CLI project context first, checking current state, enabling the service API, and validating activation upon completion.
Adım Adım Çözüm
Anahtar Kavram
Standard operational workflow for managing and enabling Google Cloud service APIs using the gcloud CLI tool.