New Year Sale 2026! 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 Associate Cloud Engineer Exam - Topic 5 Question 89 Discussion

Actual exam question for Google's Associate Cloud Engineer exam
Question #: 89
Topic #: 5
[All Associate Cloud Engineer Questions]

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?

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

by Noel at Aug 03, 2024, 11:47 AM

Limited Time Offer

25%

Off

Get Premium Associate Cloud Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Felix
3 months ago
Wow, didn't know preemptible VMs could save that much!
upvoted 0 times
...
Jerry
3 months ago
Option C sounds safer, but might cost more.
upvoted 0 times
...
Joanna
4 months ago
Not sure if preemptible is reliable for a 30-hour job.
upvoted 0 times
...
Timothy
4 months ago
I think option A is the best choice.
upvoted 0 times
...
Carlton
4 months ago
Preemptible VMs are cheaper!
upvoted 0 times
...
Lisandra
4 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.
upvoted 0 times
...
Shasta
5 months 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.
upvoted 0 times
...
Noah
5 months ago
I think option A sounds familiar, but I’m worried about the interruptions since it needs to restart if interrupted.
upvoted 0 times
...
Frederica
5 months 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.
upvoted 0 times
...
Gwenn
5 months 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.
upvoted 0 times
...
Verdell
5 months 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.
upvoted 0 times
...
Alline
5 months 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.
upvoted 0 times
...
Antonette
5 months 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.
upvoted 0 times
...
Gaynell
5 months 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.
upvoted 0 times
...
Gregg
10 months 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.
upvoted 0 times
Annamae
8 months ago
I get what you mean. I prefer simple solutions too.
upvoted 0 times
...
Carylon
8 months ago
C) Migrate the workload to a Compute Engine VM. Start and stop the instance as needed.
upvoted 0 times
...
Deeanna
9 months ago
B) Migrate the workload to a Google Kubernetes Engine cluster with Preemptible nodes.
upvoted 0 times
...
Harrison
9 months ago
A) Migrate the workload to a Compute Engine Preemptible VM.
upvoted 0 times
...
...
Eura
10 months 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.
upvoted 0 times
Serina
8 months ago
Using Preemptible VMs could definitely help reduce costs while migrating the workload to the cloud.
upvoted 0 times
...
Tricia
9 months ago
I agree, the Preemptible VM option seems like a simple and efficient solution.
upvoted 0 times
...
Leslie
9 months ago
Option A sounds like a good choice. It's cost-effective and can handle interruptions.
upvoted 0 times
...
...
Kayleigh
10 months 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.
upvoted 0 times
Jess
9 months ago
It's worth considering the GKE cluster option for this migration. The Preemptible nodes could be a cost-effective solution.
upvoted 0 times
...
Jade
9 months ago
I agree, using a Kubernetes Engine cluster can definitely help with workload management and cost efficiency.
upvoted 0 times
...
Rikki
9 months ago
Option B with the GKE cluster sounds like a good choice. The Preemptible nodes should help with cost savings.
upvoted 0 times
...
...
Karan
10 months 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.
upvoted 0 times
Mira
10 months ago
I agree with Option D. Managing the workload with a Managed Instance Group and adjusting Target CPU Utilization seems like a smart move.
upvoted 0 times
...
Veta
10 months ago
I think Option D might be better. Creating a Managed Instance Group with Preemptible VMs can provide more flexibility and cost savings.
upvoted 0 times
...
Adelina
10 months ago
Option C sounds like a good choice. Starting and stopping the instance as needed can definitely help save on costs.
upvoted 0 times
...
...
Yong
11 months 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.
upvoted 0 times
Kimbery
10 months ago
Yes, it's a good way to migrate the workload to the cloud while keeping costs low.
upvoted 0 times
...
Earleen
10 months ago
I agree, using Preemptible VMs and a Managed Instance Group seems like a cost-effective solution.
upvoted 0 times
...
...
Candida
11 months ago
I'm not sure about option D. Maybe we should consider option B as well, using Google Kubernetes Engine cluster with Preemptible nodes.
upvoted 0 times
...
Pilar
11 months ago
I agree with Karma. Preemptible VMs can be a cost-effective solution for this kind of workload.
upvoted 0 times
...
Karma
11 months ago
I think option D sounds like a good choice. Using Preemptible VMs can help save costs.
upvoted 0 times
...

Save Cancel