70-473 · Question #67
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might h
The correct answer is B. No. Creating a Database Audit Specification in each database does not efficiently meet the requirement to audit all SELECT statements across all databases and doesn't configure the output to the application log.
Question
Options
- AYes
- BNo
How the community answered
(27 responses)- A7% (2)
- B93% (25)
Why each option
Creating a Database Audit Specification in each database does not efficiently meet the requirement to audit all SELECT statements across all databases and doesn't configure the output to the application log.
A Database Audit Specification is scoped to a single database and defines what events to audit within that specific database; it does not define the audit log destination, nor can a single specification configured this way efficiently cover all 17 databases for a unified audit requirement.
Concept tested: SQL Server Database Audit Specification scope and destination
Source: https://learn.microsoft.com/en-us/sql/relational-databases/security/auditing/sql-server-audit-database-level-action-groups-and-actions
Topics
Community Discussion
No community discussion yet for this question.