An administrator is relying on an Azure Bicep linter to find possible issues in Bicep files. Which problem can the administrator expect to find?

Question

Options

• AThe resources to be deployed exceed the quota for a region.
• BSome resources are missing dependsOn statements.
• CThere are output statements that contain passwords.
• DOne or more modules are not using runtime values as parameters.

• A
  3% (1)
• B
  77% (27)
• C
  9% (3)
• D
  11% (4)

Explanation

The Azure Bicep linter performs static analysis on .bicep files before deployment, catching structural and configuration issues in code - and one of its built-in rules flags resources that likely need a dependsOn but are missing it, helping prevent race conditions during deployment.

Why the distractors are wrong:

• A is wrong because quota limits are a runtime/subscription concern checked at deployment time, not something static analysis can detect by reading file contents.
• C is wrong because while some linters (e.g., PSRule for Azure) can flag secrets in outputs, the built-in Bicep linter does not scan output values for sensitive data patterns.
• D is wrong because the linter flags the opposite - it warns when modules do use runtime values (like reference()) as parameters where compile-time values are expected, not when they don't.

Memory tip: Think of the Bicep linter as a "relationship counselor" for resources - its job is to analyze declared dependencies between resources in your code, so missing dependsOn relationships are exactly the kind of structural issue it catches before anything gets deployed.

No community discussion yet for this question.