You are designing an Azure Web App that includes many static content files.
The application is accessed from locations all over the world by using a custom domain name.
You need to recommend an approach for providing access to the static content with the least amount of latency.
Which two actions should you recommend? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
Click on the arrows to vote for the correct answer
A. B. C. D.BD
D: Add Azure Content Delivery Network (CDN) to a web app in Azure App Service.
B: When you use a CDN endpoint to deliver content, a custom domain is necessary if you would like your own domain name to be visible in your CDN URL.
Having a visible domain name can be convenient for your customers and useful for branding purposes.
Create a CNAME DNS record, and associate the custom domain with your CDN endpoint.
https://docs.microsoft.com/en-us/azure/cdn/cdn-map-content-to-custom-domain https://docs.microsoft.com/en-us/azure/cdn/cdn-add-to-web-appTo provide access to the static content with the least amount of latency in an Azure Web App that includes many static content files, the following two actions should be recommended:
Configure a custom domain name that is an alias for the Azure Storage domain: To reduce the latency for serving static content, it is recommended to store the static content in Azure Storage. This storage account should be configured to use a custom domain name that is an alias for the Azure Storage domain. By doing this, the domain name will be resolved to the nearest Azure datacenter, reducing the latency for serving the content to end-users. This can be achieved by creating a CNAME record in the DNS zone file for the custom domain name, pointing it to the Azure Storage domain name.
Configure a CNAME DNS record for the Azure Content Delivery Network (CDN) domain: To further reduce the latency for serving static content, it is recommended to use Azure Content Delivery Network (CDN). CDN caches the static content at various edge locations around the world, closer to the end-users, reducing the round-trip time to fetch the content from the origin server. To configure CDN, a CNAME DNS record should be created for the Azure CDN domain name, pointing it to the custom domain name used for Azure Storage. Once the DNS record is propagated, the static content can be accessed using the CDN domain name, which will automatically route the requests to the nearest CDN edge location.
Option C and D are not recommended approaches for reducing latency for serving static content in this scenario, because placing the static content in Azure Table storage (Option C) or Azure Blob storage without enabling CDN (Option D) will not leverage the benefits of CDN and will not provide a fast and scalable solution for serving static content globally.