In the Microsoft Call Quality Dashboard, you discover an increasing trend of poor-quality calls. You need to implement a solution to identify problematic sites. Which two actions should you perform?…

Question

Options

• ARun the CQD User Feedback (Rate My Call) Report.
• BCreate a building data file.
• CUpload a file to the Tenant Data Upload page.
• DUpload a file to the Reporting Labels page.
• ECreate an endpoint data file.
• FInstall the Power BI connector for Call Quality Dashboard (CQD).

• A
  3% (1)
• B
  71% (25)
• D
  3% (1)
• E
  6% (2)
• F
  17% (6)

Explanation

Identifying problematic sites requires CQD to correlate call quality data with physical locations, which it cannot do without a mapping of network subnets to buildings. Option B (creating a building data file) produces the CSV/TSV that maps IP subnets to site names, regions, and building details. Option C (uploading to the Tenant Data Upload page) is the correct mechanism to ingest that file into CQD, after which location-based reports become available.

Why the distractors fail:

• A (Rate My Call) captures subjective user feedback - useful for perception data, but not for pinpointing which network sites are degrading quality.
• D (Reporting Labels page) is a distractor; building/subnet data goes to Tenant Data Upload, not Reporting Labels.
• E (endpoint data file) maps devices to labels, not network locations to buildings - it won't reveal site-level problems.
• F (Power BI connector) enhances visualization of existing CQD data but adds no location context on its own.

Memory tip: Remember "Build → Upload" - you must Build the location mapping file first, then Upload it via Tenant Data Upload. If the question asks about identifying physical sites, the answer always involves the building data workflow (B + C).

No community discussion yet for this question.