Which two CMX 10.6.2 interferer filtering parameters stop short-lived bursts?
Short answer
BC In CMX 10.6.2, set the Duty Cycle Cutoff (Interferer) and Severity Cutoff (Interferer) filtering parameters to stop bursts of short-lived interferers.
Question
Key Takeaways
It tests the exact CMX 10.6.2 interferer-filtering change, where the trap is picking the plausible-sounding Intensity Cutoff instead of Severity Cutoff.
Cisco CMX 10.6.2 strengthened interferer filtering so the Detect and Locate engine is protected from bursts of short-lived interferers, and this question tests which two filtering parameters must be tuned. The page establishes that the correct pair is Severity Cutoff and Duty Cycle Cutoff (B, C), the two parameters named in the CMX 10.6.2 release notes.
Common mistake: Most learners pair Duty Cycle Cutoff with Intensity Cutoff (giving AC, the source key's answer and one half of the tie), because 'intensity' sounds like signal-strength filtering, but the 10.6.2 release notes name Severity Cutoff for that role instead.
Expert Analysis
Why the Answer Is Correct
CMX 10.6.2 specifically strengthened interferer filtering so that a burst of short-lived interferers does not swamp the Detect and Locate service, and the release guidance points at two interferer filtering parameters that must be set correctly: Duty Cycle Cutoff (Interferer) and Severity Cutoff (Interferer). Duty Cycle Cutoff discards interferers that are present for only a small percentage of the measurement window, which is precisely the behaviour of a short-lived burst. Severity Cutoff raises the interference-severity index required before an interferer is recorded, so transient low-severity events never reach the CMX database. Setting both together is what the requirement asks for, which is why option C and option B are the two parameters to configure.
Why the Other Options Are Wrong
Intensity Cutoff (A) is the seductive distractor: 'intensity' suggests signal strength, but the 10.6.2 guidance does not list it among the two parameters to tune for bursty interferers, and receiver-strength filtering in CMX is expressed through the RSSI cutoffs rather than an 'intensity' threshold. RSSI Maximum (D) is not an interferer filtering parameter at all; it describes a maximum received signal level and does not discard short-lived interferers. Utilization Maximum (E) belongs to channel-utilization monitoring thresholds, not to the decision of whether CMX records an interferer. Selecting A with C leaves the severity dimension unconfigured, so short but high-severity interference bursts still get logged.
Community Comment Notes
Community votes are split exactly in half, with AC and AB each at 50, which shows how many learners fall for the Intensity Cutoff distractor. Lambo1700 quotes the vendor documentation directly, noting that you should set the "interferer filtering parameters for Duty Cycle Cutoff (Interferer) and Severity Cutoff" — the release-note wording for the 10.6.2 change. rrahim argues for Intensity Cutoff plus Duty Cycle Cutoff on the basis that Intensity filters weak signals, but that rationale really describes RSSI filtering, not the interferer-filtering enhancement. claudio392 shared the Cisco CMX Detect and Locate configuration link yet recorded AB, another sign that the distractor is what divides the community. The only pairing that matches the vendor's own language is Duty Cycle Cutoff and Severity Cutoff.
Official Reference
This link opens the official vendor documentation in a new tab.
Exam Strategy
When a question cites an exact software release, expect the answer to come straight from that release's own wording — here the 10.6.2 interferer-filtering note. Read the option list for the two parameter names the vendor actually uses, and treat any 'improved' parameter such as Intensity Cutoff that is not in that guidance as the distractor.
Frequently Asked Questions
Why is Intensity Cutoff wrong for CMX 10.6.2 interferer filtering?
How do Duty Cycle and Severity Cutoff protect CMX from burst interferers?
Community Votes
50% of anonymous learners picked answer AC. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
rrahim 👍 1To strengthen interferer filtering in a Cisco CMX 10.6.2 solution and protect it from bursts of short-lived interferers, the engineer should configure the following two parameters: A. Intensity Cutoff C. Duty Cycle Cutoff Explanation: Intensity Cutoff: This parameter sets a threshold for the signal strength (RSSI) of interferers. Signals below this threshold are ignored, helping to filter out weak or irrelevant interferers. Duty Cycle Cutoff: This parameter defines the minimum duty cycle an interferer must have to be considered significant. Short-lived interferers with low duty cycles are filtered out, reducing the impact of transient interference. These two parameters work together to ensure that only persistent and strong interferers are flagged, protecting the system from short-lived interference bursts.
-
Lambo1700 👍 1From Cisco CMX release 10.6.2, Interferers filtering is strengthened to protect Cisco CMX from burst of short lived interferers. For effective interferer filtering results, we recommend that you set the interferer filtering parameters for Duty Cycle Cutoff (Interferer) and Severity Cutoff (Interferer) correctly. For more information, see Setting Filtering Parameters. With this change, short lived interferers would not be tracked by Cisco CMX and moved under Not Tracked category in the System tab > Settings > Tracking window.
-
claudio392 👍 1https://www.cisco.com/c/en/us/td/docs/wireless/mse/10-6/cmx_config/b_cg_cmx106/the_cisco_cmx_detect_and_locate_service.html
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.