Option A: Using the CrowdStrike API to configure granular IAM policies is a potential task during or

after registration, but it is not the initial step. IAM roles and policies should be defined by the cloud

provider's configuration tools, not CrowdStrike, as a preliminary task.

Option B: Inputting cloud provider credentials directly into the CrowdStrike console is not a step in the

configuration process. Instead, API-based integrations rely on secure token-based authentication, not

direct username/password access, to align with best practices for security and scalability.

Option C: Assigning full administrator access to the CrowdStrike service account is unnecessary and

violates the principle of least privilege. Only specific permissions (e.g., read-only access for threat

detection) are required, and overly broad access increases the attack surface.

Option D: Generating an API client ID and secret is the required first step to enable secure

communication between the CrowdStrike Falcon platform and the cloud provider. The client ID and

secret are used for authentication when configuring API integrations, ensuring secure access to the cloud

account's data. Without this step, the integration cannot proceed.

5/192