Free Practice Questions for the Nokia SRC Certification 4A0-104 Exam (2026 Updated)

A-pipe

F-pipe

C-pipe

E-pipe

The VC-IDs used between the E-pipe and VPLS must match.

The E-pipe must maintain a MAC FDB in order to connect to the VPLS.

The service ID of the E-pipe can be different from that of the VPLS.

The service MTU of the VPLS and E-pipe must match.

An Ipipe is a point-to-point Layer 2 VPN capable of only carrying Ethernet payloads. An Epipe interworking refers to the transportation of ATM/FR traffic over an Epipe.

An Ipipe is used for performing Ethernet interworking with ATM/FR/PPP using bridged-PDUs. An Epipe interworking is used for performing Ethernet interworking with ATM/FR/PPP using routed-PDUs.

An Ipipe is used for performing Ethernet interworking with ATM/FR/PPP using routed-PDUs. An Epipe interworking is used for performing Ethernet interworking with ATM/FR/PPP using bridged-PDUs.

None of the above.

Dedicates a separate port for each customer.

Performs ARP look-ups for each service.

Maintains a different IP routing table for each service.

Maintains a different MAC Forwarding Database for each service.

3

4

6

12

A VPLS service does not use a MAC FDB.

The router reads the destination MAC address of frames passing through the service.

The router reads the source MAC address of frames passing through the service.

The router uses reverse ARP (RARP) to resolve the MAC addresses for unknown destinations.

The router is programmed with MAC addresses by the network administrator.

1514

1528

1536

1540

1560

A "remote-source" needs to be added to the mirror destination on PEL

A mirror source needs to be added to PE1 with a "remote-source".

This is not possible since the protocol analyzer is located at the Central Office. It needs to be at the customer site.

A mirror source with SAP 1/1/2 needs to be added on PEL

Route distinguishes are used to ensure that VPRN IP prefixes are globally unique.

Route distinguishes are appended to IPv4 prefixes to form IPv6 prefixes.

Route distinguishes are used to determine which routes a VPRN should import.

CE routes use a route distinguisher to indicate which VPRN they are associated to.

vc-type null

vc-type ether

vc-type vlan

vc-type none

The number of VPRN routes can become very large. MP-BGP can support a very large number of routes.

MP-BGP can carry routing information for a number of different address families.

MP-BGP is designed to exchange information between routers that are not directly connected. This feature keeps VPRN routing information out of P-routers.

MP-BGP can carry additional information attached to a route as an optional BGP attribute.

All of the above statements are valid reasons for using MP-BGP as a VPRN routing protocol.

Epipe

Apipe

Fpipe

Ipipe

Cpipe

ISIS, RIP, OSPF, static routes

BGP, ISIS, RIP, OSPF, static routes

BGP, RIP, OSPF, static routes, OSPF3

ISIS, RIP, OSPF, static routes, OSPF3

The SAP 1/1/1 will forward all traffic transparently.

The SAP 1/1/1:0.* will forward all untagged traffic and traffic tagged with VLAN 0.

The SAP 1/1/1:* will forward untagged traffic but not tagged traffic.

TheSAP1/1/1:400 will forward customer traffic tagged with VLAN 400

The SAP 1/1/1:0 will forward untagged traffic and traffic tagged with VLAN 0

Traffic is flooded to all SAPs in the service.

Traffic is flooded to all SAPs and spoke SDPs in the service.

Traffic is flooded to all SAPs and mesh SDPs in the service.

Traffic is flooded to all SAPs, spoke SDPs, and mesh SDPs in the service.

The traffic is not flooded.

TRUE

FALSE

Dot1Q

Q-in-Q

ATM

NULL

Nil

The frame is dropped.

The service ID is added as the VLAN tag.

A VLAN tag of 0 is added as the provider VLAN tag

The frame is forwarded with no VLAN tag

configure service sdp sdp-id gre create

configure service sdp sdp-id create

Idp

Isp Isp-name

Layer 3 direct Internet access service

Layer 2 point-to-point service

Layer 2 multipoint-to-multipoint service

Layer 3 IP multipoint-to-multipoint VPN service

