Security needs durable records of failed logins and SELECT activity on the lock-chemistry table. Where should Azure SQL auditing send those events?
Select an answer to reveal the explanation.
Short Explanation
“We glanced at the portal” is not an audit trail. Point SQL auditing at Storage, Log Analytics, or Event Hubs so failed logins and table access land somewhere you can actually keep.
Full Explanation
Azure SQL Database and Managed Instance auditing supports destinations such as Azure Storage, Log Analytics, and Event Hubs for durable retention and analysis. Portal watching and informal spreadsheets are not auditing configurations. Microsoft Defender for SQL provides threat detection that can complement auditing but does not replace configuring an audit destination for who did what.