You have a Microsoft 365 E5 subscription that uses Microsoft Teams
Users report poor call quality.
You need to identify the source of the call quality issues and which locations are affected.
What should you do first?
Suggested Answer: C
Get Premium MS-700 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
13 comments · newest first
RO
Ronna
11 months ago
I’d go with uploading reporting labels, seems more organized.
LU
Luis
11 months ago
Surprised that uploading building data isn't the first step!
LI
Lisha
11 months ago
Not so sure about that, user activity might give better insights.
AN
Angella
11 months ago
Definitely agree, that’s the best way to start!
ST
Stephanie
12 months ago
I think we should run the Teams device usage report first.
SH
Shasta
12 months ago
I thought uploading reporting labels for each location was important, but I wonder if we should gather more data before doing that.
KI
Kimberely
1 year ago
I feel like uploading building data to the Call quality dashboard could help pinpoint the locations affected, but I can't recall if that's the first step.
HE
Helene
1 year ago
I'm not entirely sure, but I remember something about the user activity report being useful for identifying call quality problems too.
SH
Sharen
1 year ago
I think we might need to run the Teams device usage report first to see if the issues are related to specific devices.
LA
Latricia
1 year ago
I'm leaning towards Option D, setting up a VPC in a one-off dyno. That way, you can spin up a secure environment just for accessing the database when needed, without having to make permanent changes to the infrastructure.
SH
Shenika
1 year ago
I remember learning about the different NSX node types in class. I'm pretty sure the answer is C - Transport Node. That sounds right based on the question.
IR
Irving
1 year ago
Hmm, not sure I fully understand the details here. Need to think through the impact of the insurance premiums and tax rate.
JI
Jill
1 year ago
If I recall correctly, it's usually about the number of associated APs rather than CPU. But I'm a bit fuzzy on whether it's about free license capacity or just the least number of APs.