DP-300 Implement a secure environment Practice Question
Your organization requires that all changes to sensitive data in an Azure SQL Database be logged for compliance. You need to capture who changed what data and when, and store the logs in a Log Analytics workspace for analysis. What should you configure?
⚠ Common exam trap
It's easy for candidates to confuse change tracking (which only detects row changes) with auditing (which captures who, what, and when), or they think security tools like Defender for Cloud provide granular data change logging.
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
✓
Configure server-level auditing to send logs to a Log Analytics workspace.
Server-level auditing in Azure SQL Database can be configured to send audit logs directly to a Log Analytics workspace, capturing detailed information about data changes including who made the change, what was changed, and when. This meets the compliance requirement for logging sensitive data changes and enables analysis using Log Analytics queries.
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 change tracking on the database.
Why it's wrong here
Change tracking records only that rows changed and their primary keys, not the old and new column values, the identity of the user, or a timestamp suitable for compliance auditing. It is tempting because it is a lightweight, low-overhead mechanism for synchronising data changes between applications and databases.
- ✗
Enable Microsoft Defender for Cloud on the server.
Why it's wrong here
Defender for Cloud surfaces security posture, alerts and threat detections; it does not record row-level before-and-after values of sensitive data or write that audit trail to Log Analytics. It is tempting because it is the default Azure security monitoring service and does forward alerts to a workspace.
- ✓
Configure server-level auditing to send logs to a Log Analytics workspace.
Why this is correct
Server-level auditing in Azure SQL Database captures the identity, statement and timestamp of every data modification and can stream audit records directly to a Log Analytics workspace, satisfying the requirement to record who changed what and when for compliance analysis.
- ✗
Enable Transparent Data Encryption (TDE) with customer-managed keys.
Why it's wrong here
TDE encrypts data at rest with customer-managed keys; it produces no record of who modified which rows, so no audit trail reaches Log Analytics. It is tempting because TDE with customer-managed keys satisfies encryption and key-control compliance requirements, which is a different control from auditing.
Go deeper
Related to this question
Learn chapter
Deploying and Configuring SQL Server on Azure Virtual Machines
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
This DP-300 question is part of Courseiva's 574-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.