The Cloud Security Posture Management platform uses REST API calls to carry out the following procedures EXCEPT:

Question

Options

• AManage locking and unlocking cloud-based Security Groups and regions
• BRun the compliance engine and Security Policy groups
• CRemediate non-compliant cloud resources with Cloudbots
• DDeploy agents to each resource in each region

• A
  6% (3)
• B
  2% (1)
• C
  2% (1)
• D
  90% (46)

Explanation

D is correct because CSPM platforms are fundamentally agentless. They interact with cloud environments entirely through cloud provider REST APIs (AWS, Azure, GCP, etc.), meaning they never need to install software on individual resources. Deploying agents to each resource in each region is the opposite of how CSPM works - that describes traditional endpoint security tools, not posture management.

Why the distractors are wrong:

• A is wrong - locking/unlocking Security Groups and regions is a core CSPM function executed via REST API calls to the cloud provider.
• B is wrong - running compliance checks and policy groups is the primary job of a CSPM engine, all triggered and managed through API calls.
• C is wrong - Cloudbots are serverless auto-remediation scripts invoked via API to fix non-compliant resources in real time; this is a key CSPM feature.

Memory tip: CSPM = "No boots on the ground." The whole value proposition is that CSPM gives you cloud-wide visibility and control without touching individual machines - it only speaks to the cloud control plane via APIs. If an answer mentions deploying something to each resource, it's breaking that agentless model and is almost certainly the odd one out.

No community discussion yet for this question.