ASSOCIATE-CLOUD-ENGINEER Question #380: Real Exam Question with Answer & Explanation

Question

You are planning to migrate a database and a backend application to a Standard Google Kubernetes Engine (GKE) cluster. You need to prevent data loss and make sure there are enough nodes available for your backend application based on the demands of your workloads. You want to follow Google- recommended practices and minimize the amount of manual work required. What should you do?

Options

• ARun your database as a StatefulSet. Configure cluster autoscaling to handle changes in the
• BRun your database as a single Pod. Run the resize command when you notice changes in the
• CRun your database as a Deployment. Configure cluster autoscaling to handle changes in the
• DRun your database as a DaemonSet. Run the resize command when you notice changes in the

Explanation

StatefulSet for the Database: Databases are stateful applications that require persistent storage and stable network identities. A StatefulSet is designed specifically for stateful applications, as it provides unique, stable network identifiers and persistent storage via PersistentVolumeClaims (PVCs). This setup helps ensure that data is not lost during pod rescheduling or node failures. Cluster Autoscaling for the Backend Application: Configuring cluster autoscaling allows the GKE cluster to automatically add or remove nodes based on the demands of your workloads. This ensures that the backend application has sufficient compute resources available to handle fluctuating workloads, while minimizing the need for manual intervention.

No community discussion yet for this question.