Question-46:Compute Engine is being used by your business to handle the application demands. The apps have been installed in the production environment, as well as the acceptance environment, and the development environment. The production environment is the most important one for the company, as it is utilized around the clock. In contrast, the acceptance and development environments are only important during regular business hours. Your chief executive officer has requested that you tweak these settings in order to realise cost savings during periods of inactivity. An application that is being executed on Kubernetes is referred to as a workload. On Kubernetes, you will execute your workload inside of a group of pods, regardless of whether your workload consists of a single component or multiple that operate together. A group of containers that are currently executing on your cluster is referred to as a Pod in Kubernetes. Pods in Kubernetes follow a predetermined lifespan. What should you do?
A. Create a shell script that uses the gcloud command to change the machine type of the development and acceptance instances to a smaller machine type outside of office hours. Schedule the shell script on one of the production instances to automate the task.
B. Use Cloud Scheduler to trigger a Cloud Function that will stop the development and acceptance environments after office hours and start them just before office hours.
C. Deploy the development and acceptance applications on a managed instance group and enable autoscaling.
D. Use regular Compute Engine instances for the production environment, and use preemptible VMs for the acceptance and development environments.
Correct Answer
Get All 340 Questions and Answer for Google Professional Cloud Architect
: 2 Explanation: You only need to pay for the computing resources that you actually use when you use a platform like Google Compute Engine since you can schedule VMs to start and stop on their own. Virtual machines (VMs) in development, test, or personal settings are often only utilized during work hours. However, shutting these VMs off may save you a significant amount of money since production systems typically remain up around the clock. Cloud Scheduler, which is totally managed by Google Cloud Platform and acts as a cron task scheduler, offers a convenient solution for automatically stopping and resuming virtual machines (VMs). You are able to pause and restart groups of virtual machines (VMs) that are distinguished by labels of your choosing if you use Cloud Scheduler in conjunction with Cloud Pub/Sub to trigger Cloud Functions on a timed basis (created in Compute Engine). An example schedule is shown below that shuts down all virtual machines with the dev label at 5 p.m. and restarts them at 9 a.m., but it does not affect the VMs with the prod label in any way. The problem with Option 3 is that it could not deliver any cost savings at all if we make consistent use of the minimum viable scale during office hours. Option 2 is preferable, while Option 3 has potential for improvement. Option-2