MENU
You are deploying a new Cloud SQL instance on Google Cloud using the Cloud SQL Auth proxy. You have identified snippets of application code that need to access the new Cloud SQL instance. The snippets reside and execute on an application server running on a Compute Engine machine. You want to follow Google-recommended practices to set up Identity and Access Management (IAM) as quickly and securely as possible. What should you do?
Suggested Answer: C
Get Premium Professional Cloud Database Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
https://cloud.google.com/sql/docs/mysql/sql-proxy#using-a-service-account
30 comments · newest first
FR
Francine
6 months ago
Yeah, C is definitely the way to go for IAM best practices.
HO
Howard
6 months ago
I feel like A is too risky. Shared accounts can cause issues.
AJ
Aja
6 months ago
True, but C is recommended for automation.
SE
Serina
6 months ago
But what about B? Dedicated accounts seem safer.
JA
Jani
7 months ago
I agree, C makes sense. It’s more manageable.
AN
Andra
7 months ago
I think option C is the best. Service accounts are secure.
ST
Stephaine
7 months ago
Totally agree with B, dedicated accounts help with auditing too.
SL
Slyvia
7 months ago
Wait, why would anyone use a shared account? That sounds risky!
CY
Cyril
7 months ago
C is definitely the best practice for service accounts.
AD
Adria
8 months ago
I disagree, A seems easier to manage.
HA
Hannah
8 months ago
B is the way to go! Dedicated accounts are more secure.
AG
Agustin
8 months ago
I'd go with C. Service accounts are the way of the future, my friend.
AL
Allene
8 months ago
B) and C) are the way to go. Gotta keep that security tight, you know?
KA
Karon
9 months ago
C) For the application server, set up a service account. This is the recommended practice by Google.
SA
Sabrina
9 months ago
B) For each application code, set up a dedicated user account. This ensures better security and accountability.
FL
Florinda
9 months ago
I’m a bit confused about whether a common shared user account is ever recommended. I thought we should avoid that for security reasons.
VA
Vanesa
9 months ago
This question seems similar to one we practiced about IAM roles. I feel like using a common shared user account could lead to security risks.
GR
Gracie
9 months ago
I’m not entirely sure, but I think setting up a service account for the application server might be the best practice.
MO
Mollie
9 months ago
I'm not totally sure about the shared user account options. I'll need to double-check the security implications of those approaches.
SH
Shenika
10 months ago
This seems straightforward. I'd go with option C and set up a service account for the application server to access the Cloud SQL instance.
MA
Maybelle
10 months ago
Okay, I think I've got a strategy here. I'll focus on setting up the IAM securely, likely using a service account for the application server.
TA
Tandra
10 months ago
I remember we discussed the importance of using dedicated user accounts for different applications to enhance security.
SH
Sheridan
11 months ago
Haha, a common shared user account? What is this, the Stone Age?
JA
Jaclyn
11 months ago
Hmm, I'm a bit confused on the best way to handle the IAM for this Cloud SQL instance. I'll need to review the Google-recommended practices.
CA
Carmela
11 months ago
This looks like a tricky IAM setup question. I'll need to think through the different options carefully.
CL
Claudia
6 months ago
Yeah, I’d stick with the service account for better IAM practices.
YU
Yuonne
6 months ago
Shared accounts can lead to security issues. Better to avoid them.
LA
Lanie
10 months ago
I agree, a service account seems more secure for the application server.
RA
Ramonita
10 months ago
This is definitely tricky! I think a service account might be the best option.
OC
Octavio
11 months ago
But what about dedicated user accounts? They could work too, right?