A media company ingests daily video files into Azure Blob Storage. Videos are read heavily for 7 days, occasionally for the next 3 months, and then must be retained for 5 years at the lowest cost. Only the ‘critical’ container needs to be replicated to a secondary region. The secondary copy will have a longer retention policy than the primary. What should you design?

The correct answer addresses all requirements: Blob object replication allows granular replication of only the 'critical' container to a secondary region, as specified. Lifecycle rules in both the primary and secondary accounts enable cost-effective tiering from Hot (initial heavy access) to Cool (occasional access) to Cold and then Archive (long-term, lowest cost retention) over the required 5 years, with the flexibility to set different retention policies per region. Incorrect options: GZRS replicates the entire storage account, not just a specific container, and a single lifecycle policy wouldn't allow for different retention in the secondary region. Storing directly in Archive and rehydrating is too expensive for the initial heavy access period. RA-GRS replicates the entire account. Azure Data Factory for nightly copies is less efficient and more complex than native object replication, and setting both accounts to Cool permanently doesn't meet the multi-tier cost optimization or 5-year archive requirement. Azure Files is not designed for large-scale video ingestion and archival, and DFS-N is for file share access, not blob storage.