exam questions

Exam 350-801 All Questions

View all questions & answers for the 350-801 exam

Exam 350-801 topic 1 question 321 discussion

Actual exam question from Cisco's 350-801
Question #: 321
Topic #: 1
[All 350-801 Questions]





Refer to the exhibit. An engineer must implement toll fraud prevention on a Cisco UCM cluster by allowing only the indicated IP address and protocols through Cisco Unified Border Element. What must be configured?

  • A.
  • B.
  • C.
  • D.
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
auswar3ft
Highly Voted 2 years, 3 months ago
Selected Answer: A
I think it is A the CUBE must allow the customer to reach the representative. it must allow SIP to H323 it must add the SIP trunk remote device .10.10 that is what A is. right?
upvoted 8 times
WeNt48
2 years, 2 months ago
As far as I know ip address trusted list isn't needed when there are up and running dial-peers with valid session target so all we need to focus in here are directions. As we already have h323 to sip we need to add sip to h323. However why in the world do we have two matching answers. From both of them I'd have picked up A since local IP address is trusted by default so 10.10 is the answer. At least this is how I can see this.
upvoted 3 times
...
Panda_man
2 years, 3 months ago
i was thinking the same , especially because in the given config there is already h.323 to sip allowed so now should be in opposite way allowed as well
upvoted 2 times
...
...
v1nhthanh
Most Recent 1 week, 1 day ago
Selected Answer: A
Terrible question
upvoted 1 times
...
v1nhthanh
1 week, 4 days ago
Selected Answer: A
Need the allow-connections both way or CUBE will drop it. The ip address trusted list is not needed if the session target is already defined. Just a trick to get people confuse.
upvoted 1 times
...
G0y0
2 months ago
Selected Answer: A
Well, first let us to discard B. and D. because they are trusting the CUBE interfaces and it is not reasonable. Now, if we see the configuration, it already exists "allow-connections h323 to sip". Just we need add "allow-connections sip to h323" and this condition can be provided by Answer A, because C does not have sense (in first instance because "allow-connections h323 to sip" is done and the cucm ip addres is alreade trusted in the dial peer).
upvoted 1 times
G0y0
2 months ago
Another thing that is weird, why both dial peers are using "session protocol sipv2"?, in this case, it is needed "allow-connections sip-to-sip" and answer B could be the solution even though "ipv4 192.168.11.10" is wrong (however it does not affect, it is cosmetic, because the correct ip addresses are already trusted from the dial-peers). The another stuff weird is in the drawing, I do not understand why the "H323" text (between the CUCM and CUBE icons), if the dial peers are exhibiting other such a very different thing. I just say, watchout in the exam.
upvoted 1 times
...
...
decdca7
5 months, 2 weeks ago
Selected Answer: C
We trust CUCM not the interent/customer/provider
upvoted 1 times
...
b3532e4
8 months, 1 week ago
C is correct, the CUCMs should be trusted
upvoted 2 times
...
TheBabu
11 months, 3 weeks ago
Selected Answer: A
A makes sense to me, you gotta trust the source IP of your incoming calls. This Cisco video states "if the source IP does not match an explicit entry in the configuration as a trusted VoIP source, the call is rejected" https://video.cisco.com/detail/video/6050186898001
upvoted 1 times
...
Komy
1 year ago
Selected Answer: C
I would go with C, and here is my reasoning: If we are trusting the IP of the "Customer", then we are allowing the "Customer" to send whatever traffic/signalling to the CUBE (which can allow for Toll Fraud). So , we do not trust "Customer" side but instead we trust the traffic/signalling from the System side (because the system is configured by Admins not Customers)
upvoted 2 times
...
c6176b5
1 year, 3 months ago
Selected Answer: C
C is correct, the CUCMs should be trusted
upvoted 2 times
...
ALLENNN
2 years ago
Selected Answer: C
CUCM to CUBE
upvoted 2 times
...
Telcoeric
2 years, 3 months ago
Selected Answer: C
I'm going with C. This allows the CUBE to trust endpoints on the line side. Unified CME 12.6 enforces security and toll fraud prevention for SIP line side on Unified CME. The ip address trusted authentication configuration blocks unauthorized calls from the line side. Hence, the Toll fraud Prevention feature secures Unified CME 12.6 and later from unauthorized users on the line side. As part of the configuration for toll fraud prevention on Unified CME 12.6, all the line side endpoints must register to Unified CME. https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucme/admin/configuration/manual/cmeadm/cmetoll.html
upvoted 2 times
...
jayceeAD
2 years, 3 months ago
It should depends what is the call direction (inbound or outbound): "The CLI command ip address trusted list lists the IP address of INCOMING calls from all the registered directory numbers. The command is configured under voice service voip configuration mode." So A, or C or Both
upvoted 2 times
...
Br_Ry
2 years, 3 months ago
Selected Answer: C
Trusts list are who the CUBE trusts, the CUCM is .11 so we must trust .11
upvoted 3 times
...
NNickyy
2 years, 3 months ago
Answer should be A
upvoted 2 times
...
wwisp3422112
2 years, 5 months ago
Can someone help me on this one? Should be A? Allow SIP to H323?
upvoted 1 times
mzmrizmy
2 years, 4 months ago
The IP trusted list should be the dial peer.
upvoted 1 times
...
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago