Module 5bb - Identity, Governance, Privacy and Compliance - Build a Cloud Governance Strategy, Resource Locks, Tags Flashcards
What is a Resource Lock?
It’s a mechanism used to prevent the accidental deletion or manipulation of a Resource
Where do you manage Resource Locks
You can manage locks from the usual places: Azure Portal, Powershell, Azure CLI (az.exe) or from an ARM Template
In Azure Portal, go to any details page for a resource and click on Settings
What are the three (3) levels can you apply Locks to?
Subscription, Resource Group or an individual Resource
What two (2) types of Locks can be applied?
CanNotDelete - authorized can read and modify but cannot delete without removing the lock first
ReadOnly - authorized can only read, no modify, no delete. Equivalent to restricting everyone to “Reader” Role in RBAC
What’s the process for changing or deleting a locked Resource
- Remove the lock
- Do whatever your account has permission to do
The extra step helps to keep your Resource secure even from Administrator actions
Resource Locks adhere to RBAC permissions, so if you are the designated Owner of a Resource, you can override any Lock on that Resource (T/F)?
False! Locks apply to everyone even if you are the Owner!
When locking a Resource Group, you prevent the Resource Group from being deleted, but not any of its contained Resources (T/F)?
False. Locking a Resource Group is transitive to all its internal Resources
What are Tags?
Tags allow you to easily add Metadata to your Resources.
What scenarios make Tags useful?
Organizing Resources by Tags make them much easier to manage and filter should you need to:
- Group Resources that may or may not be within the same Resource Group, to associate them to specific business needs, workflows, etc.
- Cost Reporting
- Group by SLA
- Group by security level classification (Azure Gov)
- Group by specific Governance or Regulatory Compliance requirements
How can you manage/apply/remove Resource Tags?
The usual! Azure Portal, Azure CLI, Azure PowerShell, ARM Templates or REST API
When applying a Tag to a Resource Group, it applies to ALL Resources within that Resource Group (similar to Locking) (T/F)?
False. Tags do NOT auto-apply to child Resources by default. This is opposite of Resource Group locking, where the lock applies to all child Resources…