You are deploying a single website on App Engine that needs to be accessible via the URL http://www.altostrat.com/
What should you do?
Click on the arrows to vote for the correct answer
A. B. C. D.A.
https://cloud.google.com/appengine/docs/flexible/dotnet/mapping-custom-domains?hl=faSure, I'd be happy to provide a detailed explanation of each answer option and the reasoning behind each one.
A. Verify domain ownership with Webmaster Central. Create a DNS CNAME record to point to the App Engine canonical name ghs.googlehosted.com. Option A suggests verifying domain ownership with Webmaster Central and creating a DNS CNAME record to point to the App Engine canonical name ghs.googlehosted.com. This approach is the correct way to configure a custom domain name for an App Engine application. When you create a custom domain for your App Engine app, you must verify that you own the domain by adding a TXT record to the domain's DNS configuration. Once you have verified domain ownership, you can create a CNAME record that points the custom domain to the App Engine canonical name ghs.googlehosted.com. This method enables you to serve your website from a custom domain name, in this case, http://www.altostrat.com.
B. Verify domain ownership with Webmaster Central. Define an A record pointing to the single global App Engine IP address. Option B suggests verifying domain ownership with Webmaster Central and defining an A record pointing to the single global App Engine IP address. However, App Engine does not provide a single global IP address that you can use to point your custom domain to your App Engine app. Additionally, when you define an A record, it maps the domain name to a specific IP address. This approach does not allow for scaling, and it may not be the best choice if you want to serve your website from a custom domain name.
C. Define a mapping in dispatch.yaml to point the domain www.altostrat.com to your App Engine service. Create a DNS CNAME record to point to the App Engine canonical name ghs.googlehosted.com. Option C suggests defining a mapping in dispatch.yaml to point the domain www.altostrat.com to your App Engine service and creating a DNS CNAME record to point to the App Engine canonical name ghs.googlehosted.com. While defining a mapping in dispatch.yaml can be useful for routing requests to different services within your App Engine app, it is not necessary for serving your website from a custom domain. Moreover, this approach does not allow for scaling, as it maps the domain name to a specific service within your App Engine app.
D. Define a mapping in dispatch.yaml to point the domain www.altostrat.com to your App Engine service. Define an A record pointing to the single global App Engine IP address. Option D suggests defining a mapping in dispatch.yaml to point the domain www.altostrat.com to your App Engine service and defining an A record pointing to the single global App Engine IP address. As previously mentioned, App Engine does not provide a single global IP address that you can use to point your custom domain to your App Engine app. Additionally, while defining a mapping in dispatch.yaml can be useful for routing requests to different services within your App Engine app, it is not necessary for serving your website from a custom domain.
In conclusion, the correct answer is A: Verify domain ownership with Webmaster Central. Create a DNS CNAME record to point to the App Engine canonical name ghs.googlehosted.com. This approach allows you to serve your website from a custom domain name and enables scaling as App Engine handles load balancing automatically.