Discuss Google Professional Cloud Developer Exam Topic 7 Question 117

You are porting an existing Apache/MySQL/PHP application stack from a single machine to Google Kubernetes Engine. You need to determine how to containerize the application. Your approach should follow Google-recommended best practices for availability. What should you do?

APackage each component in a separate container. Implement readiness and liveness probes.

BPackage the application in a single container. Use a process management tool to manage each component.

CPackage each component in a separate container. Use a script to orchestrate the launch of the components.

DPackage the application in a single container. Use a bash script as an entrypoint to the container, and then spawn each component as a background job.

Suggested Answer: A

https://cloud.google.com/blog/products/containers-kubernetes/7-best-practices-for-building-containers

https://cloud.google.com/architecture/best-practices-for-building-containers

'classic Apache/MySQL/PHP stack: you might be tempted to run all the components in a single container. However, the best practice is to use two or three different containers: one for Apache, one for MySQL, and potentially one for PHP if you are running PHP-FPM.'

Get Premium Professional Cloud Developer Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

26 comments · newest first

Dorothea 1 month ago

I feel like A is the way to go. Probes are crucial for availability.

Shawana 1 month ago

Option B seems easier, but it’s not best practice for Kubernetes.

Val 2 months ago

Agreed, A allows for better scaling and health checks.

Emiko 2 months ago

I think option A is the best. Separate containers are more manageable.

Avery 2 months ago

I prefer A too. It aligns with microservices architecture, which is more reliable.

Francesco 2 months ago

Option B seems easier, but it could lead to issues with component failures.

Mindy 2 months ago

Agreed! Readiness and liveness probes are crucial for availability.

Ty 2 months ago

I think option A is the best. Separate containers ensure better scalability.

Dewitt 3 months ago

I prefer A too. It aligns with Kubernetes best practices.

Valentine 3 months ago

Option B sounds easier, but it complicates management. Not recommended.

Mari 3 months ago

Agreed! Readiness and liveness probes are crucial for availability.

Weldon 3 months ago

I think option A is the best. Separate containers ensure better isolation.

Leatha 3 months ago

D) is a recipe for disaster, no way!

Rochell 4 months ago

C) sounds like a hassle, just stick with A).

Frederica 5 months ago

Surprised that people still suggest single containers!

Alesia 5 months ago

I disagree, B) seems simpler for small apps.

Bok 5 months ago

A) is the way to go for best practices!

Gerald 6 months ago

C) sounds interesting, but is it really reliable?

Maxima 6 months ago

Definitely A), separate containers are more manageable.

Kami 6 months ago

Surprised that D) is even an option, sounds risky!

Fernanda 6 months ago

I disagree, B) seems simpler for small apps.

Emile 6 months ago

A) is the way to go for best practices!

Sharika 6 months ago

I have a vague memory of a lesson where we talked about using a single container, but it seems like that could lead to issues with availability.

Gail 7 months ago

I feel like we practiced a question similar to this, and I think packaging each component separately was emphasized as a best practice.

Ashley 7 months ago

I'm not entirely sure, but I think using readiness and liveness probes is crucial for ensuring the application is healthy in Kubernetes.

Clorinda 7 months ago

I remember we discussed the importance of separating components into different containers for better scalability and management.

Google Professional Cloud Developer Exam - Topic 7 Question 117 Discussion