B. Azure Blueprints
Azure Blueprints can replace a resource lock automatically if the lock is removed. A resource lock is a setting that you apply to a resource to prevent accidental deletion or modification of the resource. When a lock is applied to a resource, it blocks any operations that would modify or delete the resource.
If a resource lock is removed, it can leave the resource vulnerable to accidental deletion or modification. However, if the resource is associated with an Azure Blueprint, the Blueprint can automatically replace the lock to help protect the resource. This is because Azure Blueprints enforce compliance with policies and standards across multiple subscriptions, environments, and regions.
B is the answer.
https://learn.microsoft.com/en-us/azure/governance/blueprints/concepts/resource-locking#overriding-locking-states
It's typically possible for someone with appropriate Azure role-based access control (Azure RBAC) on the subscription, such as the 'Owner' role, to be allowed to alter or delete any resource. This access isn't the case when Azure Blueprints applies locking as part of a deployed assignment. If the assignment was set with the Read Only or Do Not Delete option, not even the subscription owner can perform the blocked action on the protected resource.
This security measure protects the consistency of the defined blueprint and the environment it was designed to create from accidental or programmatic deletion or alteration.
Azure Blueprints is a service that allows you to define a set of Azure resources that implement and adhere to an organization's standards, patterns, and requirements. You can use Azure Blueprints to create a repeatable, predictable, and auditable way to build and manage Azure environments.
One of the features of Azure Blueprints is the ability to apply resource locks to prevent unauthorized changes to your resources. A resource lock is a way to prevent accidental or unauthorized deletion, modification, or movement of a resource.
If a resource lock is removed, Azure Blueprints can automatically replace the lock to ensure that your resources remain protected. This helps to prevent accidental or unauthorized changes to your resources, and ensures that your environments remain compliant with your organizational standards and requirements.
B is the answer.
https://learn.microsoft.com/en-us/azure/governance/blueprints/concepts/resource-locking#overriding-locking-states
It's typically possible for someone with appropriate Azure role-based access control (Azure RBAC) on the subscription, such as the 'Owner' role, to be allowed to alter or delete any resource. This access isn't the case when Azure Blueprints applies locking as part of a deployed assignment. If the assignment was set with the Read Only or Do Not Delete option, not even the subscription owner can perform the blocked action on the protected resource.
This security measure protects the consistency of the defined blueprint and the environment it was designed to create from accidental or programmatic deletion or alteration.
Absolutely B
Locking Mode applies to the blueprint assignment and it has three options: Don't Lock, Read Only, or Do Not Delete. The locking mode is configured during artifact deployment during a blueprint assignment.
https://learn.microsoft.com/en-us/azure/governance/blueprints/concepts/resource-locking
I go with B Azure blueprints
https://learn.microsoft.com/en-us/azure/governance/blueprints/concepts/resource-locking
upvoted 1 times
...
This section is not available anymore. Please use the main Exam Page.AZ-900 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
BeauChateau
Highly Voted 2 years, 1 month agojambroba
Most Recent 9 months, 1 week agob274b54
10 months, 3 weeks agoZainZakria
1 year, 5 months agogilldilraj
2 years, 1 month agozellck
2 years, 3 months agozellck
2 years, 3 months agozellck
2 years, 3 months agoScotrideff1
2 years, 3 months agolombri
2 years, 4 months agoRobertON1969
2 years, 4 months ago