Microsoft
DP-300 · Question #335
Case Study 5 - ADatum Corporation 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…
The correct answer is D. Run the sys.sp_cdc_enable_db stored procedure. Explanation Running sys.sp_cdc_enable_db is the correct first step because the security requirement states that all changes to DB3, including ones within individual transactions, must be audited and recorded - this describes Change Data Capture (CDC), which captures INSERT…
Submitted by rohit_dlh· Mar 6, 2026Implement a secure environment
Question
Case Study 5 - ADatum Corporation 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. 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. 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. 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. 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. 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. 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. 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?
Options
- ARun the sp_addarticle stored procedure.
- BRun the ALTER TABLE statement and specify the ENABLE CHANGE_TRACKING Clause.
- CRun the ALTER DATABASE statement and specify the SET CHANGE_TRACKING = ON Clause.
- DRun the sys.sp_cdc_enable_db stored procedure.
How the community answered
(17 responses)- A6% (1)
- B18% (3)
- C6% (1)
- D71% (12)
Explanation
Explanation
Running sys.sp_cdc_enable_db is the correct first step because the security requirement states that all changes to DB3, including ones within individual transactions, must be audited and recorded - this describes Change Data Capture (CDC), which captures INSERT, UPDATE, and DELETE operations at the transaction level, storing a complete audit trail in change tables. CDC must be enabled at the database level first before it can be enabled on individual tables, making this the mandatory first step.
Why the distractors are wrong:
- Option A (sp_addarticle) is used to add articles to a SQL Server replication publication - this is a replication concept, not an auditing solution, and is irrelevant here.
- Option B (ALTER TABLE...ENABLE CHANGE_TRACKING) enables Change Tracking at the table level, but Change Tracking only records that a row changed (not what changed within a transaction), so it doesn't meet the requirement to capture individual transaction details.
- Option C (ALTER DATABASE...SET CHANGE_TRACKING = ON) enables Change Tracking at the database level - same limitation as Option B, it lacks the granular, transaction-level detail required, and it's also a prerequisite step for Change Tracking, not CDC.
Memory Tip: Think "CDC = Complete Data Changes" - when you need a full audit trail including what changed inside transactions, always choose CDC, and remember: database first, then tables (sp_cdc_enable_db → sp_cdc_enable_table).
Topics
#Change Data Capture (CDC)#Auditing#Data Security#Compliance
Community Discussion
No community discussion yet for this question.