4A0-C02 Nokia SRA Composite Exam Question and Answers

Traditional BGP loop detection mechanisms may detect a loop in the VPRN scenario, which in fact is not present.

The Alcatel-Lucent 7750 SR accepts routes containing AS_PATH loops by default.

When the CLI command "config>router>bgp# loop-detect discard-route" is used, the Alcatel-Lucent 7750 SR sends a notification to the remote peer and drops the BGP session.

In VPRN implementations where the CE-PE protocol is BGP, it is possible for separate sites of the same customer to use the same BGP autonomous system number.

"Blue-Only"

"Blue-Only" and "Blue-Green"

"Green-Only"

"Extranet-VPN-Green"

"Blue-Green"

Creating an export policy on CSC-CE1 and CSC-CE2 to advertise local PE addresses to the network provider.

Configuring eBGP between CSC-CE and CSC-PE routers; setting the address family to IPv4; and enabling the advertisement of labels for IPv4 routes.

Configuring iBGP between PE and CSC-CE within each customer carrier site; setting the address family to IPv4; and enabling the advertisement of labels for IPv4 routes.

Configuring MP-iBGP between PE1 and PE2; setting the address family to IPv4; and enabling the advertisement of labels for IPv4 routes.

The VPRN ID must match the value used in the vrf-target command.

The VPRN ID must match the value used in the route-distinguisher command.

The router-id command should not be used in this context.

The "no shutdown" command must be configured for the VPRN to be operationally UP.

The service MTU must be equal to or smaller than 1514 bytes.

The service MTU must be 1514 bytes.

The service MTU must be equal to or greater than 1514 bytes.

The service MTU can be any value.

Set the bridge priority to 131071.

Set the bridge priority to 0.

Set the bridge priority to 32768.

Leave the bridge priority as the default.

On the PE the endpoint has been configured with "supress-standby-signalling"

On the PE the endpoint has been configured with "no supress-standby-signalling"

On the MDU the endpoint has been configured with "supress-standby-signalling"

On the MDU the endpoint has been configured with "no supress-standby-signalling1

The port that the SAP belongs to must have the correct ether type configured.

The SAP must be configured with the right VLAN tag.

The SDP VC type must be configured as type VLAN and the correct vlan-vc-tag must be specified.

All of the above.

To reduce the number of VPRN tunnels required.

To allow routes to be exchanged between all, or selected, sites of one VPRN, and all, or selected, sites of a second VPRN.

To simplify the administration of multiple VPRNs.

To allow network access between the headquarter sites of each VPRN service and a shared VPRN service offered by a third party.

The policy should be applied as an import policy on the PE connected to the main site of Customer 1.

The policy should be applied as an import policy on all the PEs connected to the sites of Customer 1.

The policy should be applied as an export policy on the PE connected to the main site of Customer 1.

The policy should be applied as an export policy on all the PEs connected to the sites of Customer 1.

sap 1/1/1:200.100

sap 1/1/1:200*

sap 1/1/1:*

sap 1/1/1:0*

The SDP must be configured to use GRE encapsulation.

The SDP must follow the same path as the user's SDP.

The SDP should be configured to use an RSVP signaled transport with fast reroute.

The SDP must be the same as the user's SDP.

MP-BGP, LDP, RSVP-TE

LDP, RSVP-TE, GRE

MP-BGP, RSVP-TE, GRE

MP-BGP, LDP

MP-BGP only

The AS-Path is not present because a policy is configured on PE2 to set it to null.

The AS-Path is not present because a policy is configured on CE1 to set it to null.

The AS-Path is not present because a policy is configured on PE1 to set it to null.

The AS-Path is not present because VPN-IPv4 routes do not propagate the IPv4 AS-Path BGP attribute.

PE1 pushes two labels on the IP packet and forwards it to ASBR1.

ASBR1 pops the LDP label, swaps the BGP label and forwards the IP packet to ASBR2.

ASBR2 forwards the IP packet with two labels to PE2.

PE2 pops the labels and forwards the unlabeled IP packet to its destination.

VLANs 1-4094

VLAN 0

There is not enough information provided

None, this is an invalid configuration

MAC learning

SA filtering

Routing table population

Frame forwarding

On initialization and then every hello-interval.

Only after receiving LACP packets.

Every 1 second.

Never.

TRUE

FALSE

An error will be generated and the configuration will not be allowed.

The filter entry will be ignored and traffic matching the criteria will be forwarded

All traffic matching entry 20 will be dropped.

Traffic matching entry 20 will be forwarded to sdp 100:1.

Bridge B 1/1/3

Bridge B 1/1/2

