Courseiva

DP-300 Implement a secure environment Practice Question

You need to audit all schema changes in an Azure SQL Database and store the audit logs in a storage account for long-term retention. What should you enable?

⚠ Common exam trap

Many exam-takers confuse Azure SQL Auditing with other security features like Advanced Threat Protection or Vulnerability Assessment, assuming they all capture schema changes, but only Auditing provides granular event logging with a storage destination for long-term retention.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Azure SQL Auditing with storage account destination.

Azure SQL Auditing with a storage account destination is the correct choice because it tracks database events, including schema changes (DDL operations), and writes audit logs to Azure Blob Storage for long-term retention. This meets the requirement to audit all schema changes and store logs durably, as storage accounts provide configurable retention policies.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    Azure SQL Auditing with storage account destination.

    Why this is correct

    Azure SQL Auditing captures schema changes such as CREATE, ALTER and DROP through the database audit specification, and the storage account destination provides the long-term retention the scenario requires. This satisfies both the auditing and retention constraints.

  • ✗

    Advanced Threat Protection with email alerts.

    Why it's wrong here

    Advanced Threat Protection detects anomalous activity such as SQL injection and sends alerts; it does not record schema changes or write audit records to a storage account. It is the right choice for security alerting, not for audit log retention.

  • ✗

    Query Store with 'Data Flush Interval' set to 1 minute.

    Why it's wrong here

    Query Store captures query plans and runtime statistics, not schema-change events, so it cannot record DDL audit trails or write them to a storage account. It is tempting because Query Store does track schema modifications indirectly through plan regressions, making it useful for performance troubleshooting — but auditing requires SQL Server Audit writing to Blob Storage.

  • ✗

    SQL Vulnerability Assessment with recurring scans.

    Why it's wrong here

    Vulnerability Assessment scans for security misconfigurations and vulnerabilities, not schema-change events, so it cannot capture DDL audit records. It is tempting because it also stores results for later review, but it would be the right choice for meeting compliance benchmarks on database configuration, not for auditing schema modifications.

Quick reference

Azure Blob Storage Tier Comparison

TierStorage CostRetrieval CostLatencyUse Case
HotHighestLowestImmediateActive data, frequent reads
CoolLowerHigherImmediateData accessed < once / month
ColdLower stillHigherImmediateData accessed < once / quarter
ArchiveLowestHighest + rehydration delayHoursLong-term compliance retention

Go deeper

Related to this question

About these practice questions

One of 574 original DP-300 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This DP-300 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-300 exam.