What does Prisma Cloud execute to change public cloud infrastructure when autoremediation is enabled?

Question

Options

• Alocal scripts to public cloud APIs
• Bremote function calls to host agents
• Cthird-party integration tools
• Dpublic cloud CLI commands

• B
  94% (17)
• C
  6% (1)

Explanation

When Prisma Cloud autoremediation is triggered, it executes remote function calls to host agents - specifically, it invokes cloud-native serverless functions (like AWS Lambda) that act as agents, which then make the actual API calls to modify the cloud infrastructure on Prisma Cloud's behalf. This serverless agent model keeps Prisma Cloud's control plane decoupled from direct cloud access while still enabling automated fixes.

Why the distractors are wrong:

• A (local scripts to public cloud APIs): Prisma Cloud is a SaaS platform - there is no "local" script execution in the traditional sense; it doesn't run scripts locally on your machine or its own server to call cloud APIs directly.
• C (third-party integration tools): Autoremediation is a native Prisma Cloud capability, not delegated to third-party tools like Terraform or Ansible.
• D (public cloud CLI commands): CLI commands are human-facing tools; Prisma Cloud uses programmatic API/function invocations, not CLI binaries.

Memory tip: Think of it as Prisma Cloud "calling a remote agent to do the dirty work" - it never touches your cloud directly; it fires a function (the agent) that lives in your cloud environment and has the permissions to make changes.

No community discussion yet for this question.