DRAG DROP Match the Azure governance feature to the correct description. Instructions: To answer, drag the appropriate feature from the column on the left to its description on the right. Each feature may be used once, more than once, or not at all. NOTE: Each correct match is worth one point.
Nice, this mapping lines up with how these features are used in Azure. Azure Policy is all about enforcing resource rules, tags help with organizing (especially for billing and reporting), and Blueprints let you package entire environments for deployment. Pretty sure that’s the intent here, matches what I’ve seen in other practice sets. Anyone see a case where locks would fit better here?
- Bucket 1: Azure Policy
- Bucket 2: Azure tags
- Bucket 3: Azure Blueprints
Pretty sure it's Policy to Bucket 1, Tags to Bucket 2, Blueprints to Bucket 3-this matches what I remember from similar questions and docs. Resource locks can look tempting if one area mentions deletion prevention but here it's not the focus. Anybody see it differently?
Policy for restrictions, tags for organizing, blueprints for deployment. Had something like this in a mock, same mapping fits. If the question was asking for the most secure feature instead, resource locks might be the pick.