Apipe

Fpipe

Cpipe

Epipe

Bridge service

MP-BGP sessions need to be configured in the service provider network to support a VPN-IPv6 address family.

PE routers must be configured to run MP-BGP and IPv6

PE-to-CE BGP sessions need to be configured to support IPv6.

The provider core must be configured to support IPv6

None of the above statements are false.

All of the above statements are false

Configure an autonomous system number in the global context.

Configure a BGP group and peer parameters.

Configure a VPN-IPv4 address family.

All of the above steps are mandatory.

None of the above steps are mandatory.

OSPF

RIP

BGP

IS-IS

sap 1/1/1

sap 1/1/1:5

sap 1/1/1:5:5

sap 1/1/1:10.100

Each router requires 1 VPLS service.

Each router requires 2 VPLS services.

Each router requires 1 SDP with 2 LSPs, one to each of the other 2 routers.

Each router requires 2 SDPs.

Each router requires 3 SDPs

The mirror destination configuration on PE5 is missing the "remote-source" command,

The mirror destination on PE3 needs a "remote-source" command.

The mirror service IDs on the local and remote destinations must match.

The mirror source on PE3 needs a "remote-source" command.

The mirror source command on the remote PE3 needs a command that tells it to monitor port 1/1/2.

The VPN-IPv4 address family.

The IPv4 address family.

Either IPv4 or VPN-IPv4 address families can be configured.

The same address family must be used for the provider network and the PE-CE.

The service label is swapped for a transport label during transport.

The transport label is used to forward packets between PEs.

The service label is used to identify which VPRN a packet belongs to.

Labels are initially added at the ingress PE.

A VPRN is a Layer 3 service.

A PE maintains a separate forwarding table for each VPRN.

The service provider manages the customers IP addressing.

Multiple VPRNs can be deployed over the same IP/MPLS network infrastructure.

sap 1/1/1

sap 1/1/1:*

sap 1/1/1:0

sap 1/1/1:1

LDP

BGP

MP-BGP

MPLS

MP-BGP in the provider network needs to support the VPN-IPv6 address family.

PE routers must be configured to run MP-BGP.

PE-to-CE BGP sessions need to be configured to support IPv6.

The provider network core must be configured to support IPv6.

An IES requires a spoke SDP.

A virtual route table must be configured for an IES service.

An IES service must use static routes to communicate with customer networks.

An IES must have at least one SAP defined.

Routes from different customers with the same IPv4 address prefix are treated as equivalent by MP-BGP.

MP-BGP will advertise routes to other BGP sessions on the same PE without the need of policies.

The multi-protocol nature of MP-BGP allows VPRN routes to be converted into IPv4 routes in the provider core network.

MP-BGP is an enhanced version of BGP that can carry customer route prefixes for multiple VPRNs.

Configuring an autonomous system number in the global context.

Configuring a BGP group and peer parameters.

Configuring a VPN-IPv4 address family.

Configuring an export policy to advertise routes between PEs.

All routes in the VRF are advertised to the PEs and CEs.

No routes in the VRF are advertised to the PEs or to the CEs.

All routes in the VRF are advertised to the PEs, but not to the CEs.

All routes in the VRF are advertised to the CEs, but not to the PEs.

SDP IDs must be locally unique.

SDPs are specific to one service type.

SDPs must use MPLS for their encapsulation.

An SDP is required for a local service.

They allow a VPLS to scale more easily.

They use mesh SDPs to connect smaller VPLSes together.

They allow a service to span multiple metro networks.

They simplify the configuration required when adding new PEs.

When a PE router receives an IPv4 prefix from its local CE, it creates a VPN-IFV4 prefix.

VPN-IPv4 allows BGP to distinguish between duplicate prefixes originating from different customers.

In a VPRN, data traffic is carried in packets that have VPN-IPv4 addresses.

VPN-IFV4 addresses are only present within the service provider network.

The frame is dropped.

The frame's outer tag is changed to match the SAP, and it is accepted.

The frames outer tag is dropped, and the frame is accepted.

The frame's tags are removed, and the frame is accepted.

Route targets are carried in MP-BGP updates.

