Nokia 4A0-108 Dumps

Discard the register message as RPF-check fails

Forward the register message to Router D (RP) according to its routing table

Forward the register message out of all the interfaces in its (", 239.1.1.1) entry's outgoing interface list

Forward the register message out of all the interfaces in its (192.168.1.1, 239.1.1.1) entry's outgoing interface list

FF02::1

FF02::2

FF02::16

The specific multicast group address which the host is interested in

The resources required by the sending device increases with each new receiver that is added

Unicast is based on TCP which is not scalable

Servers cannot deliver multiple simultaneous unicast flows

Routers do not forward broadcast traffic

This is the initial join message and exclusions of sources will follow

It is willing to receive traffic from any source

This is the initial join message and a selection of source will follow

This is the way it indicates it is leaving the group

A router may be both a candidate-BSR and candidate-RP

A router configured as a candidate-BSR may also be configured as a static RP

A router configured as a candidate-RP may be also be configured as a static RP

A converged multicast network with BSR may have multiple routers elected as BSRs

A converged multicast network with BSR may have multiple routers elected as RPs

The switch populates multicast source addresses into the forwarding table

The switch acts as an IGMP proxy for the receiver

The switch inspects IGMP messages between receivers and routers and populates the forwarding table with active multicast group addresses

The switch inspects all multicast traffic between receivers and routers and populates the forwarding table with active multicast group addresses

FF1X::/16

FF3X::/16

FF3X::/96

FF7X::/16

One to one

Many to all

One to many

Many to many

One to all

Router A

Router B

Router C

Router D

The first 3 bits of the address set to '110'

A value between 223.0.0.0 and 239.255.255.255

The first 4 bits of the address set to '1111'

A subnet mask to indicate the network and host portion of the address

The first 4 bits of the address set to '1110'

PIM DM

PIM ASM

PIM SSM

Either PIM ASM or PIM SSM

To advertise the P-tunnel type to be used for the I-PMSI.

To advertise the group address for the I-PMSI.

To provide MVPN auto-discovery and binding within a single AS domain.

To advertise the customer multicast group address.

A multicast packet destined to FF70::1234.

A multicast packet destined to FF1E::1234.

A multicast packet destined to FF02::1234.

A multicast packet destined to FF3A::1234.

23

25

27

28

It is the process of finding the remote PE connected to the C-root of the multicast tree.

It is the process of finding the remote CE connected to the C-root of the multicast tree.

It is the RPF check for the multicast traffic received from remote PEs in the MVPN.

It is the RPF check for the multicast traffic received from local CEs in the MVPN.

Authentication

Guaranteed delivery

Device security

Prevention of forwarding loops

Prevention of Denial of Service attacks

The system IP address of the originating PE router.

The source IP address of the customer packet.

The outgoing interface IP address of the originating PE router.

The source IP address specified in the MVPN configuration.

P2MPID

Tunnel ID

Extended Tunnel ID

Sub-Group ID

Its data delivery is more efficient than unicast and broadcast.

It is more scalable than unicast and broadcast.

It suits VoD (Video on Demand) services very well.

It suits BTV (Broadcast TV) services very well.

MLD snooping enables switches to forward multicast data to specific hosts interested in the group.

MLD snooping can co-exist with IGMP snooping in the same VPLS service.

Once MLD snooping is enabled, the switch can snoop both MLDv1 and MLDv2 messages.

MLD snooping snoops MLD report and done messages, but not query messages.

Allowing the source to select the multicast group address

Creating standards for Directory Services

Allowing the receiver to specify the source address

Modifying the IGMP messaging format to include the multicast source address

Modifying the PIM messaging format to include the multicast source address

The router elected as Querier on a LAN

The first host to expire their local suppression timer

Only the multicast enabled hosts on a LAN

All routers on a LAN

All multicast enabled routers on a LAN

Receivers are generally unknown by the source

Receivers are generally known by each other since any receiver may be a source

Well suited for applications in which the receivers provide feedback to each other and the source

All devices are potentially capable of generating multicast data

Well suited for applications such as video on demand where each source sends a separate data stream to each of the many different receivers

Yes. As it is maintained by the PIM hellos, it will exist until Router D or Router E is PIM disabled

Yes, it will exist until the source stops sending multicast traffic

Yes, it will exist until Router D prunes itself from the shared path tree

No. Only Source Path Trees will remain

(*.G) Join/Prune

(S.G) Join/Prune

Register

Candidate-RP-Advertisement

Never

30 seconds

60 seconds

120 seconds

260 seconds

A router will never join this group

RP Multicast

Any Source Multicast

Source Based Multicast

Source Specific Multicast

All Sender Multicast

(*, G) Join/Prune

(S.G) Join/Prune

Register Stop

(S, G, rpt) Join/Prune

FF02::FF02:2003

FF02::FE02:2003

FF02::FF:FE02:2003

FF02::1:FF02:2003

Hello, Join/prune messages use All-PIM-Routers multicast address (FF02 D) as destination

Register message uses RP's global unicast IPv6 address as destination

Hello, Join/prune messages use outgoing interface's global unicast IPv6 address as source address

Register message uses outgoing interface's global unicast IPv6 address as source address

The router is the first hop router from the source.

The router is the RP.

The router is one router upstream on the Shared Path Tree from the diverging router.

The router is the last hop router from the source.

Customer multicast routing information is distributed only with PIM.

Customer multicast routing information is distributed only with MP-BGP.

Customer multicast routing information is distributed with either PIM or MP-BGP.

Customer multicast routing information is distributed with either mLDP or RSVP-TE.

The RPF check fails, as PIM relies exclusively on the multicast routing table by default.

The RPF check fails, as it requires the source address be present in both the unicast and multicast routing tables.

The RPF check succeeds, as PIM uses only the unicast routing table by default.

The RPF check succeeds, as PIM uses the multicast routing table first, and then the unicast routing table by default.

It received the query, but it does not wish to join any group.

It is willing to receive traffic for the group from any source.

This is the initial join message; a selection of source will follow.

It indicates that it is leaving the group.

01-00-5e-66-3a-6b

01-00-5e-75-2a-0b

01-00-5e-67-2a-0b

00-01-5e-al-2a-6b

00-01-5e-67-2a-0b

00-01-5e-76-2b-cc

There are no active sources in the LAN.

There is one active source for 239.1.1.1, and two active sources for 239.2.2.2.

The devices on SAP 1/1/4 and SDP 1000:500 have issued joins for 239.1.1.1.

There is a router on SDP 1000:500.

Receivers are generally unknown by the source.

Receivers are generally known by each other, since any receiver may be a source.

It is well suited for applications in which the receivers provide feedback to each other and the source.

All devices are potentially capable of generating multicast data.

It is well suited for applications such as video on demand, where each source sends a separate data stream to each of the many different receivers.