Verify QoS Markings for Microsoft Teams Calls
Plan network settings for Teams
Your company has a Microsoft 365 subscription. When making voice calls from Microsoft Teams, users report poor call quality at specific times of the day. You need to verify whether Quality of Service (QoS) is being applied to the calls. What should you use?
Answer
Correct answer: D — Use a network monitoring tool to capture and inspect packet headers for DSCP values at the network egress point.
Community Insight
This question tests the distinction between performance monitoring and network configuration verification; the trap is choosing CQD because it reports call quality rather than verifying the presence of QoS tags.
To verify if Quality of Service (QoS) DSCP markings are correctly applied to Microsoft Teams voice traffic, you must use a network monitoring tool to inspect packet headers. The Call Quality Dashboard analyzes performance metrics but cannot validate the underlying network tagging.
Candidates often select Microsoft Call Quality Dashboard (B) because it is the primary tool for troubleshooting poor audio/video, failing to realize that CQD does not display raw packet DSCP values required to verify QoS implementation.
Community Discussion (38 comments)
84103spam
👍 1
Selected: D
Captures packets so you can confirm the Teams client is marking audio/video/signaling with the expected DSCP values — and see whether a network device is stripping or re-marking them.
spektrum1988
👍 2
I think the keywords in the question are "specific times of the day" AI answer is. To verify whether Quality of Service (QoS) is being applied to the calls, you should use B. Microsoft Call Quality Dashboard. This tool provides rich set of reports, including call quality at different times of the day, and can help you troubleshoot call quality issues in Microsoft Teams. It also allows you to check if QoS policies are being applied correctly. The other options are not specifically designed for this purpose. The Microsoft Teams client (A) is the application used for making the calls, Network Testing Companion © is used for testing network performance, and Network Monitor (D) is a protocol analyzer. None of these provide the specific QoS information that the Call Quality Dashboard does.
jwillams
👍 2
Selected: C
To verify whether Quality of Service (QoS) is being applied to the voice calls made from Microsoft Teams, you should use option C, Network Testing Companion. This tool allows you to assess the network conditions and test the connection quality specifically for Microsoft Teams. By using Network Testing Companion, you can analyze the network performance, including metrics like latency, jitter, and packet loss, which can affect call quality. It will help you determine if QoS is being applied correctly and identify any network issues that may be causing poor call quality at specific times of the day.
JamesWilliams
👍 6
Selected: B
B. Microsoft's Call Quality Dashboard. The Microsoft Call Quality Dashboard (CQD) is a tool that provides detailed information about the quality of voice and video calls in Microsoft Teams. It allows administrators to analyze bandwidth, packet loss, delay, and other metrics to identify call quality issues and take steps to resolve them.
mjarroyo
👍 2
Selected: B
The correct answer is B. Microsoft Call Quality Dashboard. To verify whether Quality of Service (QoS) is being applied to the calls, you can use the Microsoft Call Quality Dashboard. This dashboard provides insights into the call quality of Microsoft Teams and Skype for Business calls, including information on call reliability, network performance, and call quality issues.
Ryuseishin
👍 1
Selected: D
You can not see DCSP mark on CDQ. This can only be done with a network monitoring tool at both ends of the call. You may have configured QoS within Teams but if there is a packet shaper at either end, the DCSP marker may be removed and CDQ will not show this.
idioteque
👍 1
The answer is D. Guaranteed.
robcon
👍 4
Selected: B
It's B. D is outdated
Timmy3000
👍 2
Selected: B
https://docs.microsoft.com/en-us/microsoftteams/monitor-call-quality-qos
Bipsy
👍 2
Answer is B . https://docs.microsoft.com/en-us/microsoftteams/monitor-call-quality-qos Call Quality Dashboard (CQD) gives you a network-wide view of call quality across your organization. Use CQD information to help you identify and fix problems. First, Set up CQD. Then read Manage call and meeting quality in Teams.
WS_21
👍 1
Selected: B
https://docs.microsoft.com/en-us/learn/modules/plan-configure-network-settings-for-microsoft-teams/05-implement-quality-service Validate the QoS implementation For the QoS to be effective, the DSCP value set by the Group Policy object needs to be present at both ends of a call. By analyzing the traffic generated by the Teams client, you can verify if the DSCP value has not changed or been stripped out when the Teams workload traffic traverses moves through the network. It is also recommended that you use the Call Analytics and Call Quality Dashboard for evaluating your changes. Network Monitor is the archived protocol analyzer and is no longer under development https://docs.microsoft.com/en-us/windows/client-management/troubleshoot-tcpip-netmon
linmix
👍 4
Read again carefully: the Call quality dashboard is an additional tool, but not the main method of checking. What is described requires a network monitor tool. The link you provide to the article informing Network Monitor has been deprecated specifically suggest "using another, non-Microsoft network protocol analyzer tool".
carbon337
👍 1
Question should say "a network monitor" in my opinion. Network Monitor sounds like an embedded tool such as CQD etc
BenStokes
👍 3
Selected: D
Correct answer is D - Network monitor Justification - I have used this tool extensively to verify DSCP values against the posrt range for audio, video and application sharing set in QoS. The network monitor tool needs to be run at client and server level (in case of on-prem but not possible in Teams :P ) Hope this is a clear answer
Tyffty
👍 5
Selected: D
Only a network monitor that can inspect the packet will show if the QoS marking is applied
sha1979
👍 1
Answer is correct Validate the QoS implementation For the QoS to be effective, the DSCP value set by the Group Policy object needs to be present at both ends of a call. By analyzing the traffic generated by the Teams client, you can verify if the DSCP value has not changed or been stripped out when the Teams workload traffic traverses moves through the network. It is also recommended that you use the Call Analytics and Call Quality Dashboard for evaluating your changes.
TMW
👍 1
https://docs.microsoft.com/en-us/troubleshoot/windows-server/networking/network-monitor-3
TMW
👍 2
In addition, I logged into the CQD. It appears to heave only trends and performance counters. I don't see anywhere that indicates if QOS is being applied or not.
TMW
👍 4
This one appears to be correct: "you capture traffic at the network egress point. You can use port mirroring on a switch or router to help with this." The only way to verify DSCP is applied at both ends, is by analyzing the traffic generated by the Teams client. When they use the term "network monitor" they mean any tool that can capture network traffic and analyze the packets. you can use Wireshark to accomplish this for example. https://docs.microsoft.com/en-us/microsoftteams/qos-in-teams#validate-your-qos-implementation https://cloudbrothers.info/en/optimize-your-microsoft-teams-traffic-with-qos-on-a-unifi-usg/
MimeTalk
👍 1
great article thanks for sharing
jeremyburrows
👍 2
is it not A?? Link: https://docs.microsoft.com/en-us/microsoftteams/qos-in-teams#validate-your-qos-implementation States "By analyzing the traffic generated by the Teams client"
FuzzyKiwiFruit
👍 2
Correct answer is D.
DrGonzo
👍 1
https://www.ismyconnect.com/Welcome/DownloadDocument/305/Is+My+Connect_MS_Teams.pdf Check page 9.
PrettyFlyWifi
👍 2
QoS works at a different OSI layer and thus you need to check DSCP markings, which is best done using Network Monitor (or WireShark but they won't push another product!). I don't think you'll see the DSCP markings in CQD so it can't be that option I think.
kivo
👍 2
I believe that CQD only shows that there is a problem, but it does not assure that the root cause is that QoS is not being applied. I choose D.
JoshD
👍 2
Quality of service (Qos) = network traffic , and to monitor network traffic at specific times of the day you will need a network monitoring tool. D correct
ajcjames1234
👍 1
Can't see any mention of the phrase 'network monitor'.
1337Troll
👍 15
Answer is definitely D, also documented here: https://docs.microsoft.com/en-us/microsoftteams/qos-in-teams#validate-your-qos-implementation CQD is mentioned there only for helping too decide if the port rannge needs to be adjusted.
Eggsamine
👍 7
Repeat of question 34: https://www.examtopics.com/exams/microsoft/ms-700/view/23/
TMW
👍 6
Not any more.
Prep4Exam
👍 4
Q = You need to verify whether QoS.................. Key word: Verify CQD doesn't give U that As stated in the URL above: -> For QoS to be effective, the DSCP value set by the Group Policy object needs to be present at both ends of a call. By analyzing the traffic generated by the Teams client, you can verify that the DSCP value isn’t changed or stripped out when the Teams workload traffic moves through the network. Preferably, you capture traffic at the network egress point. You can use port mirroring on a switch or router to help with this. <- So it's Netmon (or WireShark) to check if the DSCP markings make it 'End2End' .... U could also check if the DSCP markings were received for an individual call: TAC -> Users -> User -> Call History -> Call -> Debug : Connectivity_RecvDSCP
ajcjames1234
👍 1
where are you getting this from and what does it mean? What is DSCP value. It's not clearly explained on Microsoft documents, and there is no mention of the phrase 'network monitor'.
nix1
👍 2
B is the correct answer - Call Quality Dashboard (CQD) to identify problems and then make adjustments using QoS and selective bandwidth additions. https://docs.microsoft.com/en-us/microsoftteams/qos-in-teams#validate-the-qos-implementation
1337Troll
👍 2
It is D, CQD is not mentioned for verifying QOS in the article you linked
nix1
👍 2
B. Microsoft Call Quality Dashboard
Iamrandom
👍 4
I strongly disagree: you might have PL or jitter even with QoS applied (or its misconfiguration could be the very reason of those). D is the correct answer as the tool shows if packets are DCSP marked or not at the egress of the network interface of the client.
Umbravir
👍 2
I think correct answer is B. The dashboard will show how many calls were established and for how many QoS was not applied.
becke
👍 1
B will also show jitter and packet loss which is an indication QoS isnt working.
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The correct approach to verify QoS implementation is using a network monitoring tool (Option D). To confirm that DSCP values are being applied correctly at the egress point of the client or network, an administrator must capture and analyze network traffic packets. This allows for direct inspection of the IP header's Differentiated Services Code Point field.Why the Other Options Are Wrong
Microsoft Call Quality Dashboard (CQD) provides aggregated data on call quality metrics like latency, jitter, and packet loss, but it does not show individual packet headers or DSCP markings. The Microsoft Teams client (A) offers user-facing diagnostics but lacks the granular packet analysis needed to verify network infrastructure settings. Network Testing Companion (C) is used for testing bandwidth and connectivity thresholds, not for inspecting specific protocol tags like DSCP.Community Comment Notes
Community consensus strongly favors Option D. As noted by user '1337Troll', official documentation indicates that analyzing traffic generated by the Teams client is the method to verify QoS. User 'linmix' emphasizes that while CQD helps identify quality issues, it is not the main method for checking if QoS is actually applied. Another commenter, 'Iamrandom', points out that poor quality can exist even with QoS applied, so verifying the tag itself requires a network monitor.Official Reference
Exam Strategy
Always distinguish between tools that measure outcome (like CQD for call quality) and tools that measure configuration (like Network Monitor for QoS tags). When asked to 'verify' network settings like DSCP, look for packet analysis tools.
Frequently Asked Questions
Why isn't Call Quality Dashboard used to verify QoS?
CQD aggregates call quality metrics like jitter and packet loss but does not provide visibility into individual packet headers or DSCP markings.
What does Network Testing Companion do?
It tests network bandwidth and latency thresholds against Microsoft's recommended limits, but it does not inspect packet tags for QoS verification.
Related Analysis
Practice All MS-700 Questions
Access 88 questions with complete answers and detailed explanations.
View Full MS-700 Practice Test →