You suspect that there is malware in one of your container images.
What can you investigate to confirm this?
A Drift indicators
B Container alerts
C Container misconfigurations
D Image detection findings
To confirm whether malware exists within a container image, CrowdStrike Falcon Cloud Security directs investigators to review Image detection findings. These findings are generated during container image assessments, where Falcon performs deep inspection of image layers, binaries, and embedded artifacts.
Image detection findings include indicators of known malware, suspicious executables, malicious scripts, and other threats identified through CrowdStrike's threat intelligence and detection engines. Because container images are often reused across environments, identifying malware at the image level is critical to preventing widespread propagation.
Other options do not directly confirm malware within an image. Drift indicators relate to changes in a running container compared to its original image, not malware embedded in the image itself. Container alerts are typically runtime detections triggered by behavior during execution. Container misconfigurations focus on insecure settings rather than malicious code.
By reviewing image detection findings, security teams can identify infected images early, remediate by rebuilding clean images, and prevent deployment through policy enforcement mechanisms such as the Kubernetes Admission Controller. Therefore, the correct investigation path for suspected malware in a container image is Image detection findings.
Reveal Answer
Next
Question
Reveal Answer
Next
Question
Which are valid attributes when creating an image group?
A Image tags and Image name
B Repository and Image tags
C Image name and Repository
D Registry and Image name
When creating an image group in CrowdStrike Falcon Cloud Security, valid attributes must align with how container images are uniquely identified and organized. The supported attributes include repository and image tags, which together allow precise grouping of related images.
The repository defines the image namespace or project within a registry, while image tags represent versions or variants such as latest, prod, or semantic versions. Using these attributes enables security teams to target policies and assessments consistently across image versions without relying on static names.
Options involving image name are incorrect because Falcon does not use a standalone image name field for grouping. Image identity is derived from registry, repository, and tag combinations. Registry can be used in some grouping contexts, but for image groups specifically, repository and tag are the valid selectable attributes.
Therefore, the correct answer is Repository and Image tags.
Reveal Answer
Next
Question
Reveal Answer
Next
Question
You want to customize the GKE autopilot policy by updating the detection severity (Critical) and the detection type (CIS benchmark deviation) along with Vulnerability ExPRT.ai severities (Critical).
Which combination will trigger the prevention?
A Vulnerability ExPRT.ai severities (Critical), Detection severity (Critical)
B Vulnerability ExPRT.ai severities (Critical), Detection severity (Critical), Image misconfigurations
C Vulnerability ExPRT.ai severities (Critical), Detection severity (Critical), Detection type (CIS benchmark deviation)
In Falcon Cloud Security, prevention actions are triggered when all configured enforcement criteria within a policy are met. When customizing the GKE Autopilot policy, enforcement requires alignment across vulnerability intelligence, detection severity, and compliance context.
By setting:
Vulnerability ExPRT.ai severity = Critical
Detection severity = Critical
Detection type = CIS benchmark deviation
you ensure that both risk-based vulnerability intelligence and compliance deviation severity thresholds are satisfied. This combination confirms that the issue is not only severe but also represents a critical deviation from an accepted security benchmark, justifying prevention.
Omitting the detection type or replacing it with image misconfiguration alone does not meet the enforcement logic required for policy-triggered prevention.
Therefore, Option C is the correct combination that triggers prevention.
Reveal Answer
Next
Question
Which action is required when creating a new image registry connection that accesses a privately hosted registry?
A Verify the registry URL
B Confirm expiration date of the secret for any used service accounts
C Add CrowdStrike IP addresses to registry allowlists
D Verify the token and secret
When configuring a new image registry connection for a privately hosted container registry in CrowdStrike Falcon Cloud Security, the required and most critical action is to verify the token and secret used for authentication. Private registries require explicit credentials so Falcon can securely access and assess container images for vulnerabilities, malware, and misconfigurations.
CrowdStrike supports multiple private registry types (such as private Docker registries or cloud-native registries with restricted access). In all cases, Falcon relies on valid authentication credentials---typically a token, username/password, or service account secret---to pull image metadata and layers. If these credentials are incorrect, expired, or misconfigured, image assessment will fail even if the registry connection appears configured.
Other options may be relevant in specific environments but are not universally required at creation time. Registry URLs are validated during setup, and allowlisting IP addresses may be necessary only if strict network controls are in place. Secret expiration checks are a maintenance concern, not a mandatory creation step.
Therefore, the required action when creating a private registry connection is to verify the token and secret.
Reveal Answer
Next
Question
Reveal Answer
Next
Question