DP-300 Implement a secure environment Practice Question
Your Azure SQL Database contains sensitive financial data. You need to audit all data modifications (INSERT, UPDATE, DELETE) and store the audit logs in a central Azure Storage account for compliance. What should you configure?
⚠ Common exam trap
It's easy for candidates to confuse security monitoring tools (Defender for SQL, Vulnerability Assessment) or performance diagnostics (query store) with the specific auditing feature required for capturing data modification logs for compliance.
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
✓
Enable auditing on the database and set the audit log destination to an Azure Storage account.
Azure SQL Database's built-in auditing feature can be configured to capture all data modifications (INSERT, UPDATE, DELETE) and write audit logs directly to an Azure Storage account. This meets the compliance requirement for centralized, durable storage of audit records without additional services or complex pipelines.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Enable auditing on the database and set the audit log destination to an Azure Storage account.
Why this is correct
Azure SQL Database auditing captures INSERT, UPDATE and DELETE activity against the database, and configuring an Azure Storage account as the log destination centralises those records for compliance retention. This directly satisfies the requirement to audit all data modifications and store logs centrally.
- ✗
Configure diagnostic settings to stream query store data to an event hub.
Why it's wrong here
Query Store captures execution plans and runtime statistics, not row-level INSERT, UPDATE or DELETE events, and event hubs are not the required storage account. Diagnostic settings suit exporting metrics and logs for monitoring pipelines, but auditing data modifications requires SQL auditing writing to Azure Storage.
- ✗
Enable Microsoft Defender for SQL and configure security alerts to be sent to a storage account.
Why it's wrong here
Defender for SQL raises threat alerts on suspicious activity; alerts are detections, not a complete audit trail of every INSERT, UPDATE and DELETE, and cannot be routed to a storage account. It suits anomaly detection and attack investigation, whereas modification auditing requires SQL auditing writing to Azure Storage.
- ✗
Enable SQL Vulnerability Assessment and export the results to a storage account.
Why it's wrong here
Vulnerability Assessment scans for configuration weaknesses and missing patches, producing baseline scan reports rather than a record of data modifications. It is tempting because it also exports to a storage account, but compliance auditing of INSERT, UPDATE and DELETE statements needs SQL auditing configured to write to Azure Storage.
Go deeper
Related to this question
Learn chapter
Securing Data at Rest and in Transit
Key term
Azure SQL Performance Tuning
Azure SQL Performance Tuning is the process of optimizing the speed and efficiency of queries and database operations in Microsoft Azure SQL Database or SQL Managed Instance to reduce latency and improve throughput.
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 →
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.