Route targets identify the VRF that a VPN-IFV4 prefix is associated with.

Route targets are communicated between PEs that are part of a specific VPRN.

Route targets identify the egress SAP of a service towards a CE.

They are used to identify the VRF table for a prefix at the receiving PE.

They are used by VPRNs to control the distribution of VPN routing information.

They are distributed to all PEs and CEs that are part of the VPRN.

They are distributed to PEs to identify the VRF table that a VPN-IPv4 prefix is associated with.

An IES has a configurable VC MTU.

An IES interface has an IP address assigned to it.

IES supports QoS.

An IES requires a spoke SDP.

IPCP

LDP

PPP

TLDP

A PE uses the same VRF table for all the VPRN services on it.

A PE uses a VRF to maintain forwarding information.

Information for VRFs can be advertised between PEs by MP-BGP.

A PE uses a VRF to route traffic to CEs.

LDP

BGP

MP-BGP

MPLS

Customers must use the same routing protocol as the service provider.

Customers belonging to the same VPRN service must use the same subnet.

Service providers only need to perform configurations on the PEs to add additional VPRNs.

For each VPRN, only one customer can be connected at each PE.

The original VLAN tag is removed.

The original VLAN tag is kept.

The VLAN tag is replaced by a provider tag.

The VLAN tag is kept and a provider tag is added.

ADSPEC sets an SDP's MTU to the smallest MTU value found along the LSP path.

RSVP must be enabled on all MPLS routers of a path to use ADSPEC.

ADSPEC can automatically adjust the service MTU.

ADSPEC can be enabled on individual LSPs.

"ping 192.168.20.1"

"oam vprn-ping 100 source 192.168.10.1 destination 192.168.20.1"

"oam vprn-ping 100 source 192.168.20.1 destination 192.168.10.1"

