A scoped request
A fictional publisher needs an application to read blobs in one storage account. Start with the application’s identity, the required data operation and the specific account. Reader grants management visibility; it isn’t the same as permission to read blob contents. Check the relevant data role and existing inherited assignments before describing the result as least privilege.
A managed identity supplies a workload identity without putting a stored credential in application code. It still needs authorization to the target resource. Enabling an identity alone doesn’t grant that application the requested access.
The saved assignment
Open the RBAC scope exercise, inspect its fictional resource and make the requested assignment. Compare the saved principal, role and target scope. An assignment with the right role at the wrong resource is still wrong.
Try changing the scope or choosing a management-plane role. Explain which requirement each alternative misses. The local checker inspects the resulting configuration; it doesn’t issue Entra tokens or enforce real authorization.
Workload practice
Use the Azure course to combine identity with network and storage settings. The Azure interview guide asks you to explain the same access boundary in a workplace scenario. Validate actual identity behavior and effective access in an authorized Azure environment before relying on the configuration.