Bridge C 1/1/2

Bridge C 2/1/1

Bridge D 1/1/1

Bridge D 1/1/3

Bridge E 1/1/1

Monitor and troubleshoot a point-to-point full-duplex link.

Monitor and troubleshoot end-to-end services.

Can be used at the core to trigger MPLS protection mechanisms when a physical failure detection is not possible.

Should not be used at the core to trigger MPLS protection. BFD is the only method that can be used when physical failure detection is not possible.

Valuable in the last-mile connection to the Service Provider demarcation device.

The frame will be flooded.

The frame will be discarded.

The frame will be fragmented.

Relearning of the MAC address that was purged can only be done once customer traffic resumes.

Relearning of the MAC address that was purged can only be done with the "oam mac-populate" command.

Customer traffic destined to the MAC address that was purged will be dropped until the MAC address is relearned with the "oam mac-populate" command.

Relearning of the MAC address that was purged can only be done with the "oam mac-register" command.

The oam mac-ping will fail. The MAC address must be known in the local FDB to be successful.

The request will be flooded and the only response will come from the PE node that has learned the specified MAC address on a local SAP.

The request will be flooded and the CE device with the corresponding MAC will reply.

All nodes will reply because the oam mac-ping is flooded.

A Spanning Tree BPDU will be sent across the mesh flushing the FDB table in all devices participating in the VPLS instance.

Stale information will be used within the VPLS instance to forward traffic until the FDB ages out.

An LDP control message will be sent to all devices in the mesh participating in the VPLS instance. Only MAC addresses associated with the PE that the failure occurred on will be flushed.

An LDP control message will be sent to all devices in the mesh participating in the VPLS instance. The entire FDB in the VPLS instance will be flushed.

The PE devices participating in the VPLS mesh run a separate Spanning Tree instance in the Core. The Primary Bridge is the Root Bridge for the VPLS mesh.

The PE devices participating in the VPLS mesh determine which bridge is closest to Root Bridge. This bridge becomes the Primary Bridge.

The PE devices participating in the VPLS mesh determine which bridge has the lowest bridge-id. This bridge becomes the Primary Bridge.

The PE devices participating in the VPLS mesh determine which bridge is the Root Bridge. This becomes the Primary Bridge.

The lower the age-time, the greater the amount of flooding

The higher the age-time, the greater the amount of flooding.

The lower the age-time, the lower the amount of flooding.

There is no relationship between the age-time and the amount of flooding.

It will always revert to the previously failed link.

It will never revert to the previously failed link.

It will revert if the precedence of the previously failed link is set to 0 or "primary".

It will revert if the precedence of the previously failed link is lower than the currently active link

SDP id

Service ID

VC Label

Tunnel Label

Customer id

Spanning tree will be disabled on the SAP that the PVST BPDU was received on.

The SAP that the PVST BPDU was received on will be disabled to prevent loops.

The spanning tree encapsulation will be dynamically changed to PVST on the SAP the PVST BPDU was received on.

The PVST BPDU will be ignored and 802.1D 2004 BPDUs will continue to be transmitted on the SAP.

9100 bytes

9104 bytes

9108 bytes

9118 bytes

ports must be on the same MDA

ports must have the same speed and duplex settings

auto negotiation must be on

auto negotiation must be off or limited

port must be in access mode only

The neighbor shown is an ASBR router.

The address family between the peers should be VPN-IPv4 instead of IPv4.

The neighbor address cannot be the interface address 10.3.4.4.

The omitted AS number under "BGP summary" must be equal to 64496.

PE1 pushes three labels on the IP packet: a VPN label, a BGP label, and an LDP transport label.

ASBR1 pops the LDP and BGP labels and swaps the VPN label.

ASBR2 pops the BGP label and pushes an LDP transport label.

PE2 pops two labels and forwards the unlabeled packet to its destination.

Open

Update

Route Refresh

Notification

Option A

Option B

Option C

Option D

Identify the customer network on the egress PE

Establish the LSPs between PE devices

Identify the egress PE in the MPLS domain

Identify the customer network on the ingress PE

Reduced number of VPN tunnels that need to be managed

Centralized filtering policies with the introduction of a hub site

Optimal routing between all sites

Limited configuration required on the hub PE device

Each customer site has a logically direct route to every other customer site.

It provides optimal routing between all sites.

It allows access between all CE devices and all sites participating in the same VRF.

It requires a full BGP mesh in the provider core.

Signaled via MP-BGP and used to identify the egress PE.

Signaled via T-LDP and used to identify the customer VPRN.

Signaled via MP-BGP and used to identify the customer VPRN.

