CCSM Advanced Content Inspection Practice Question
A security engineer needs to configure Threat Prevention to inspect compressed archive files containing heavily nested ZIP structures. Which Threat Extraction and Emulation setting prevents Denial of Service attacks caused by recursive decompression bombs?
⚠ Common exam trap
Candidates often confuse 'Maximum file size' with 'Recursion depth', assuming that increasing the file size limit will automatically solve issues related to complex, nested archive structures used in decompression bombs.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure the archive inspection profile to enforce a strict maximum recursion depth threshold.
Limiting archive depth prevents decompression bombs from exhausting gateway memory and CPU by stopping inspection past a specific nesting threshold. This protective mechanism ensures that maliciously crafted zip-within-zip payloads cannot cause a gateway outage. Configuring this threshold correctly maintains operational stability during high-volume data transfers involving legitimate compressed archive payloads.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the maximum archive recursion depth value to unlimited to ensure complete visibility into all nested layers.
Why it's wrong here
Setting recursion depth to unlimited invites catastrophic Denial of Service attacks when malicious actors transmit deeply nested zip bombs. The gateway will exhaust all available memory resources attempting to unpack infinite layers of compressed data.
- ✓
Configure the archive inspection profile to enforce a strict maximum recursion depth threshold.
Why this is correct
Enforcing a strict maximum recursion depth threshold halts decompression once nested archives exceed the permitted layers, preventing recursive decompression bombs from exhausting CPU and memory. This directly satisfies the Denial of Service constraint by bounding resource consumption during archive inspection, rather than relying on file-size or signature-based limits alone.
- ✗
Disable all compressed file inspection capabilities globally across the Threat Prevention security profile.
Why it's wrong here
Disabling archive inspection entirely creates a massive blind spot, allowing threat actors to easily smuggle malicious payloads inside standard compressed files. Security policies must inspect archives while utilizing proper depth limitations rather than disabling the feature.
- ✗
Force the gateway to unpack and store every single extracted file directly onto the local management server.
Why it's wrong here
Writing every extracted file to the management server fills its disk and creates the very resource-exhaustion condition the setting should prevent. Storing extracted content is intended for controlled sandbox delivery to endpoints, not for unpacking unbounded nested archives on the gateway's management plane.
About these practice questions
One of 219 original CCSM practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Check Point exam blueprint
This CCSM practice question is part of Courseiva's free Check Point certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CCSM exam.