Microsoft Exam MS-721 Topic 3 Question 40 Discussion

Actual exam question for Microsoft's MS-721 exam

Question #: 40
Topic #: 3

You have a Microsoft Teams Phone deployment.

You are deploying Direct Routing by using a certified Session Border Controller (SBC). The FQDN of the S6C is sbcVcontoso.com. You use signaling port 5067.

You cannot place calls and receive an error message m the Microsoft Teams admin center as shown in the following exhibit.

What is a possible cause of the issue?

ALocation-Based Routing is enabled for the SBC

BThe Baltimore root certificate is missing on the SBC.

CThe Forward P-Asserted Identify (PA!) header is disabled.

DThe failover timer is set to 0 seconds

Show Suggested Answer

Suggested Answer: B

by Tony at Mar 24, 2025, 02:06 AM

Limited Time Offer

25%

Off

Get Premium MS-721 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Yoko

4 months ago

Haha, I bet the IT admin who set this up forgot to renew the SBC certificate. Classic mistake, right?

upvoted 0 times

Laurena

3 months ago

C) The Forward P-Asserted Identify (PA!) header is disabled.

upvoted 0 times

...

Tran

3 months ago

B) The Baltimore root certificate is missing on the SBC.

upvoted 0 times

...

Altha

3 months ago

A) Location-Based Routing is enabled for the SBC

upvoted 0 times

...

Kristofer

4 months ago

Hmm, I'm not sure about this one. Maybe it's Option D and the failover timer is set too low, causing the calls to drop before they can connect properly.

upvoted 0 times

Tayna

2 months ago

Agreed, let's look into that and see if adjusting the failover timer resolves the issue.

upvoted 0 times

...

Yvonne

2 months ago

We should check the settings and make sure the failover timer is properly configured.

upvoted 0 times

...

Viola

2 months ago

Yeah, I think so too. The failover timer being set to 0 seconds could definitely cause problems with call connections.

upvoted 0 times

...

Ozell

2 months ago

Maybe you're right, Option D does seem like a possible cause for the issue.

upvoted 0 times

...

Krystal

3 months ago

D) The failover timer is set to 0 seconds

upvoted 0 times

...

Dylan

3 months ago

C) The Forward P-Asserted Identify (PA!) header is disabled.

upvoted 0 times

...

Frederic

3 months ago

B) The Baltimore root certificate is missing on the SBC.

upvoted 0 times

...

Elina

3 months ago

A) Location-Based Routing is enabled for the SBC

upvoted 0 times

...

Tamera

4 months ago

I'm going with Option C. The Forward P-Asserted Identity (PAI) header is crucial for Direct Routing, so if it's disabled, that could definitely cause call failures.

upvoted 0 times

Freida

3 months ago

I think we should check if the Forward P-Asserted Identity (PAI) header is disabled on the SBC. That could be causing the issue.

upvoted 0 times

...

Lajuana

3 months ago

I agree, Option C seems like the most likely cause. Without the Forward P-Asserted Identity (PAI) header, calls won't work properly.

upvoted 0 times

...

Jerry

4 months ago

But could it also be because the Baltimore root certificate is missing on the SBC?

upvoted 0 times

...

Jeniffer

4 months ago

Option B seems the most likely culprit. If the Baltimore root certificate is missing, the SBC won't be able to establish a secure connection with Teams, leading to this issue.

upvoted 0 times

...

Lavera

4 months ago

I agree with Tandra, the error message seems to indicate a problem with the PAI header.

upvoted 0 times

...

Tandra

4 months ago

I think the issue might be with the Forward P-Asserted Identity header.

upvoted 0 times

...