Discuss Google Professional Cloud DevOps Engineer Exam Topic 4 Question 97

[Building and implementing CI/CD pipelines for a service]

You work for a company that manages highly sensitive user dat

a. You are designing the Google Kubernetes Engine (GKE) infrastructure for your company, including several applications that will be deployed in development and production environments. Your design must protect data from unauthorized access from other applications while minimizing the amount of management overhead required. What should you do?

ACreate one cluster for the organization with separate namespaces for each application and environment combination.

BCreate one cluster for each environment (development and production) with each application in its own namespace within each cluster.

CCreate one cluster for the organization with separate namespaces for each application.

DCreate one cluster for each application with separate namespaces for production and development environments.

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

30 comments · newest first

Jacqueline 6 months ago

Option B gives more control. Better to be safe with sensitive data.

Novella 6 months ago

I worry about option A. What if one namespace gets compromised?

Cristina 7 months ago

I’m leaning towards option C. Fewer clusters mean less management.

Leontine 7 months ago

Option D sounds good too. Isolating apps is crucial for sensitive data.

Theodora 7 months ago

I prefer option B. Separate clusters for environments feel safer.

Clorinda 7 months ago

I think option A is the best. It keeps things organized.

Corrie 7 months ago

I think B is the best choice for clear separation.

Lashon 8 months ago

C is a good balance, but I worry about security.

Anabel 8 months ago

I’m surprised that D is even an option! Too many clusters!

Emogene 8 months ago

I disagree, A is more efficient with management.

Jennifer 8 months ago

Option B seems the safest for sensitive data.

Linn 9 months ago

Ah, the age-old question of cluster design. I say we just put everything in one cluster and see what happens. What could go wrong?

Irma 9 months ago

B) is the clear winner here. Gotta keep those dev and prod environments separate, you know? Security first!

Brett 9 months ago

D) sounds like a nightmare to manage. One cluster per app? No thanks, I'll pass on that headache.

Kizzy 9 months ago

I feel like option D might be overkill with too many clusters, but I do see the benefit of isolating applications completely.

Arthur 9 months ago

I think I practiced a question similar to this, and I recall that using separate namespaces can help with security, but I can't remember if one cluster is enough for everything.

Wei 9 months ago

Separating environments is important for security, but managing multiple clusters could get complicated. I'm going to carefully consider the pros and cons of each approach.

Holley 10 months ago

This is a good opportunity to demonstrate my understanding of Kubernetes best practices. I'm pretty confident option B is the way to go, but I'll review the other choices just to be sure.

Penney 10 months ago

I'm a bit confused by the wording here. Can we have multiple clusters in the same organization? I want to make sure I understand the constraints before deciding.

Malcolm 10 months ago

I'd go with C). Fewer clusters to manage, and namespaces can handle the isolation. Plus, who needs more than one cluster, am I right?

Owen 10 months ago

B) is the way to go. Separate clusters for dev and prod, with each app in its own namespace. Keeps things nice and tidy.

Dewitt 10 months ago

I remember discussing the importance of isolating environments, so option B seems like a good choice, but I'm not entirely sure if it's the most efficient.

Virgilio 11 months ago

I’m leaning towards option A since it minimizes management overhead, but I worry about the security implications of having everything in one cluster.

Leslie 11 months ago

Okay, let's see. I think the key is balancing security and maintainability. I'm leaning towards option B, but I'll need to double-check the details.

Vernice 11 months ago

Hmm, this seems like a tricky one. I'll need to think carefully about the trade-offs between data isolation, management overhead, and cluster complexity.

Eileen 6 months ago

↳ replying to Vernice

D seems like a good balance for isolation and management.

Alison 6 months ago

↳ replying to Vernice

A could lead to data access issues between apps, though.

Mariann 6 months ago

↳ replying to Vernice

What about option A? It could simplify things with fewer clusters.

Frank 6 months ago

↳ replying to Vernice

True, but it might increase management overhead.

Quentin 11 months ago

↳ replying to Vernice

I think option B makes sense. Separate clusters for each environment can enhance security.

Google Professional Cloud DevOps Engineer Exam - Topic 4 Question 97 Discussion