You are deploying an application to Cloud Run. The application requires a password to start. Your organization requires that all passwords are rotated every 24 hours, and your application must have…

The correct answer is B. Store the password in Secret Manager and mount the secret as a volume within the application. https://cloud.google.com/run/docs/configuring/services/secrets Mount each secret as a volume, which makes the secret available to the container as files. Reading a volume always fetches the secret value from Secret Manager, so it can be used with the latest version. This method…

Submitted by fatima_kr· Apr 18, 2026Applying site reliability engineering principles to a service

Question

You are deploying an application to Cloud Run. The application requires a password to start. Your organization requires that all passwords are rotated every 24 hours, and your application must have the latest password. You need to deploy the application with no downtime. What should you do?

Options

AStore the password in Secret Manager and send the secret to the application by using
BStore the password in Secret Manager and mount the secret as a volume within the application.
CUse Cloud Build to add your password into the application container at build time. Ensure that
DStore the password directly in the code. Use Cloud Build to rebuild and deploy the application

How the community answered

(31 responses)

A
10% (3)
B
74% (23)
C
3% (1)
D
13% (4)

Explanation

https://cloud.google.com/run/docs/configuring/services/secrets Mount each secret as a volume, which makes the secret available to the container as files. Reading a volume always fetches the secret value from Secret Manager, so it can be used with the latest version. This method also works well with secret rotation.

Topics

#Secret Management#Cloud Run#Password Rotation#No Downtime Deployment

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Practice