When an engineer was optimizing the customer's existing network, in order to ensure the Internet access quality of online users, he enabled the weak signal user offline control function. The…

Question

Options

• AWhen the signal-to-noise ratio threshold is configured too large, it may cause the terminal to go
• BWhen the terminal signal strength is lower than -25dBm, the terminal is forced to go offline
• CBy default, the function of quickly forcing weak signal users to go offline is enabled.
• DSpecify the threshold value of 25dB for quickly forcing users to go offline based on the signal-to-

• A
  84% (21)
• B
  8% (2)
• C
  8% (2)

Explanation

Options A and D are correct because they accurately describe the behavior and configuration of the weak signal offline control feature. Setting the SNR (signal-to-noise ratio) threshold too high (Option A) means more terminals will fail to meet the threshold, causing legitimate users to be unnecessarily forced offline. Option D correctly identifies that the SNR-based quick-offline mechanism uses a 25dB threshold - when a terminal's SNR drops below this value, it is rapidly disconnected to push it toward a stronger access point.

Option B is wrong because -25dBm is actually a strong signal (dBm scale: closer to 0 = stronger). Weak signal thresholds are typically set at much lower values like -65 to -75dBm. Forcing offline at -25dBm would kick off nearly every connected user.

Option C is wrong because the quick-force-offline function is disabled by default - the scenario explicitly states the engineer had to enable it during optimization, which would be unnecessary if it were on by default.

Memory tip: Think of SNR thresholds like a volume dial - turning it "too high" (too large) makes the system overly sensitive and kicks out users who are actually fine. And remember dBm: the more negative the number, the weaker the signal, so -25dBm is near-excellent, not weak.

No community discussion yet for this question.