ASSOCIATE-CLOUD-ENGINEER · Question #331
ASSOCIATE-CLOUD-ENGINEER Question #331: Real Exam Question with Answer & Explanation
The correct answer is D: Use HTTP(S) load balancing for the MIG and an A record in your DNS public zone with the load. To implement a secure and highly available web application using a Managed Instance Group (MIG), you should use HTTP(S) load balancing combined with an A record in a public DNS zone.
Question
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?
Options
- AUse SSL proxy load balancing for the MIG and an A record in your DNS private zone with the
- BUse SSL proxy load balancing for the MIG and a CNAME record in your DNS public zone with the
- CUse HTTP(S) load balancing for the MIG and a CNAME record in your DNS private zone with the
- DUse HTTP(S) load balancing for the MIG and an A record in your DNS public zone with the load
Explanation
To implement a secure and highly available web application using a Managed Instance Group (MIG), you should use HTTP(S) load balancing combined with an A record in a public DNS zone.
Common mistakes.
- A. SSL proxy load balancing is primarily for non-HTTP(S) SSL traffic, and a private DNS zone would prevent the web application from being publicly accessible.
- B. SSL proxy load balancing is not the primary choice for standard web applications, which benefit more from HTTP(S) Load Balancing's Layer 7 features.
- C. A private DNS zone would prevent external users from accessing the web application, as it only resolves names within a private network.
Concept tested. HTTP(S) Load Balancing and public DNS configuration
Reference. https://cloud.google.com/load-balancing/docs/choosing-load-balancer
Community Discussion
No community discussion yet for this question.