Your organization decides to discontinue using a specific cloud account monitored by CrowdStrike Falcon. What is the correct procedure to deprovision the account from Falcon without leaving residual…

Question

Options

• ADelete all virtual machines associated with the cloud account before deprovisioning.
• BRemove the cloud account from the Falcon console and disable API access for Falcon.
• CRevoke permissions granted to CrowdStrike Falcon on the cloud account.
• DUninstall all CrowdStrike endpoint agents from the cloud account.

• A
  4% (1)
• B
  92% (22)
• D
  4% (1)

Explanation

Option A: Deleting virtual machines is unnecessary for deprovisioning. The focus should be on severing integration points between Falcon and the cloud account. Option B: Removing the account from the Falcon console ensures that Falcon no longer attempts to monitor it. Disabling API access prevents further interaction and completes the deprovisioning Option C: Revoking permissions alone is insufficient because the account remains linked to Falcon. Proper deprovisioning requires both removing the account and disabling API access. Option D: Uninstalling endpoint agents is irrelevant to deprovisioning a cloud account from Falcon. Agents operate independently from cloud account registration.

No community discussion yet for this question.