Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Microsoft MS-721 Exam - Topic 3 Question 40 Discussion

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?
B) The Baltimore root certificate is missing on the SBC.
A) Location-Based Routing is enabled for the SBC
C) The Forward P-Asserted Identify (PA!) header is disabled.
D) The failover timer is set to 0 seconds

Microsoft MS-721 Exam - Topic 3 Question 40 Discussion

Actual exam question for Microsoft's MS-721 exam
Question #: 40
Topic #: 3
[All MS-721 Questions]

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?

Show Suggested Answer Hide 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:

0/2000 characters
Submit Cancel
Sue
8 months ago
Nah, I’m leaning towards A. Location-Based Routing can mess things up.
upvoted 0 times
...
Lizette
9 months ago
Wait, could it really be that simple? What about option C?
upvoted 0 times
...
Chana
9 months ago
Definitely agree with B. That’s a common problem!
upvoted 0 times
...
Santos
9 months ago
I think option B is the issue. Missing certificates can cause call failures.
upvoted 0 times
...
France
9 months ago
D seems unlikely, who sets a failover timer to 0 seconds?
upvoted 0 times
...
Delsie
9 months ago
Setting the failover timer to 0 seconds seems odd, but I don't remember if that would prevent calls from going through. It could be a possibility.
upvoted 0 times
...
Jess
10 months ago
The P-Asserted Identity header sounds familiar, but I can't recall if it directly affects call placement. I might need to double-check that.
upvoted 0 times
...
Cherry
10 months ago
I think the Baltimore root certificate is crucial for the SBC to function properly. I recall a practice question that mentioned certificates causing issues.
upvoted 0 times
...
Velda
10 months ago
I remember something about Location-Based Routing, but I'm not entirely sure if it applies here. It seems like it could be a factor.
upvoted 0 times
...
Augustine
10 months ago
Hmm, my first instinct is that the issue could be related to the Forward P-Asserted Identity (PAI) header. I'll review the SBC settings and make sure that's configured correctly. Might also check the failover timer just to be thorough.
upvoted 0 times
...
Rasheeda
11 months ago
I'm a bit confused by all the technical details here. I'll need to take some time to really understand the setup and the error message before I can make a confident guess about the cause. Gotta be careful with these tricky networking questions.
upvoted 0 times
...
Cristal
11 months ago
Alright, this seems straightforward. The error message is pretty clear - it's probably an issue with the certificate on the SBC. I'll focus on checking the Baltimore root certificate and making sure it's installed properly.
upvoted 0 times
...
Rolande
11 months ago
Okay, let's see here. The error message mentions something about the SBC, so I'm guessing the issue is related to the SBC setup. I'll need to double-check the FQDN, port, and any other SBC settings to see if they're configured correctly.
upvoted 0 times
...
Joni
11 months ago
Hmm, this looks like a tricky one. I'll need to carefully review the details about the SBC configuration and the error message to figure out the most likely cause.
upvoted 0 times
...
Yoko
1 year ago
Haha, I bet the IT admin who set this up forgot to renew the SBC certificate. Classic mistake, right?
upvoted 0 times
Laurena
1 year ago
C) The Forward P-Asserted Identify (PA!) header is disabled.
upvoted 0 times
...
Tran
1 year ago
B) The Baltimore root certificate is missing on the SBC.
upvoted 0 times
...
Altha
1 year ago
A) Location-Based Routing is enabled for the SBC
upvoted 0 times
...
...
Kristofer
1 year 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
1 year ago
Agreed, let's look into that and see if adjusting the failover timer resolves the issue.
upvoted 0 times
...
Yvonne
1 year ago
We should check the settings and make sure the failover timer is properly configured.
upvoted 0 times
...
Viola
1 year 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
1 year ago
Maybe you're right, Option D does seem like a possible cause for the issue.
upvoted 0 times
...
Krystal
1 year ago
D) The failover timer is set to 0 seconds
upvoted 0 times
...
Dylan
1 year ago
C) The Forward P-Asserted Identify (PA!) header is disabled.
upvoted 0 times
...
Frederic
1 year ago
B) The Baltimore root certificate is missing on the SBC.
upvoted 0 times
...
Elina
1 year ago
A) Location-Based Routing is enabled for the SBC
upvoted 0 times
...
...
Tamera
1 year 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
1 year 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
1 year 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
1 year ago
But could it also be because the Baltimore root certificate is missing on the SBC?
upvoted 0 times
...
Jeniffer
1 year 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
1 year ago
I agree with Tandra, the error message seems to indicate a problem with the PAI header.
upvoted 0 times
...
Tandra
1 year ago
I think the issue might be with the Forward P-Asserted Identity header.
upvoted 0 times
...

Save Cancel