How does Prisma Cloud Enterprise autoremediate unwanted violations to public cloud infrastructure?

Question

Options

• AIt inspects the application program interface (API) call made to public cloud and blocks the change
• BIt makes changes after a policy violation has been identified in monitoring.
• CIt locks all changes to public cloud infrastructure and stops any configuration changes without prior
• DIt uses machine learning (ML) to identify unusual changes to infrastructure.

• B
  95% (54)
• C
  4% (2)
• D
  2% (1)

Explanation

Option B is correct because Prisma Cloud Enterprise operates in a detect-then-remediate model: it continuously monitors cloud infrastructure, identifies policy violations after they occur, and then automatically triggers remediation actions (such as reverting misconfigurations via cloud provider APIs) to bring resources back into compliance.

• A is wrong because Prisma Cloud is not an inline API gateway - it does not sit in the request path to block API calls before they execute. That describes a Cloud Access Security Broker (CASB) or preventive control, not Prisma Cloud's autoremediation mechanism.
• C is wrong because Prisma Cloud does not lock or freeze all infrastructure changes. A complete lock would break normal DevOps workflows; the platform selectively corrects violating configurations, not all changes.
• D is wrong because autoremediation is policy-driven (rules you define), not ML-driven. ML is used elsewhere in Prisma Cloud (e.g., anomaly detection for user/network behavior), but the autoremediation feature acts on known, defined policy violations.

Memory tip: Think of autoremediation as a smoke alarm with a sprinkler - it doesn't stop you from cooking (no blocking), but after it detects smoke (violation), it automatically responds (remediates). The key word is "after" - Prisma Cloud remediates post-detection, not pre-emptively.

No community discussion yet for this question.