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:

Yong
3 days 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
...
Candida
9 days 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
13 days ago
I agree with Karma. Preemptible VMs can be a cost-effective solution for this kind of workload.
upvoted 0 times
...
Karma
15 days ago
I think option D sounds like a good choice. Using Preemptible VMs can help save costs.
upvoted 0 times
...

Save Cancel