70-473 · Question #107
Your company has an application that uses several Microsoft Azure SQL databases. New databases are added regularly as customers sign up for new services. Databases are removed regularly as customers…
The correct answer is C. Set-AzureRmSqIServerAuditingPolicy. To ensure all Azure SQL databases, including new ones, are constantly audited, you must configure a server-level auditing policy.
Question
Options
- ASet-AzureRmSqIDatabaseAuditingPolicy
- BUse-AzureRmSqlServerAuditingPolicy
- CSet-AzureRmSqIServerAuditingPolicy
- DNew-AzureRmOperationallnsightsAzureAuditDataSource
How the community answered
(65 responses)- A5% (3)
- B3% (2)
- C85% (55)
- D8% (5)
Why each option
To ensure all Azure SQL databases, including new ones, are constantly audited, you must configure a server-level auditing policy.
Set-AzureRmSqlDatabaseAuditingPolicy configures auditing for a specific Azure SQL database, requiring manual configuration for each new database and failing to meet the requirement for automatically auditing all databases.
Use-AzureRmSqlServerAuditingPolicy is not a valid PowerShell cmdlet for managing Azure SQL Server auditing policies.
The Set-AzureRmSqlServerAuditingPolicy cmdlet configures the auditing policy for an entire Azure SQL logical server. When auditing is enabled at the server level, all existing and newly created databases on that server automatically inherit and apply the auditing policy, ensuring that auditing is constant and covers all databases, including those added regularly.
New-AzureRmOperationalInsightsAzureAuditDataSource is used to create a new Log Analytics data source for Azure SQL Audit data, configuring where audit logs are sent, not the auditing policy itself.
Concept tested: Azure SQL Database server-level auditing
Source: https://learn.microsoft.com/en-us/powershell/module/az.sql/set-azsqlserverauditingpolicy?view=azps-11.4.0
Topics
Community Discussion
No community discussion yet for this question.