최신CrowdStrike Certified Cloud Specialist - CCCS-203b무료샘플문제

A. Falcon Prevent Next-Gen Antivirus

B. Falcon Spotlight Vulnerability Management

C. Manual process using cloud provider dashboards

D. Falcon Horizon (CSPM)

A. Building a custom base image with multiple utility tools pre-installed.

B. Using the latest version of the base image without modification.

C. Using a minimal base image with only the necessary dependencies.

D. Relying solely on runtime security tools to mitigate risks.

A. An account with "read-only" permissions to production resources but no login activity in 90 days.

B. An account with permissions scoped to the "least privilege" principle and limited to specific resources.

C. An account with "write" access to storage buckets and "admin" access to IAM policies but only performs read operations.

D. An account with "limited" access to staging resources used for development purposes.

A. Use third-party threat detection solutions like Aqua Security or Sysdig

B. Query the Kubernetes API server using tools like kubectl

C. Enable runtime monitoring in Docker by default

D. Install a Falcon sensor on the Kubernetes cluster nodes

A. Forces all cloud accounts to be grouped together under a single security policy, eliminating flexibility in security management.

B. Allows security teams to segment resources by cloud provider, region, or application to streamline threat monitoring.

C. Only works for multi-cloud environments and cannot be used within a single cloud provider's infrastructure.

D. Requires manual intervention for every new cloud resource, preventing automated assignment of resources to groups.

A. All data and alerts associated with the account are immediately and permanently deleted.

B. The cloud account's data remains visible only if the account is re-registered within 7 days.

C. Data is archived for 30 days and then permanently deleted.

D. Historical data and alerts remain accessible, but new data collection stops.

A. To provide runtime protection and detect threats within containerized workloads.

B. To perform static analysis of container images during the build phase.

C. To replace Kubernetes' native logging and monitoring tools with Falcon's services.

D. To manage Kubernetes cluster scaling based on security alerts.

A. Update the API key's privileges to restrict access temporarily

B. Delete the API key and create a new one with the same scopes

C. Rotate the API key and notify the Falcon administrator immediately

D. Disable the cloud account integration and restart the API client

A. Add the image digest to the allowlist under image assessment exclusions.

B. Apply a "Do Not Scan" label to the container in Kubernetes.

C. Configure an exception for the image repository in the Falcon runtime policies.

D. Add the container image tag to the policy exclusion list.

A. The container runtime (e.g., containerd or CRI-O) is misconfigured; reinstall Kubernetes to ensure proper integration.

B. The sensor DaemonSet is not using a privileged security context; restart with the --privileged flag enabled.

C. The sensor is blocked by Kubernetes network policies; verify the namespace and allow necessary outbound traffic.

D. The sensor lacks permissions to access container runtime data; check the Kubernetes RBAC settings.

A. Disable the firewall on all nodes where container images are stored.

B. Add CrowdStrike IP addresses to the registry allowlist.

C. Add container image tags associated with CrowdStrike to the allowlist.

D. Configure CrowdStrike to bypass allowlist requirements via elevated privileges.

A. API-driven cloud workload discovery

B. Real-time behavioral monitoring

C. Deployment of lightweight monitoring agents

D. Vulnerability patching orchestration

A. To replace the Kubernetes control plane with a secure alternative provided by CrowdStrike.

B. To manage Kubernetes cluster configurations directly from the Falcon console.

C. To monitor and secure containerized applications by detecting runtime threats within Kubernetes clusters.

D. To automatically scale Kubernetes clusters based on threat levels.

A. Rely on traditional antivirus (AV) software to detect vulnerabilities in installed packages

B. Implement only network-based intrusion detection systems (IDS) to monitor for suspicious activity

C. Only allow software installations from trusted vendors without performing vulnerability scanning

D. Utilize Falcon Spotlight to scan for vulnerabilities and integrate with patch management solutions