Google Professional Cloud Architect Exam - Topic 1 Question 89 Discussion

Actual exam question for Google's Professional Cloud Architect exam

Question #: 89
Topic #: 1

[All Professional Cloud Architect Questions]

You have deployed an application to Kubernetes Engine, and are using the Cloud SQL proxy container to

make the Cloud SQL database available to the services running on Kubernetes. You are notified that the

application is reporting database connection issues. Your company policies require a post-mortem. What should you do?

AUse gcloud sql instances restart.

BValidate that the Service Account used by the Cloud SQL proxy container still has the Cloud Build Editor role.

CIn the GCP Console, navigate to Stackdriver Logging. Consult logs for Kubernetes Engine and Cloud SQL.

DIn the GCP Console, navigate to Cloud SQL. Restore the latest backup. Use kubect1 to restart all pods.

Show Suggested Answer

Suggested Answer: C

This option can help create an organization structure that allows developers to create projects, but prevents them from modifying production projects. Folders are containers for projects and other folders within Google Cloud organizations. Folders allow resources to be structured hierarchically and inherit policies from their parent resources. By creating folders under the organization resource named ''Development'' and ''Production'', you can organize your projects by environment and apply different policies to them. By granting all developers the Project Creator IAM role on the ''Development'' folder, you can allow them to create projects under that folder, but not under the ''Production'' folder. By moving the developer projects into the ''Development'' folder, you can ensure that they are subject to the policies set on that folder. By setting the policies for all projects on the organization, you can manage policies centrally and efficiently. By additionally setting the production policies on the ''Production'' folder, you can enforce more restrictive policies for production projects and prevent developers from modifying them. The other options are not optimal for this scenario, because they either create a second Google Workspace account and organization, which increases complexity and cost (A), or do not use folders to organize projects by environment, which makes it harder to manage policies and permissions (B, D). Reference:

https://cloud.google.com/resource-manager/docs/creating-managing-folders

https://cloud.google.com/architecture/framework/system-design

by Viki at Aug 03, 2024, 10:35 AM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Architect Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Ammie

3 months ago

Restoring from backup? That sounds extreme for connection issues!

upvoted 0 times

...

Karl

3 months ago

Validating the Service Account is a good step too.

upvoted 0 times

...

Theodora

4 months ago

Wait, why would you restart the SQL instance first? Seems risky.

upvoted 0 times

...

Amber

4 months ago

Definitely agree with that! Logs tell you everything.

upvoted 0 times

...

Joaquin

4 months ago

I think checking the logs is crucial.

upvoted 0 times

...

Loise

4 months ago

I feel like restoring a backup, as mentioned in option D, should be a last resort. We should investigate the logs first before taking such action.

upvoted 0 times

...

Sabrina

5 months ago

I’m a bit confused about whether restarting the SQL instance is necessary. Option A seems too drastic without more information.

upvoted 0 times

...

Tamra

5 months ago

I think option C makes sense because checking the logs could give us insights into what went wrong. We practiced a similar question about troubleshooting with logs.

upvoted 0 times

...

Blair

5 months ago

I remember we discussed the importance of checking service account permissions in class, so option B seems relevant, but I'm not entirely sure if that's the first step.

upvoted 0 times

...

Detra

5 months ago

This seems straightforward enough. I'd start by restarting the Cloud SQL instance and see if that resolves the issue. If not, then I'd dig into the logs and check the service account permissions.

upvoted 0 times

...

Fletcher

5 months ago

Okay, I think I've got a plan. First, I'll validate the service account permissions, then I'll check the logs in Stackdriver. If that doesn't give me any insights, I'll try restarting the Cloud SQL instance as a last resort.

upvoted 0 times

...

Lura

5 months ago

Hmm, I'm a bit unsure about this one. I know we need to do a post-mortem, but I'm not sure if restoring the database backup is the right first step. Maybe I should double-check the service account permissions first.

upvoted 0 times

...

Martina

5 months ago

This seems like a pretty straightforward troubleshooting scenario. I'd start by checking the logs in Stackdriver to see if there are any clues about the connection issues.

upvoted 0 times

...

Jolene

5 months ago

Hmm, I'm a bit unsure about this one. I know quality management is different from traditional management, but I'm not totally clear on the specific differences. I'll have to think it through carefully.

upvoted 0 times

...

Gail

10 months ago

Ooh, Stackdriver Logging, my favorite place to find cryptic error messages and confusing log entries. Gotta love cloud troubleshooting!

upvoted 0 times

Gracia

8 months ago

After that, we can use kubect1 to restart all pods if needed.

upvoted 0 times

...

Bambi

8 months ago

Let's also validate that the Service Account used by the Cloud SQL proxy container still has the Cloud Build Editor role.

upvoted 0 times

...

Rossana

8 months ago

I think we should consult the logs for Kubernetes Engine and Cloud SQL to find the issue.

upvoted 0 times

...

Floyd

9 months ago

I know, Stackdriver Logging can be a real puzzle sometimes.

upvoted 0 times

...

Blossom

10 months ago

Haha, I bet someone forgot to renew their Cloud Build Editor role. Classic cloud infrastructure gotcha!

upvoted 0 times

Tawanna

9 months ago

D) In the GCP Console, navigate to Cloud SQL. Restore the latest backup. Use kubect1 to restart all pods.

upvoted 0 times

...

Alaine

9 months ago

C) In the GCP Console, navigate to Stackdriver Logging. Consult logs for Kubernetes Engine and Cloud SQL.

upvoted 0 times

...

Art

9 months ago

C) In the GCP Console, navigate to Stackdriver Logging. Consult logs for Kubernetes Engine and Cloud SQL.

upvoted 0 times

...

Aide

9 months ago

B) Validate that the Service Account used by the Cloud SQL proxy container still has the Cloud Build Editor role.

upvoted 0 times

...

Lai

10 months ago

B) Validate that the Service Account used by the Cloud SQL proxy container still has the Cloud Build Editor role.

upvoted 0 times

...

Isaac

10 months ago

A) Use gcloud sql instances restart.

upvoted 0 times

...

Aliza

10 months ago

I agree, C is the best choice here. Jumping straight to restarting the SQL instance or restoring a backup without investigating the root cause first doesn't seem like the right approach.

upvoted 0 times

...

Ryan

11 months ago

Option C looks like the right way to go. Checking the logs for any errors or issues with the Cloud SQL proxy container would be the first step to diagnose the problem.

upvoted 0 times