MENU
[Building and implementing CI/CD pipelines for a service]
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?
Suggested Answer: B
Get Premium Professional Cloud DevOps Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
16 comments · newest first
HA
Hassie
10 months ago
I thought storing passwords in code was a big no-no? D seems risky.
GA
Gary
10 months ago
I disagree, B seems better for managing secrets.
LU
Lucy
10 months ago
Option A is the best choice! Using Secret Manager is secure.
LE
Levi
11 months ago
Wait, can you really rotate passwords every 24 hours without downtime?
SA
Sabine
11 months ago
A is definitely the way to go, no downtime and secure!
TA
Tamala
11 months ago
Storing the password in the code seems really risky, but I guess option D could work if we automate the rebuild process.
VA
Valentine
11 months ago
I practiced a similar question where we had to manage secrets, and I feel like using environment variables might expose the password during deployment.
CL
Clay
11 months ago
I'm not entirely sure, but I think mounting the secret as a volume could be a better way to handle updates without downtime.
CR
Crista
12 months ago
I remember discussing the importance of using Secret Manager for sensitive data, so option A seems like a good choice.
SY
Sylvie
12 months ago
Cloud Build to add the password at build time? That's an interesting approach. I'll need to make sure the Artifact Registry is locked down tight, but that could be a good solution.
GE
Gertude
1 year ago
Mounting the secret as a volume seems like it could work, but I'm not sure if that's the most secure option. I'll have to research that a bit more.
MA
Maricela
1 year ago
Okay, I think I've got a plan. I'll use Secret Manager to store the password and send it to the application as an environment variable. That way, I can rotate the password easily without any downtime.
HE
Helga
1 year ago
Hmm, storing the password directly in the code seems like a bad idea from a security standpoint. I'll probably rule that out.
VE
Venita
1 year ago
This looks like a tricky one. I'll need to think through the security implications of each approach carefully.
RO
Rosio
1 year ago
I disagree, I believe we should store the password in Secret Manager and mount the secret as a volume within the application.
ET
Ettie
1 year ago
I think we should store the password in Secret Manager and send the secret to the application by using environment variables.