"ping 10.10.10.6" (router R6's system IP)

Customer ID and SAP ID.

Customer ID and Service ID.

SAP ID and Service ID.

SDP ID and Service ID.

SDP ID and SAP ID.

SDP ID and VC ID.

The FCS is verified and kept in the customer frame. The VLAN tag is kept and transported over the network.

The FCS is verified and kept in the customer frame. The VLAN tag is removed for transport over the network.

The FCS is verified and removed from the frame. The VLAN tag is kept and transported over the network.

The FCS is verified and removed from the frame. The VLAN tag is removed for transport over the network.

The SDP to 10.10.10.1 on router R4 is shutdown.

Router R4 has not sent a label to router R1 (10.10.10.1) yet.

10.10.10.1 has a different service MTU set.

10.10.10.1 has not sent a label to router R4 yet.

1

3

6

12

The FCS is verified and kept in the customer frame. The VLAN tag is kept and transported over the network.

The FCS is verified and kept in the customer frame. The VLAN tag is removed for transport over the network.

The FCS is verified and removed from the frame. The VLAN tag is kept for transport over the network.

The FCS is verified and removed from the frame. The VLAN tag is removed for transport over the network.

Family ipv4

Family ipv6

Family ipv4 ipv6

Family vpn-ipv4

Family vpn-ipv4 vpn-ipv6

Isp-trace

Idp-trace

Sdp-ping

Svc-ping

Ping

They reduce the number of SDPs that need to be configured.

They can be used to work around physical topologies that prevent a fully meshed deployment.

They prevent loops that can be introduced by mesh deployments.

They can simplify the implementation of security policy enforcement and packet inspection.

Only the mirror source must be re-configured.

Only the mirror destination must be re-configured.

Both the mirror destination and mirror source must be re-configured.

Neither the mirror destination nor the mirror source must be re-configured.

They both function as a Layer 2 switch from the service provider's perspective.

They both support SAP encapsulations of null, dot1Q and Q-in-Q.

They both use SAPs as the demarcation point between the customer and the provider.

MAC addresses are learned by VPLSes, but not by E-pipes.

5000

5004

5008

5014

Layer 3 direct Internet access service.

Layer 2 point-to-point service.

Layer 2 multipoint-to-multipoint service.

Layer 3 IP multipoint-to-multipoint VPN service.

The IES's interface must be an IGP peer with the CE.

The IES must use an IP address that is different than the C£.

The IES can only include one SAP for the CE.

The IES must include a network port.

When an Alcatel-Lucent Service Router is rebooted, the mirror destination and mirror source must be re-configured

A mirror destination is shut down by default on an Alcatel-Lucent Service Router.

A mirror source is shut down by default on an Alcatel-Lucent Service Router.

When an Alcatel-Lucent Service Router is rebooted, the mirror destination must be re-configured.

When an Alcatel-Lucent Service Router is rebooted the mirror source must be re-configured.

By default, a 7750 SR does not advertise all routes in the VRF to a CE router.

The default 7750 SR behavior describes all routes in a VRF that are advertised to other PE routers.

By default, a 7750 SR does not advertise all routes in the VRF to other PE routers.

By default, a 7750 SR advertises all routes in the VRF to a CE router.

A mirror source listing port 1/1/4.

A mirror destination listing port 1/1/4.

A remote source command indicating the IP address of the service router he is configuring a local mirror on.

Verification that his IP/MPLS infrastructure is in place

None of the above.

6VPE is a tunneling technology that makes use of MPLS tunnels to transport IPv6 information over an IPv4 MPLS infrastructure.

Customers connected to 6VPE could run native IPv6 or IPv4.

On the PE router, the next hop for a VPN IPv6 address is an IPv6 address, regardless of the nature of the network between the PEs.

6VPE requires an IPv6-aware MPLS core.

Both C and D are false.

All of the above statements are true.

Configuring the physical port in access mode.

Configuring the physical port in network mode.

Enabling the port using the no shutdown command.

Ports are enabled by default, thus no need to use the no shutdown command.

A VPLS service does not use an FDB.

An FDB is maintained on the PE router to track MAC addresses learned from all traffic through the router.

An FDB is maintained on the PE router to track MAC addresses learned from all VPLS services on the router.

A separate FDB is maintained for each VPLS service to track MAC addresses learned from each service.

For each VPLS service, two FDBs are maintained to track MAC addresses; one for unicast traffic and one for multicast and broadcast traffic.

configure router sdp sdp-id

configure service sdp sdp-id create

configure service mpls sdp sdp-id create

configure service gre sdp sdp-id create

configure service sdp sdp-id mpls create

Configuring an Epipe service with a customer ID

Defining a SAP or SAPs.

Binding to an SDP if it is a distributed service.

Enabling the service using the no shutdown command.

Creating and assigning an IP filter to the SAP.

Configuring QoS parameters

1514

1526

1548

1556

1536

RSVP

IPCP

TLDP

PPP

Either RSVP or LDP

TRUE

FALSE

A VRF contains a single VPRN routes.

Every VRF in a PE is associated with one or more route target attributes.

Each VPRN needs a separate VRF in each PE router.

On the 7750 SR, by default, there is a unique one-to-one association between a VPN label and a VRF

All of the above statements are true.

All of the above statements are false.

TRUE

FALSE

Route distinguishes are 12 bytes in length

Route distinguishes are appended to IPv4 prefixes to form 16 byte VPN-IFV1 prefixes.

Route distinguishes are used to determine which routes a VPRN should import.

CE routes must be configured with the proper route distinguishes for the VPRN they are associated to

All of the above statements are true.

All of the above statements are false.

TRUE

FALSE

MTU must match on both services,

Mesh-SDP with matching vc-id configured,

Spoke-SDP with matching vc-id configured.

Spoke-SDP.

config > service# epipe service-id enable

config > service# vpws service-id enable

config > service# service-id no shutdown

config > port# port-id no shutdown

config > service# epipe service-id no shutdown

The mesh SDP on router R4 has been shutdown.

The mesh SDP on 10.10.10.1 has been shutdown.

The service MTU on 10.10.10.1 has been set to a different value.

The IngLbl and EgrLbl that router R4 has for 10.10.10.1 are identical.

The frame is dropped.

The service ID is added as the provider VLAN tag.

A VLAN tag of 0 is added as the provider VLAN tag.

The frame is forwarded with no provider VLAN tag.