You are deploying Microsoft Teams Teams Phone. You have offices in the United States, the United Kingdom, Brazil, India, and China. You will use Direct Routing for all the locations. You need to…

Question

Options

• AAdd the Teams client public IP addresses to the Trusted IPs list.
• BCreate a network site.
• CFrom the Microsoft 365 admin center, assign a usage location.
• DSet Preferred country or region for media traffic for the Session Border Controller (SBC).
• EImplement dynamic emergency calling with Presence Information Data Format Location Object

• A
  83% (24)
• C
  3% (1)
• D
  10% (3)
• E
  3% (1)

Explanation

Building a network topology for roaming bandwidth policies in Teams requires two foundational steps that work together: Trusted IPs identify the public-facing IP addresses of your corporate locations so Teams can recognize when a client is on a known network, and Network Sites are the logical representations of those physical office locations where bandwidth policies are actually applied - without both, Teams cannot match a roaming user to a policy.

Why the distractors are wrong:

• C (Usage location) is a licensing/compliance setting in the M365 admin center that determines which service features are available per country - it has no role in network topology or bandwidth policy assignment.
• D (SBC preferred country/region for media) is a Direct Routing optimization setting for controlling where media traffic flows through the SBC, not a topology-building step.
• E (PIDF-LO / dynamic emergency calling) is a location format used for E911/emergency services, entirely unrelated to bandwidth policy topology.

Memory tip: Think of it as "Trust the address, name the place" - you first Trust the public IPs so Teams knows you're on a corporate network, then you Site the location so a bandwidth policy can be enforced there. No trust = can't detect the location; no site = nowhere to attach the policy.

No community discussion yet for this question.