A cloud administrator needs to deploy a containerized data ingestion service named telemetry-ingest to Google Cloud Run. The container listens on the default port 8080 and must execute under a dedicated, non-default service account named [email protected] to interact securely with backend resources. Which gcloud command should the administrator run to deploy the container image gcr.io/prod-data-project/telemetry-ingest:v1 with the correct identity configuration?
- gcloud run deploy telemetry-ingest --image=gcr.io/prod-data-project/telemetry-ingest:v1 --service-account=ingest-worker@prod-data-project.iam.gserviceaccount.comCevap
- Bgcloud run deploy telemetry-ingest --image=gcr.io/prod-data-project/telemetry-ingest:v1 --port=80 --service-account=ingest-worker@prod-data-project.iam.gserviceaccount.com
- Cgcloud functions deploy telemetry-ingest --image=gcr.io/prod-data-project/telemetry-ingest:v1 --service-account=ingest-worker@prod-data-project.iam.gserviceaccount.com
- Dgcloud run deploy telemetry-ingest --image=gcr.io/prod-data-project/telemetry-ingest:v1 --service-account=roles/owner
Cevap
The command 'gcloud run deploy telemetry-ingest --image=gcr.io/prod-data-project/telemetry-ingest:v1 --service-account=ingest-worker@prod-data-project.iam.gserviceaccount.com' correctly deploys the container image while attaching the custom execution service account.
The correct command uses 'gcloud run deploy' with the container image URI and attaches the custom service account email using the '--service-account' flag, matching Cloud Run deployment specifications.
Adım Adım Çözüm
Anahtar Kavram
Deploying containerized workloads to Cloud Run with custom service account execution identity