MENU
Refer to the exhibit. A standard local route group is configured for long-distance calls. Calls from building A succeed, but calls from building B fail. On the system. Each building has is own device pool. The DNA tool is used to test the configuration. How is this issue resolved?
Suggested Answer: D
Get Premium 300-815 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
10 comments · newest first
LA
Lazaro
11 months ago
I agree with Alease, partition changes could fix this.
DE
Demetra
12 months ago
Definitely not option C, that prefix won't help here.
CA
Carri
12 months ago
Wait, why would calls from building A work but not B? That's odd.
OM
Omer
1 year ago
I think adding a local route group (option D) makes more sense.
AL
Alease
1 year ago
Sounds like a partition issue, maybe option A?
JE
Jennifer
1 year ago
Adding a SIP trunk seems like it could help, but I can't recall if that's the best approach for this scenario. Option B is a bit unclear to me.
NA
Nan
1 year ago
I think we practiced a similar question where adding a local route group helped with call failures, so D might be worth considering.
LE
Leoma
1 year ago
I remember something about partitions affecting call routing, so maybe option A could be the right choice?
RO
Rolande
1 year ago
I'm not entirely sure, but I feel like modifying the route pattern could be a solution too. Option C sounds familiar.
EM
Emogene
1 year ago
Ah, I think I've got it! Based on the options, "Result" must be the maximum value that the SeekBar can be moved to. That would make sense in the context of the code and the image.