Discuss Google Associate Cloud Engineer Exam Topic 5 Question 89

Your company runs one batch process in an on-premises server that takes around 30 hours to complete. The task runs monthly, can be performed offline, and must be restarted if interrupted. You want to migrate this workload to the cloud while minimizing cost. What should you do?

AMigrate the workload to a Compute Engine Preemptible VM.

BMigrate the workload to a Google Kubernetes Engine cluster with Preemptible nodes.

CMigrate the workload to a Compute Engine VM. Start and stop the instance as needed.

DCreate an Instance Template with Preemptible VMs On. Create a Managed Instance Group from the template and adjust Target CPU Utilization. Migrate the workload.

Suggested Answer: D

HTTP(S) load balancing is a Google-recommended practice for distributing web traffic across multiple regions and zones, and providing high availability, scalability, and security for web applications. It supports both IPv4 and IPv6 addresses, and can handle SSL/TLS termination and encryption. It also integrates with Cloud CDN, Cloud Armor, and Cloud Identity-Aware Proxy for enhanced performance and protection. A MIG can be used as a backend service for HTTP(S) load balancing, and can automatically scale and heal the VM instances that host the web application.

To configure DNS for HTTP(S) load balancing, you need to create an A record in your DNS public zone with the load balancer's IP address. This will map your domain name to the load balancer's IP address, and allow users to access your web application using the domain name. A CNAME record is not recommended, as it can cause latency and DNS resolution issues. A private zone is not suitable, as it is only visible within your VPC network, and not to the public internet.

HTTP(S) Load Balancing documentation

Setting up DNS records for HTTP(S) load balancing

Choosing a load balancer

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

37 comments · newest first

Felix 11 months ago

Wow, didn't know preemptible VMs could save that much!

Jerry 11 months ago

Option C sounds safer, but might cost more.

Joanna 11 months ago

Not sure if preemptible is reliable for a 30-hour job.

Timothy 11 months ago

I think option A is the best choice.

Carlton 12 months ago

Preemptible VMs are cheaper!

Lisandra 12 months ago

I vaguely recall that Managed Instance Groups can help with scaling, but I’m not confident if that’s necessary for a monthly batch job.

Shasta 1 year ago

I practiced a similar question where we had to choose between Compute Engine and Kubernetes. I feel like Compute Engine might be simpler for this batch process.

Noah 1 year ago

I think option A sounds familiar, but I’m worried about the interruptions since it needs to restart if interrupted.

Frederica 1 year ago

I remember we discussed preemptible VMs in class, but I'm not sure if they are the best choice for a long-running task like this.

Gwenn 1 year ago

The question is pretty clear, but I'm not sure if starting and stopping the instance as needed is the best approach. I'll need to weigh the pros and cons of each option carefully.

Verdell 1 year ago

Okay, I think I've got a good strategy here. I'll focus on the options that mention Preemptible VMs since that seems like the most cost-effective approach for this type of workload.

Alline 1 year ago

Hmm, I'm a bit unsure about the differences between the Preemptible VM and Preemptible nodes in GKE. I'll need to review the details of each option to make the best decision.

Antonette 1 year ago

This seems like a straightforward question about migrating a batch process to the cloud. I'll need to carefully consider the cost-saving options presented.

Gaynell 1 year ago

Okay, I've got this. The key is that the question is asking about a procedure that uses a clot-dissolving agent. That points to thrombolytic therapy as the correct answer. B is the way to go.

Gregg 1 year ago

All these options sound pretty technical. I'm just hoping the correct answer doesn't involve any coding or complex setup. I'm more of a 'turn it on and let it run' kind of person.

Annamae 1 year ago

↳ replying to Gregg

I get what you mean. I prefer simple solutions too.

Carylon 1 year ago

↳ replying to Gregg

C) Migrate the workload to a Compute Engine VM. Start and stop the instance as needed.

Deeanna 1 year ago

↳ replying to Gregg

B) Migrate the workload to a Google Kubernetes Engine cluster with Preemptible nodes.

Harrison 1 year ago

↳ replying to Gregg

A) Migrate the workload to a Compute Engine Preemptible VM.

Eura 1 year ago

Hmm, Option A with the Preemptible VM seems like the easiest solution. As long as I don't mind the occasional disruption, it could be a good fit.

Serina 1 year ago

↳ replying to Eura

Using Preemptible VMs could definitely help reduce costs while migrating the workload to the cloud.

Tricia 1 year ago

↳ replying to Eura

I agree, the Preemptible VM option seems like a simple and efficient solution.

Leslie 1 year ago

↳ replying to Eura

Option A sounds like a good choice. It's cost-effective and can handle interruptions.

Kayleigh 1 year ago

Option B with the GKE cluster might be the way to go. The Preemptible nodes should keep the costs down, and the cluster will handle the workload management for me.

Jess 1 year ago

↳ replying to Kayleigh

It's worth considering the GKE cluster option for this migration. The Preemptible nodes could be a cost-effective solution.

Jade 1 year ago

↳ replying to Kayleigh

I agree, using a Kubernetes Engine cluster can definitely help with workload management and cost efficiency.

Rikki 1 year ago

↳ replying to Kayleigh

Option B with the GKE cluster sounds like a good choice. The Preemptible nodes should help with cost savings.

Karan 1 year ago

I'm leaning towards Option C. It's a straightforward approach, and I can just start and stop the instance as needed to save on costs.

Mira 1 year ago

↳ replying to Karan

I agree with Option D. Managing the workload with a Managed Instance Group and adjusting Target CPU Utilization seems like a smart move.

Veta 1 year ago

↳ replying to Karan

I think Option D might be better. Creating a Managed Instance Group with Preemptible VMs can provide more flexibility and cost savings.

Adelina 1 year ago

↳ replying to Karan

Option C sounds like a good choice. Starting and stopping the instance as needed can definitely help save on costs.

Yong 2 years ago

Option D looks good to me. Using Preemptible VMs and a Managed Instance Group should help minimize the cost while ensuring the workload can run reliably.

Kimbery 1 year ago

↳ replying to Yong

Yes, it's a good way to migrate the workload to the cloud while keeping costs low.

Earleen 1 year ago

↳ replying to Yong

I agree, using Preemptible VMs and a Managed Instance Group seems like a cost-effective solution.

Candida 2 years ago

I'm not sure about option D. Maybe we should consider option B as well, using Google Kubernetes Engine cluster with Preemptible nodes.

Pilar 2 years ago

I agree with Karma. Preemptible VMs can be a cost-effective solution for this kind of workload.

Karma 2 years ago

I think option D sounds like a good choice. Using Preemptible VMs can help save costs.

Google Associate Cloud Engineer Exam - Topic 5 Question 89 Discussion