Question 560
A Microsoft Azure administrator receives this requirement: A data lake account permits access from all public networks despite a requirement to accept only applications in approved VNets. What technical cause best accounts for the described behavior?
Explanation
Correct Answer
The described technical condition is: The storage account network firewall rules allow broad public endpoints instead of restricting to designated networks. The appropriate corrective action is: Limit storage network access to appropriate VNets or Private Endpoints and configure DNS as required. Confirm with: Approved clients access data and unauthorized public source IPs receive network access denial.
Incorrect Answers
Blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning. “Enable supported blob versioning and define backup or lifecycle protection for critical objects” would address that alternative cause, not the condition in this question: the storage account network firewall rules allow broad public endpoints instead of restricting to designated networks.
“Generate a short-lived SAS with minimum upload permissions and appropriate IP or protocol restrictions” responds to this separate finding: the SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose. This question instead needs “Limit storage network access to appropriate VNets or Private Endpoints and configure DNS as required”, so the alternative does not meet the stated condition.
Data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone. “Configure the appropriate time-based immutability policy or legal hold for the protected container” applies to that separate problem. The observed case is a data lake account permits access from all public networks despite a requirement to accept only applications in approved VNets; choosing this alternative would address the wrong failure mode.