Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Associate Cloud Engineer 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

Contribute your Thoughts:

Gregg
2 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
Deeanna
16 days ago
B) Migrate the workload to a Google Kubernetes Engine cluster with Preemptible nodes.
upvoted 0 times
...
Harrison
25 days ago
A) Migrate the workload to a Compute Engine Preemptible VM.
upvoted 0 times
...
...
Eura
2 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
4 days ago
Using Preemptible VMs could definitely help reduce costs while migrating the workload to the cloud.
upvoted 0 times
...
Tricia
9 days ago
I agree, the Preemptible VM option seems like a simple and efficient solution.
upvoted 0 times
...
Leslie
12 days ago
Option A sounds like a good choice. It's cost-effective and can handle interruptions.
upvoted 0 times
...
...
Kayleigh
2 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
20 days 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
28 days ago
I agree, using a Kubernetes Engine cluster can definitely help with workload management and cost efficiency.
upvoted 0 times
...
Rikki
1 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
2 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
2 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
2 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
2 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
3 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
2 months ago
Yes, it's a good way to migrate the workload to the cloud while keeping costs low.
upvoted 0 times
...
Earleen
2 months ago
I agree, using Preemptible VMs and a Managed Instance Group seems like a cost-effective solution.
upvoted 0 times
...
...
Candida
3 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
3 months ago
I agree with Karma. Preemptible VMs can be a cost-effective solution for this kind of workload.
upvoted 0 times
...
Karma
3 months ago
I think option D sounds like a good choice. Using Preemptible VMs can help save costs.
upvoted 0 times
...

Save Cancel