Which statement best describes the purpose of an Azure CDN profile?
Think about how Azure organizes CDN resources for billing and management.
An Azure CDN profile acts as a container for multiple CDN endpoints, allowing centralized management and billing. It does not store content or define node locations directly.
You want to deliver static website content globally using Azure CDN. Which component must you create to specify the origin server for your content?
Consider which part connects the CDN to your source content.
The Azure CDN endpoint defines the origin server URL from which the CDN pulls content to cache and deliver to users.
Your website experiences sudden spikes in traffic worldwide. Which Azure CDN feature helps ensure low latency and high availability during these spikes?
Think about how to distribute traffic load efficiently.
Using multiple CDN endpoints within a profile allows traffic to be distributed across endpoints, improving load handling and availability during spikes.
Azure CDN supports multiple providers like Verizon and Microsoft. What is a key tradeoff when selecting a CDN provider for your Azure CDN profile?
Consider differences in cost, features, and coverage.
Each CDN provider has unique pricing, features, and geographic reach, so selecting one involves balancing these factors based on your needs.
You expect 10 million requests per day globally with an average response size of 500 KB. Approximately how much data transfer (in TB) will your Azure CDN endpoint handle daily?
Calculate total bytes transferred: requests × size, then convert to TB (1 TB = 10^12 bytes).
10 million requests × 500 KB = 5,000,000,000 KB = 5,000,000,000,000 bytes = 5 TB.