Signaled via RSVP and LDP and used to identify the egress PE.

Signaled via RSVP and LDP and used to identify the customer VPRN.

Static

RIP

OSPF

IS-IS

MP-BGP

BGP

Identify the egress PE in the MPLS domain

Signal the egress VPRN ID

Identify the ingress PE in the MPLS domain

Transport route updates between PEs

The route with the shortest AS path.

The route with the lowest route or tunnel table cost to the NEXT_HOP.

The route with the highest local preference.

The route with the lowest originator ID or BGP identifier.

MP-BGP for exchanging customer routes with other PEs

A routing protocol for exchanging customer routes with the CE

MPLS for exchanging labels with other provider core devices

MPLS for exchanging labels with the CE devices

Targeted LDP for exchanging VPRN labels with other PE devices

A label signaling protocol for defining transport tunnels between PE and CE devices

3

64

72

16

56

WRED monitors the shared buffer space utilization over a period of time.

WRED disables the TCP slow-start congestion control mechanism.

WRED uses two configurable slopes for each buffer pool: a high slope and a low slope.

WRED uses the shared buffer utilization, instead of the individual queue depth, to get a better picture of the average resource utilization of the shared buffer space.

WRED polices the shared buffer pool and marks all packets above a certain rate as "discard eligible."

TRUE

FALSE

In order to mark Layer 2 traffic, sgt-qos will set various ToS bits.

DSCP bits can be set per application, per routing instance.

The DSCP marking stays nc1 for all applications. Only the internal FC is manipulated across different applications.

In order to mark Layer 2 self-generated traffic, network interfaces must be set to dot1Q.

The internal forwarding class for self-generated traffic is set once and applied to the base router and all VPRN instances.

The scheduler will be allocated its "within CIR" bandwidth before all other children at the same level have received their "within CIR" bandwidth.

The scheduler will be allocated its "within CIR" bandwidth after all other children at the same level have received their "within CIR" bandwidth.

The scheduler will be allocated its "within CIR" bandwidth after all other children at all levels have received their "within CIR" bandwidth.

The scheduler will not be allocated its "within CIR" bandwidth.

8

16

6

4

3

It is important that all packets are classified in the same way at all SAP-ingress points.

Once a packet is classified to a forwarding class, it cannot change across the network.

Packet enters a node will be treated as per the local hop's configured policy.

Native IP packets entering a network port will be marked at the first network egress by default

Native IP packets entering a network port will not be marked at the first network egress by default.

Native IP packets entering a network port will be marked at the first network egress, regardless of the re-marking configuration.

H2

NC

L2

EF

H1

BE

Service labels are assigned based used on label blocks.

BGP-AD, RADIUS and Management are used for auto-discovery.

Service labels are signaled using MP-BGP.

Hierarchical VPLS is loosely defined in the standards.

512 MB ingress, 512 MB egress

256 MB ingress, 256 MB egress

1 GB dynamically allocated between ingress and egress.

768 MB dynamically allocated between ingress and egress.

768 MB, with a minimum of 256 MB ingress and egress, and an additional 256 MB dynamically allocated.

The EXP bits in the MPLS header.

The packet's source and destination IP addresses.

The packet's DSCP bits.

The dot1p bits in the frame header.

The ID of an SDP that is transporting the packet.

TRUE

FALSE

A point in the network where EXP bits can be mapped to one of eight predefined FCs, each one with its own queue.

A logical point in a service tunnel where all of customer traffic is aggregated.

A point at which the initial classification of customer traffic occurs.

A point in the network where QoS parameters are discarded in favor of lower-level hardware queuing functions, such as LLI (Link Layer Interleave).

A point in the network where traffic flows from multiple different services are queued together, based on forwarding class.

DSCP

PREC

Dot1p

ToS

Q-in-Q

Operates in transparent mode.

Carries RSTP BPDUs only.

Assigns RSTP state to other VPLS services.

Allows load balancing among multiple management VPLS instances.

TRUE

FALSE

FC H1, high

FC EF, high

FC H2, low

FC EF, low

PIR

CIR

MBS

burst-limit

Set the CBS to 0.

Set the MBS equal to the CBS.

Set the high-priority-only equal to the MBS.

Set the MBS to 0.

Set the high-priority-only to 0.

Each network egress port receives its own buffer pool.

Each SAP-egress port receives its own buffer pool.

All SAP-ingress ports on the same MDA share a buffer pool.

All the network ingress ports on the same MDA share a buffer pool.

Each network ingress port on the same MDA receives its own buffer pool.

QoS is not configured on the router.

