Prisma Public Cloud enables compliance monitoring and reporting by mapping which configurations to compliance standards?

Question

Options

• ARQL queries
• Balert rules
• Cnotification templates
• Dpolicies

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

Explanation

Policies (D) are the core building blocks Prisma Cloud uses to map cloud configurations to compliance standards - each policy defines a specific configuration check, and these checks are directly linked to compliance frameworks like CIS, NIST, PCI-DSS, and SOC 2, enabling automated compliance reporting and dashboards.

Why the distractors are wrong:

• A (RQL queries): RQL (Resource Query Language) is used to write or investigate configurations, but it's the raw query mechanism, not what gets mapped to compliance standards.
• B (Alert rules): Alert rules determine when and who gets notified when a policy violation occurs - they depend on policies but aren't what maps to compliance standards themselves.
• C (Notification templates): These define the format and destination of alerts (email, Slack, etc.) and have no role in compliance mapping.

Memory tip: Think of it this way - Policies → Product (compliance). Policies are the "rules of the road" that Prisma Cloud checks your cloud against; compliance frameworks are just organized collections of those policies. Everything else (alerts, notifications, RQL) flows from policies, but the mapping itself lives at the policy level.

No community discussion yet for this question.