Exam Professional Cloud Developer topic 1 question 85 discussion

A. Package each component in a separate container. Implement readiness and liveness probes. This is the recommended approach for containerizing an application for use on Kubernetes. By packaging each component in a separate container, you can ensure that each component is isolated and can be managed independently. You can then use readiness and liveness probes to monitor the health and availability of each component, which will help ensure the overall availability of the application.

A is best suited here.

A is the answer. https://cloud.google.com/architecture/best-practices-for-building-containers#package_a_single_app_per_container When you start working with containers, it's a common mistake to treat them as virtual machines that can run many different things simultaneously. A container can work this way, but doing so reduces most of the advantages of the container model. For example, take a 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.

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. Because a container is designed to have the same lifecycle as the app it hosts, each of your containers should contain only one app. When a container starts, so should the app, and when the app stops, so should the container. The following diagram shows this best practice. https://cloud.google.com/architecture/best-practices-for-building-containers#package_a_single_app_per_container Answer A

A is correct

According to me "A" is the correct answer, because the best practice says "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."