Packets in forwarding classes "be" and "12" are being queued.

Traffic belonging to forwarding class "ef" is not experiencing queuing delays.

Traffic belonging to forwarding class "11 "will never make use of the shared buffer pool.

Out-of-profile traffic in the shared buffer pool is being dropped.

The process of delaying packets within a traffic stream to have them conform to a defined traffic profile.

The overall treatment of a defined subset of a customer's traffic within a DiffServ domain.

The process of discarding packets within a traffic stream in accordance with the state of a meter to enforce a defined traffic profile.

The action of setting the DiffServ codepoint of a packet prior to its entry into a downstream DiffServ domain.

A specified algorithm or operation that is implemented in a node in order to realize one or more per-hop behaviors.

8

3

4

5

6

SAPs

SDPs

Services

Queues

Schedulers

Forwarding classes

Next Hop is modified when crossing member AS boundaries within a confederation.

Origin Code is modified when crossing member AS boundaries within a confederation.

AS Path is modified when crossing member AS boundaries within a confederation.

None of the well known mandatory attributes is modified within a confederation.

They provide both peering and transit services.

They provide services only to Tier 1 service providers.

They can be either public or private.

They provide services at the local, regional and continental levels.

TTL is a well-known mandatory BGP attribute.

The default TTL value of an eBGP message is 1, and 64 for an iBGP message.

The default TTL value of an iBGP message can be modified using the multihop command.

The default TTL value of an eBGP message can be modified using the "ttl-security" command.

All BGP routes are rejected.

All BGP routes are accepted.

All routes matching prefix list "List-1" are rejected.

All BGP routes matching prefix list "List-1" are rejected.

Option A

Option B

Option C

Option D

"client1" routes will be tagged with communities "North" and "West".

"client1" routes will be tagged with community "West".

"client1" routes will be tagged with community "North".

"client1" routes will be rejected.

None

2

3

4

"client2" routes will be tagged with communities "West" and "North".

"client2" routes will be tagged with communities "West", "North" and "South".

"client2" routes will be tagged with community "West".

"client2" routes will be tagged with community "South".

Route-Refresh

OpenSent

Notification

Update

Keepalive

1

32

64

255

The route is discarded.

The route is kept in the RIB-In, but marked as an invalid route.

The route is moved to the LOC-RIB, but not marked as a used route.

The route is moved to the route table, but not to the FIB.

BGP is waiting for the TCP connection to be completed.

BGP has established a TCP connection, and an Open message has been sent to that neighbor.

The BGP session has been interrupted, and a TCP connection is being re-established.

BGP has failed to establish a TCP connection to that neighbor, and ConnectRetry has been reset to zero.

AS Path of 65200 65100, Next Hop of router A.

AS Path of 65200 65100, Next Hop of router E.

AS Path of 65100, Next Hop of router E.

AS Path of 65100, Next Hop of router A.

Router R1forms an iBGP session with router R2, and an eBGP session with router R3.

Router R1forms iBGP sessions with routers R2 and R3.

Router R1forms eBGP sessions with routers R2 and R3.

The types of BGP sessions with routers R2 and R3 cannot be determined.

The update is sent to router R2 in ISP 1.

The update is sent to routers R2 and R3 in ISP 1.

The update is sent to all routers in ISP 1.

The update is sent to routers R2 and R3 in ISP 1, and to router R3 in ISP 2.

On router R5 only.

On either router R1or R2.

On both routers R1and R2.

On all routers R1, R2 and R5.

"client2" routes will be only tagged with communities 'East'' and "South".

"client2" routes will be tagged with community "East".

"client2" routes will only be tagged with community "South".

"client2" routes will be rejected.

An update message is used. Only a single prefix can be withdrawn at a time.

An update message is used. Multiple prefixes can be withdrawn at a time.

A withdraw message is used. Only a single prefix can be withdrawn at a time.

A withdraw message is used. Multiple prefixes can be withdrawn at a time.

Well-known mandatory.

Well-known discretionary.

Optional transitive.

Optional non-transitive.

Only the BGP route is in the route table.

Both routes are in the route table.

None of the routes is in the route table.

Only the OSPF route is in the route table.

The aggregator attribute will not be present, and the atomic aggregate flag will not be set.

The aggregator attribute will not be present, and the atomic aggregate flag will be set.

The aggregator attribute will be present, and the atomic aggregate flag will not be set.

The aggregator attribute will be present, and the atomic aggregate flag will be set.

Optional transitive attribute.

Optional non-transitive attribute.

Well-known mandatory attribute.

Well-known discretionary attribute.

7

13

21

42