CCSM Advanced Content Inspection Practice Question
An administrator is configuring Threat Extraction on an R81 Security Gateway. Users complain that PDF files received via email are being sanitized, but they need the original formatting for legal reasons. The administrator wants to ensure that only files from untrusted sources are sanitized while files from a specific trusted partner domain are delivered unmodified. What should the administrator do?
⚠ Common exam trap
It's easy for candidates to confuse Threat Extraction exceptions with Anti-Virus trusted sources, which are separate configurations.
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
✓
Create a Threat Extraction exception rule that bypasses extraction for the trusted partner's domain.
Threat Extraction exceptions are designed to bypass sanitization for trusted sources. By configuring an exception for the partner's domain, the administrator ensures that files from that domain are delivered in their original form, satisfying legal requirements. Other traffic continues to be sanitized, maintaining security. This granular approach is preferred over global changes.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create a Threat Extraction exception rule that bypasses extraction for the trusted partner's domain.
Why this is correct
Threat Extraction exceptions allow administrators to define trusted sources that bypass sanitization. By creating an exception for the partner domain, files from that domain are delivered unmodified, preserving formatting. This meets the legal requirement while still sanitizing other traffic. The exception can be based on sender domain, IP, or other criteria.
- ✗
Configure the partner's domain as a trusted source in the Anti-Virus blade settings.
Why it's wrong here
Trusted sources in Anti-Virus affect scanning, not Threat Extraction. Threat Extraction is a separate blade with its own exception configuration. Adding a trusted source to Anti-Virus would not prevent sanitization of PDFs from that partner, as the extraction policy would still apply. This does not solve the problem.
- ✗
Disable Threat Extraction globally and rely solely on Anti-Virus scanning for all email.
Why it's wrong here
Disabling Threat Extraction globally removes protection for all users and does not selectively allow trusted partner files. This increases risk from malicious files. The requirement is to keep extraction for untrusted sources while exempting a specific partner. Global disablement is too broad and fails to meet the security policy.
- ✗
Modify the Threat Extraction policy to only sanitize files with active content, such as macros.
Why it's wrong here
Threat Extraction sanitizes all files by default, not just those with active content. Changing the policy to only sanitize files with macros would leave other potentially malicious files unsanitized. This does not address the need to exempt a specific partner domain and could weaken security. It also does not guarantee original formatting for the partner's PDFs.
About these practice questions
This CCSM question is part of Courseiva's 219-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.