Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 300-610 Topic 1 Question 93 Discussion

Actual exam question for Cisco's 300-610 exam
Question #: 93
Topic #: 1
[All 300-610 Questions]

An engineer is building a data center network with VXLAN EVPN. The requirement is to use multicast for the broadcast, unknown unicast, and multicast replication.

Which two VNI to multicast group mapping methods must be used to meet these requirements? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Maryrose
1 months ago
I'm feeling a bit like a unicorn here, but I think the right answer is B and D. One VNI to one multicast group, and one NVE to many multicast groups. It just makes sense, you know?
upvoted 0 times
Alyce
3 days ago
I agree with you. And having one NVE to many multicast groups would definitely help with the replication.
upvoted 0 times
...
Jesusita
6 days ago
I think you're onto something there. One VNI to one multicast group does seem like the right choice.
upvoted 0 times
...
...
Dante
1 months ago
B and C all the way! One VNI to one multicast group, and many VNI to one multicast group. Simple and straightforward, just the way I like it.
upvoted 0 times
...
Glory
1 months ago
I'm going with B and E. Using one VNI to one multicast group and many VNI to many multicast groups seems like the most flexible and scalable approach.
upvoted 0 times
Jess
3 days ago
It's important to consider both isolation and scalability when designing the network.
upvoted 0 times
...
Lyla
6 days ago
I think many VNI to many multicast groups provides better scalability and efficiency.
upvoted 0 times
...
Rima
16 days ago
I agree, using one VNI to one multicast group ensures isolation and simplicity.
upvoted 0 times
...
...
Lorrie
2 months ago
Hmm, I'm not sure. Maybe A and C could work, but I'm a bit confused about the 'many NVE to one multicast group' part. Seems like that could get messy.
upvoted 0 times
Elke
5 days ago
User 3: Yeah, using multiple VNIs with one multicast group could simplify the network design.
upvoted 0 times
...
Kenneth
7 days ago
User 2: I agree, having one VNI to one multicast group and many VNI to one multicast group would cover all the requirements.
upvoted 0 times
...
Carlton
14 days ago
User 1: I think B and C would be the best options for this scenario.
upvoted 0 times
...
...
Bronwyn
2 months ago
I'm not sure, but I think C) many VNI to one multicast group could also work. What do you think?
upvoted 0 times
...
Timothy
2 months ago
I think the correct answer is B and C. One VNI to one multicast group and many VNI to one multicast group should meet the requirements.
upvoted 0 times
Alesia
29 days ago
So, the best options would be B and C for the VNI to multicast group mapping methods.
upvoted 0 times
...
Denae
1 months ago
That's a good point, having many NVE to one multicast group can definitely help with scalability.
upvoted 0 times
...
Hannah
1 months ago
I think we should also consider many NVE to one multicast group for better scalability.
upvoted 0 times
...
Val
1 months ago
I agree, using one VNI to one multicast group and many VNI to one multicast group should cover all the requirements.
upvoted 0 times
...
Carole
2 months ago
Yes, that combination should ensure that broadcast, unknown unicast, and multicast traffic is properly replicated across the network.
upvoted 0 times
...
Carlene
2 months ago
I agree, using one VNI to one multicast group and many VNI to one multicast group should cover all the replication requirements.
upvoted 0 times
...
...
Lea
2 months ago
I agree with Christiane. Using one VNI to one multicast group makes sense for this requirement.
upvoted 0 times
...
Christiane
3 months ago
I think the answer is B) one VNI to one multicast group.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77