Which feature is used to control approval workflows before provisioning resources?

Question

Options

• ARole-Based Access Control
• BPolicies
• CMonitoring
• DPricing Plans

• A
  6% (2)
• B
  88% (30)
• C
  3% (1)
• D
  3% (1)

Explanation

Policies are the correct answer because they define rules and conditions that must be satisfied - including human approval gates - before infrastructure or cloud resources can be provisioned. In platforms like Terraform Cloud, AWS Service Catalog, or Azure Policy, policies enforce governance checkpoints in automated workflows.

• A (RBAC) controls who can do what (permissions), but does not pause provisioning to wait for approval.
• C (Monitoring) observes running resources after deployment; it plays no role in pre-provisioning gates.
• D (Pricing Plans) governs billing tiers and feature access, not workflow approvals.

Memory tip: Think of Policies as the "rules of the road" - they can include a stop sign (approval gate) before you're allowed to drive (provision). RBAC decides who holds a license, but Policies decide whether the road is open.

No community discussion yet for this question.