How to audit all DB3 changes in Azure SQL Database?

DP-300 By islever Editorial Last updated Aug 23, 2026

Short answer

D Run the sys.sp_cdc_enable_db stored procedure.

Question

Case study - This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided. To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study. At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section. To start the case study - To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question. Overview - ADatum Corporation is a financial services company that has a main office in New York City. Existing Environment. Licensing Agreement ADatum has a Microsoft Volume Licensing agreement that includes Software Assurance. Existing Environment. Network Infrastructure ADatum has an on-premises datacenter and an Azure subscription named Sub1. Sub1 contains a virtual network named Network1 in the East US Azure region. The datacenter is connected to Network1 by using a Site-to-Site (S2S) VPN. Existing Environment. Identity Environment The on-premises network contains an Active Directory Domain Services (AD DS) forest. The forest contains a single domain named corp.adatum.com. The corp.adatum.com domain syncs with a Microsoft Entra tenant named adatum.com. Existing Environment. Database Environment The datacenter contains the servers shown in the following table. DB1 and DB2 are used for transactional and analytical workloads by an application named App1. App1 runs on Microsoft Entra hybrid joined servers that run Windows Server 2022. App1 uses Kerberos authentication. DB3 stores compliance data used by two applications named App2 and App3. DB3 performance is monitored by using Extended Events sessions, with the event_file target set to a file share on a local disk of SVR3. Resource allocation for DB3 is managed by using Resource Governor. Requirements. Planned Changes - ADatum plans to implement the following changes: • Deploy an Azure SQL managed instance named Instance1 to Network1. • Migrate DB1 and DB2 to Instance1. • Migrate DB3 to Azure SQL Database. • Following the migration of DB1 and DB2, hand over database development to remote developers who use Microsoft Entra joined Windows 11 devices. • Following the migration of DB3, configure the database to be part of an auto-failover group. Requirements. Availability Requirements ADatum identifies the following post-migration availability requirements: • For DB1 and DB2, offload analytical workloads to a read-only database replica in the same Azure region. • Ensure that if a regional disaster occurs, DB1 and DB2 can be recovered from backups. • After the migration, App1 must maintain access to DB1 and DB2. • For DB3, manage potential performance issues caused by resource demand changes by App2 and App3. • Ensure that DB3 will still be accessible following a planned failover. • Ensure that DB3 can be restored if the logical server is deleted. • Minimize downtime during the migration of DB1 and DB2. Requirements. Security Requirements ADatum identifies the following security requirements for after the migration: • Ensure that only designated developers who use Microsoft Entra joined Windows 11 devices can access DB1 and DB2 remotely. • Ensure that all changes to DB3, including ones within individual transactions, are audited and recorded. Requirements. Management Requirements ADatum identifies the following post-migration management requirements: • Continue using Extended Events to monitor DB3. • In Azure SQL Database, automate the management of DB3 by using elastic jobs that have database-scoped credentials. Requirements. Business Requirements ADatum identifies the following business requirements: • Minimize costs whenever possible, without affecting other requirements. • Minimize administrative effort. You need to recommend a solution to meet the security requirements and the business requirements for DB3. What should you recommend as the first step of the solution? - Exhibit: How to audit all DB3 changes in Azure SQL Database?

Exhibit: How to audit all DB3 changes in Azure SQL Database?

Run the sp_addarticle stored procedure.
Run the ALTER TABLE statement and specify the ENABLE CHANGE_TRACKING Clause.
Run the ALTER DATABASE statement and specify the SET CHANGE_TRACKING = ON Clause.
Run the sys.sp_cdc_enable_db stored procedure. Correct Answer

Key Takeaways

The exam tests the distinction between Change Tracking and Change Data Capture; CDC captures the actual data changes and transaction details, while Change Tracking only records that a row changed.

To meet the requirement that all changes to DB3—including those within individual transactions—must be audited and recorded, Change Data Capture (CDC) is the appropriate technology. Community consensus strongly favors enabling CDC via sys.sp_cdc_enable_db as the first step.

Common mistake: Many candidates choose C (SET CHANGE_TRACKING = ON) because Change Tracking is simpler, but it does not record the actual data modifications or transaction-level audit details required by the scenario.

Expert Analysis

Why the Answer Is Correct

The security requirement states that all changes to DB3, including ones within individual transactions, must be audited and recorded. Change Data Capture (CDC) captures the actual before-and-after data values and associates them with the transaction log, satisfying this granular audit need. The first step to implement CDC is to enable it at the database level by executing EXEC sys.sp_cdc_enable_db. As noted in comment [1], this must be done before any capture instances can be created on individual tables.

Why the Other Options Are Wrong

Option A (sp_addarticle) is used for transactional replication and is irrelevant to auditing data changes. Options B and C enable Change Tracking, which only records that a row was modified (and by which transaction) but does not capture the actual data values or provide a detailed audit trail. Comment [3] clearly explains that Change Tracking lacks the transaction-level detail required by the scenario, making CDC the only valid choice.

Community Comment Notes

The vote distribution (75 for D, 25 for C) shows that a significant minority confuses Change Tracking with CDC. Comment [4] incorrectly claims CDC is enabled by default in Azure SQL Database, but the official documentation confirms that CDC must be explicitly enabled at the database level before table-level capture instances are created. Comment [2] provides a useful link comparing CDC and Change Tracking, reinforcing why D is correct.

Exam Strategy

When a scenario requires auditing actual data changes and transaction details, always choose Change Data Capture (CDC) over Change Tracking. Remember that CDC must first be enabled at the database level with sys.sp_cdc_enable_db before individual tables can be configured.

Community Votes

75%

25%

75% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 6 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 6

JJJR 👍 3 Answered D

The answer is D. Before you can create a capture instance for individual tables, you must enable CDC for your Azure SQL Database. To enable CDC, connect to your Azure SQL Database through Azure Data Studio or SQL Server Management Studio (SSMS). Open a new query window, then enable CDC by running the following T-SQL: EXEC sys.sp_cdc_enable_db; GO https://learn.microsoft.com/en-us/azure/azure-sql/database/change-data-capture-overview?view=azuresql#enable-cdc-for-azure-sql-database
bingomutant 👍 1

Chat - D - sp_addarticle is used for replication, which is not relevant for this scenario. Change Tracking (options B and C) is focused on tracking which rows have changed, but it does not provide a detailed audit trail of all changes within individual transactions, unlike CDC. Therefore, enabling Change Data Capture with the sys.sp_cdc_enable_db stored procedure aligns with the requirement to audit and record changes.
Vitos25 👍 1 Answered C

Answer Correct C According to implementation, DB3 should move to Azure SQL Databases. Change Data Capture (CDC) is enabled by default in Azure SQL Database,Azure SQL Managed Instance. Hence, there is no need to enable it!
2f5c7cd 👍 1

CDC vs CT https://learn.microsoft.com/en-us/previous-versions/sql/sql-server-2008-r2/cc280519(v=sql.105)?redirectedfrom=MSDN
st1a 👍 1

You need cdc, not cdtjavascript:void(0). Correct answer is D.

Show 1 more comment

angelvenkovicch 👍 1

I think it's actually D

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Practice All DP-300 Questions

Access 105 questions with complete answers and detailed explanations.

View Full DP-300 Practice Test →

← Back to DP-300 Study Guide