DP-300 · Question #436
Hotspot Question You have an Azure subscription. The subscription contains an Azure Storage account named storage1, a container named Container1, and an Azure SQL managed instance that hosts a…
Azure SQL MI Backup to Blob Storage - Hotspot Explanation The complete T-SQL statement being constructed: ``sql BACKUP DATABASE DB1 TO URL = '<option1>' WITH <option2> ` --- Dropdown 1: TO URL = Correct: 'https://storage1.blob.core.windows.net/container1 Why correct: Azure Blob…
Question
Exhibit
Answer Area
- TO URL ='abfs://container1.storage1.blob.core.windows.net'https://storage1.blob.core.windows.net/container1'https://storage1.container1 .blob.core.windows.net
- WITHWITH COMPRESSIONWITH COPY_ONLYWITH DIFFERENTIAL
Explanation
Azure SQL MI Backup to Blob Storage - Hotspot Explanation
The complete T-SQL statement being constructed:
BACKUP DATABASE DB1
TO URL = '<option1>'
WITH <option2>
Dropdown 1: TO URL =
Correct: 'https://storage1.blob.core.windows.net/container1
Why correct: Azure Blob Storage URLs follow this exact pattern:
https://<storage_account>.blob.core.windows.net/<container>
storage1 is the account name, container1 is the container - the container is a path segment, not a subdomain.
Why the others are wrong:
| Option | Why Wrong |
|---|---|
abfs://container1.storage1.blob.core.windows.net | abfs:// is the Azure Data Lake Storage Gen2 (ADLS Gen2) URI scheme, used for ABFS driver access - not valid for BACKUP TO URL |
https://storage1.container1.blob.core.windows.net | Puts the container as a subdomain, which is not how Azure Blob Storage URLs are structured |
Dropdown 2: WITH
Correct: WITH COPY_ONLY
Why correct: Azure SQL Managed Instance already runs automated backups (full, differential, log) managed by Azure. A manual backup using COPY_ONLY is taken outside the normal backup sequence - it doesn't reset the differential base or break the log chain. This is a hard requirement for manual backups on MI.
Why the others are wrong:
| Option | Why Wrong |
|---|---|
WITH COMPRESSION | Valid in SQL Server generally, but doesn't address the critical requirement of protecting the automated backup chain on MI |
WITH DIFFERENTIAL | A differential backup only captures changes since the last full backup - it's not appropriate for a standalone ad-hoc backup and would interact with the automated backup chain |
Core concept: Azure SQL Managed Instance owns its backup chain. COPY_ONLY is the sanctioned way to take a manual backup without corrupting that chain.
Topics
Community Discussion
No community discussion yet for this question.
