A role, a policy and a resource lock answer different questions. A role grants actions to a principal. Policy expresses resource compliance rules. A lock protects applicable management operations from changes or deletion. Treating them as interchangeable leaves gaps in a review.
Read the failure the team wants to prevent before choosing a control. A deletion lock doesn't make every blob undeletable, and a resource-group tag isn't guaranteed to appear on every member resource. The original scenarios ask you to select the control that addresses the stated requirement. They assess design interpretation; they don't enforce directory policy, licenses or production resource governance.
Choose the control that matches the requested protection.