This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Check your knowledge with these questions.
A Microsoft Defender for Storage alert fires indicating suspicious access from a Tor exit node to a blob container. Which Defender for Storage detection pillar generated this alert?
Malware scanning
Activity monitoring
Sensitive data threat detection
Hash reputation analysis
A security engineer needs to ensure Microsoft Defender for Storage is enabled for all storage accounts in a subscription, including accounts created in the future. What is the recommended deployment method?
Enable Defender for Storage on each storage account individually through the Azure portal
Enable Defender for Storage at the subscription level using a built-in Azure Policy assignment
Run a PowerShell script on a weekly schedule to detect and enable Defender on new storage accounts
Enable Defender for Storage at the resource group level to cover all accounts in the group
An organization configures Microsoft Defender for Storage malware scanning with a monthly cap of 5,000 GB per storage account. A high-traffic account reaches this cap mid-month. What is the expected behavior?
Malware scanning pauses for that account for the remainder of the month; new uploads proceed unscanned
Malware scanning continues but only performs hash reputation analysis instead of full file scanning
Microsoft Defender for Storage is automatically disabled for the affected storage account
The monthly cap automatically doubles to prevent scanning disruption
You must answer all questions before checking your work.
Was this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?