hardMultiple ChoiceObjective-mapped

SC-100 Practice Question: Refer to the exhibit

Exhibit

Refer to the exhibit.

```json
{
  "properties": {
    "policyRule": {
      "if": {
        "allOf": [
          {
            "field": "type",
            "equals": "Microsoft.Compute/virtualMachines"
          },
          {
            "field": "Microsoft.Compute/virtualMachines/storageProfile.osDisk.managedDisk",
            "exists": "true"
          },
          {
            "anyOf": [
              {
                "field": "Microsoft.Compute/virtualMachines/storageProfile.osDisk.managedDisk.storageAccountType",
                "notEquals": "Premium_LRS"
              },
              {
                "field": "Microsoft.Compute/virtualMachines/storageProfile.osDisk.diskSizeGB",
                "greater": 1023
              }
            ]
          }
        ]
      },
      "then": {
        "effect": "audit"
      }
    }
  }
}
```

Refer to the exhibit. An Azure policy is defined as shown. Which resources will be audited?

⚠ Common exam trap

Microsoft often tests the nuance of 'auditIfNotExists' vs. 'audit' effects, where candidates mistakenly think the policy audits all non-compliant resources or unmanaged disks, but the policy actually audits only when the specified condition (Standard_LRS disk exists) is true, not when it is false.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Virtual machines with Standard_LRS managed disks

The Azure policy definition in the exhibit uses the 'audit' effect to evaluate a condition that checks whether the virtual machine's managed disk storage account type is 'Standard_LRS'. When the condition is true (i.e., the VM has a Standard_LRS managed disk), the policy triggers an audit event. Therefore, the policy audits all virtual machines with Standard_LRS managed disks, making option C correct. Options A, B, and D are incorrect because the policy does not audit all non-compliant resources, unmanaged disks, or VMs with Premium_LRS disks of size 1024 GB.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
All Azure resources that are not compliant
Why it's wrong here
The policy scope is restricted to the Microsoft.Compute/virtualMachines resource type, as shown in the assignment, so it cannot evaluate non-compliance on other Azure resource categories like storage or networking. The concept of 'not compliant' is an outcome of the policy evaluation, not a resource attribute that the policy condition can match. Thus, this option incorrectly broadens the policy's applicability beyond its defined scope.
✗
All virtual machines with unmanaged disks
Why it's wrong here
Unmanaged-disk VMs use page blobs in storage accounts instead of managed disk objects, so they lack the Microsoft.Compute/disks/sku.name property that the policy's exists condition checks for. Because the condition only applies when the managed disk SKU is present, classic VHD-based VMs are not evaluated against the Premium_LRS requirement and therefore are not marked non-compliant. The policy was deliberately designed to govern only managed-disk SKUs, leaving unmanaged-disk deployments outside its influence.
✓
Virtual machines with Standard_LRS managed disks
Why this is correct
Standard_LRS is a managed disk SKU but does not equal Premium_LRS, so the policy's notEquals Premium_LRS condition evaluates to true for any VM using it. This makes those VMs non-compliant because the policy mandates Premium_LRS for all managed disks attached to virtual machines. The disk size is not part of the condition, so every Standard_LRS disk, regardless of capacity, triggers the same non-compliance result.
✗
Virtual machines with Premium_LRS managed disks and disk size 1024 GB
Why it's wrong here
Premium_LRS is the exact value that the policy's notEquals condition explicitly excludes, so a Premium_LRS disk can never satisfy the non-compliance predicate. The disk size of 1024 GB is ignored entirely because the policy definition has no size component; it only evaluates the SKU name. Therefore, a VM with a Premium_LRS managed disk remains fully compliant, making this option an incorrect characterization of the policy's effect.

Go deeper

SC-100 Practice Question: Refer to the exhibit

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question