MS-720 · Question #140
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…
The correct answer is B. No. Option B is correct because setting -MediaBitRateKb to 1 does not specifically prevent video - it severely restricts bandwidth for all media (audio, video, and app sharing), which could break calls entirely rather than just disabling video as intended. The proper parameter to…
Question
Options
- AYes
- BNo
How the community answered
(31 responses)- A26% (8)
- B74% (23)
Explanation
Option B is correct because setting -MediaBitRateKb to 1 does not specifically prevent video - it severely restricts bandwidth for all media (audio, video, and app sharing), which could break calls entirely rather than just disabling video as intended. The proper parameter to explicitly prevent users from enabling video is -AllowIPVideo $false, which directly toggles video capability off. Additionally, New-CsTeamsMeetingPolicy only creates the policy; it must also be assigned to the target users via Grant-CsTeamsMeetingPolicy for it to take effect at that site. Option A is wrong because the solution uses the wrong parameter and incomplete steps - restricting bit rate is a bandwidth control, not a feature toggle.
Memory tip: Think of it this way - "IP Video" needs an "IP Video switch." -AllowIPVideo $false is the on/off switch for video; -MediaBitRateKb is the throttle knob for all media. Exam questions about blocking a specific feature (video, audio, screen share) almost always want an Allow* parameter set to $false, not a bandwidth parameter.
Topics
Community Discussion
No community discussion yet for this question.