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]

You are deploying a web application using Compute Engine. You created a managed instance group (MIG) to host the application. You want to follow Google-recommended practices to implement a secure and highly available solution. What should you do?

AUse SSL proxy load balancing for the MIG and an A record in your DNS private zone with the load balancer's IP address.

BUse SSL proxy load balancing for the MIG and a CNAME record in your DNS public zone with the load balancer's IP address.

CUse HTTP(S) load balancing for the MIG and a CNAME record in your DNS private zone with the load balancer's IP address.

DUse HTTP(S) load balancing for the MIG and an A record in your DNS public zone with the load balancer's IP address.

Show Suggested 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:

Submit Cancel

Dierdre

3 months ago

I believe we should use a CNAME record in our DNS public zone.

upvoted 0 times

...

Wei

3 months ago

I bet the person who wrote this question has never even heard of a CNAME record. *rolls eyes*

upvoted 0 times

Dalene

3 months ago

C) Use HTTP(S) load balancing for the MIG and a CNAME record in your DNS private zone with the load balancer's IP address.

upvoted 0 times

...

Salley

3 months ago

B) Use SSL proxy load balancing for the MIG and a CNAME record in your DNS public zone with the load balancer's IP address.

upvoted 0 times

...

Arthur

3 months ago

A) Use SSL proxy load balancing for the MIG and an A record in your DNS private zone with the load balancer's IP address.

upvoted 0 times

...

Rickie

4 months ago

But should we use an A record or a CNAME record in our DNS?

upvoted 0 times

...

Brandon

4 months ago

I agree with Dierdre, it's more secure that way.

upvoted 0 times

...

Vilma

4 months ago

I'm just happy I don't have to worry about load balancing my web app. That's what DevOps is for, right? *chuckles*

upvoted 0 times

Kristine

2 months ago

D) Use HTTP(S) load balancing for the MIG and an A record in your DNS public zone with the load balancer's IP address.

upvoted 0 times

...

Felton

2 months ago

C) Use HTTP(S) load balancing for the MIG and a CNAME record in your DNS private zone with the load balancer's IP address.

upvoted 0 times

...

Lucina

3 months ago

B) Use SSL proxy load balancing for the MIG and a CNAME record in your DNS public zone with the load balancer's IP address.

upvoted 0 times

...

Jeniffer

3 months ago

A) Use SSL proxy load balancing for the MIG and an A record in your DNS private zone with the load balancer's IP address.

upvoted 0 times

...

Francine

4 months ago

Hmm, I'm not sure about option A. Wouldn't an A record in the private DNS zone be a bit of a security risk?

upvoted 0 times

...

Dierdre

4 months ago

I think we should use SSL proxy load balancing for the MIG.

upvoted 0 times

...

Meaghan

4 months ago

Option C seems like a good choice too. HTTP(S) load balancing and a CNAME record in the private DNS zone could also work well for this scenario.

upvoted 0 times

Viva

3 months ago

I agree, using HTTP(S) load balancing and a CNAME record in the private DNS zone is a secure and highly available solution.

upvoted 0 times

...

Lavera

3 months ago

Option C seems like a good choice too. HTTP(S) load balancing and a CNAME record in the private DNS zone could also work well for this scenario.

upvoted 0 times

...

Christiane

4 months ago

I think option B is the way to go. Using SSL proxy load balancing and a CNAME record in the public DNS zone is the Google-recommended practice for a secure and highly available solution.

upvoted 0 times

Nettie

3 months ago

That's the Google-recommended practice for a reason. Option B all the way.

upvoted 0 times

...

Tina

4 months ago

I agree, SSL proxy load balancing and a CNAME record in the public DNS zone is the way to go.

upvoted 0 times

...

Sharen

4 months ago

Option B is definitely the best choice. It ensures security and high availability.

upvoted 0 times

...