Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Professional Cloud Developer Exam - Topic 7 Question 117 Discussion

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?
A) Package each component in a separate container. Implement readiness and liveness probes.
B) Package the application in a single container. Use a process management tool to manage each component.
C) Package each component in a separate container. Use a script to orchestrate the launch of the components.
D) Package 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.

Google Professional Cloud Developer Exam - Topic 7 Question 117 Discussion

Actual exam question for Google's Professional Cloud Developer exam
Question #: 117
Topic #: 7
[All Professional Cloud Developer Questions]

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?

Show Suggested Answer Hide Answer
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.'


by Filiberto at Mar 04, 2026, 08:47 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Dewitt
25 minutes ago
I prefer A too. It aligns with Kubernetes best practices.
upvoted 0 times
...
Valentine
5 days ago
Option B sounds easier, but it complicates management. Not recommended.
upvoted 0 times
...
Mari
10 days ago
Agreed! Readiness and liveness probes are crucial for availability.
upvoted 0 times
...
Weldon
16 days ago
I think option A is the best. Separate containers ensure better isolation.
upvoted 0 times
...
Leatha
21 days ago
D) is a recipe for disaster, no way!
upvoted 0 times
...
Rochell
26 days ago
C) sounds like a hassle, just stick with A).
upvoted 0 times
...
Frederica
2 months ago
Surprised that people still suggest single containers!
upvoted 0 times
...
Alesia
3 months ago
I disagree, B) seems simpler for small apps.
upvoted 0 times
...
Bok
3 months ago
A) is the way to go for best practices!
upvoted 0 times
...
Gerald
3 months ago
C) sounds interesting, but is it really reliable?
upvoted 0 times
...
Maxima
3 months ago
Definitely A), separate containers are more manageable.
upvoted 0 times
...
Kami
3 months ago
Surprised that D) is even an option, sounds risky!
upvoted 0 times
...
Fernanda
3 months ago
I disagree, B) seems simpler for small apps.
upvoted 0 times
...
Emile
4 months ago
A) is the way to go for best practices!
upvoted 0 times
...
Sharika
4 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.
upvoted 0 times
...
Gail
4 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.
upvoted 0 times
...
Ashley
4 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.
upvoted 0 times
...
Clorinda
4 months ago
I remember we discussed the importance of separating components into different containers for better scalability and management.
upvoted 0 times
...

Save Cancel