4A0-C02 Sample Questions Answers

It is a global network relying on interconnections provided by Internet service providers.

It is a continuous and interconnected set of public IP networks, advertised and shared across the globe.

It is a settlement-free global network that provides interconnection between Internet service providers.

It is a network that allows any Internet service provider to reach every other Internet service provider in the world.

ISP 1 and ISP 2 have a public transit relationship, while ISP 3 and ISP 4 have a private transit relationship.

ISP 1 and ISP 2 have a private transit relationship, while ISP 3 and ISP 4 have a public transit relationship.

ISP 1 and ISP 2 have a private peering relationship, while ISP 3 and ISP 4 have a public peering relationship.

ISP 1 and ISP 2 have a public peering relationship, while ISP 3 and ISP 4 have a private peering relationship.

Router C sends the update to routers E and F only.

Router C sends the update to routers D, E and F.

Router C sends the update to routers A, B, E and F.

Router C sends the update to routers A, B, D, E and F.

R5-R2-R4-R8

R5-R1-R3-R4-R8

R5-R1-R2-R4-R8

R5-R1-R3-R7-R8

Import policies affect ingress data flow.

Export policies affect ingress data flow.

Both import and export policies affect ingress data flow.

Policy direction and data flow are independent.

Only entry 10 is executed for "client1" and "client2".

Entries 10 and 20 are executed for "client1", and entries 10 and 30 are executed for "client2".

Entries 10 and 20 are executed for "client1", and entries 10, 20 and 30 are executed for

"client2".

Entry 10 is executed for directly-connected routes, entry 20 for "client1" and entry 30 for "client2".

Broadcast traffic will be flooded.

If the unicastSA has not been learned in the FDB, the frame will be dropped.

If the unicast DA has not been learned in the FDB, the frame will be dropped.

All traffic will be dropped, including multicast and broadcast.

Broadcast traffic will be dropped.

Only R4 will be reachable through the VPLS.

B All devices will be reachable through the VPLS.

R4 and R3 will remain reachable.

No devices will be reachable.

The loopback control PDU instructs the remote port to enter loopback mode.

Putting a port in loopback does not affect customer data flow

Both ports must rediscover the OAM capabilities of each other once the port is put back into service.

Both ports must still send Information PDUs to avoid going back to discovery mode.

When a port is in loopback mode, service mirroring will still work if it is a mirror-source or mirror-destination.

All packets, except for information PDUs, are looped back.

TRUE

FALSE

It flushes the local FDB speeding recovery

It discards all packets in the queue and sends icmp-discad messages to the sender. The packets are re-transmitted resulting in no loss of data.

On failure, the PE sends an LDP flush-all-from-me message to all PE devices in the VPLS. This speeds convergence to the new topology.

It is not important to use send-flush-on-failure as Active/Standby signalling automatically converges the FDB in all VPLS instances

The time to relearn thousands of MAC addresses may result in excessive flooding or loss of packets.

If the FDB reaches the limit, the router will discard frames.

Discarding frames when the FDB limit is reached could deny SLA guarantees.

It could take several seconds to relearn thousands of MAC addresses denying QoS/SLA guarantees.

A management VPLS carries customer traffic over the non-blocking spoke-SDP

A VPLS service must be defined as a management VPLS upon creation to take on the role of a management VPLS

The state of a spoke-SDP within a user VPLS will take on the state of the spoke-sdp within the management VPLS.

The management VPLS must be created before the user VPLS.

VPLS1500 is a user VPLS.

VPLS 1500 is management VPLS.

Spanning tree BPDUs for the management VPLS are tagged.

Spanning tree BPDUs for the management VPLS are untagged.

A VPLS is a multipoint Layer 2 service.

A VPLS allows multiple customer sites to be connected in a single bridged domain.

A VPLS on a single node requires a SDP.

With an IP/MPLS infrastructure, service providers can provide multiple VPLS services over a common IP/MPLS infrastructure.

The VPLS switches traffic based on MAC address associated to the appropriate SAP.

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

TLDP is used to create the inner label, RSVP is used to create the outer label.

TLDP is used to create the outer label, RSVP is used to create the inner label.

TLDP and RSVP cannot be used in the same network since they both provide the same label.

When RSVP is used, TLDP must be disabled and static vc labels should be used.

TLDP and RSVP can be used to create either labels based on how they are configured.

MEP

MAP

MIP

MUP

Designated

Discarding

Listening

Root

Forwarding

5-one for each service.

2-one in each direction.

10-five in each direction.

None of the above.

The FDB on PE-A will contain entries for all CE routers.

The FDB on PE-B will contain an entry for the CE router connected to PE-A.

The FDB on PE-B will contain an entry for all CE routers.

The FDB on PE-C will contain entries for the CE router connected to PE-A and the CE router connected to PE-C.

oam mac-populate

oam mac-ping

oam mac-trace

oam svc-ping

oam cpe-ping

On all ports on the Alcatel-Lucent 7750 SR.

At the junction of high-speed to low-speed links or at places of traffic aggregation.

At the junction of low-speed to high-speed links or at places of traffic aggregation.

On low-speed WAN links.

Nowhere. Shaping is only performed in hardware and serviced in a round-robin.

The egress port scheduler takes the ratio of requested bandwidth to total bandwidth request from all children. It allocates bandwidth fairly, using these percentages and not exceeding the egress interface speed.

The egress port scheduler allocates bandwidth based on a WRR distribution method that takes into account the CIR and PIR requested at each level and the max speed, either default or configured, on egress.

The egress port scheduler allocates bandwidth on a first come, first served distribution method that takes into account the total CIR and PIR requested at each level and the max PIR requested from a single level.

The egress port scheduler will limit the bandwidth offered to the egress port based on the over-subscription factor, provisioned under the router interface, while using a WRR scheduler for the remaining bandwidth.

The egress port scheduler will use the Russian Dolls Method to allocate bandwidth to each level of requested bandwidth. HPO-Only is automatically set to 100%, allowing only high priority traffic to be buffered during congestion.

PIR = 4 Mbps, CIR = 1 Mbps

PIR = 1 Mbps, CIR = 1 Mbps

PIR = 10 Mbps, CIR = 1 Mbps

PIR = 5 Mbps, CIR = 5 Mbps

PIR = 1.25 Mbps, CIR = 1.25 Mbps

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.

Has the ability to distinguish traffic in 32 different ways.

Uses the RSVP protocol to create microflows through a network.

Has the ability to manually configure foiwarding classes through a network.

Uses the RSVP protocol to create macroflows through a network.

1

2

3

4

5

8

8

16

6

4

3

The IOM3 adds more memory to both forwarding complexes which increases the total number of queues available.

The IOM3 only contains a single forwarding complex which reduces the number of queues used.

The IOM3 allows multiple forwarding classes to be assigned to a single queue.

The IOM3 allows queues to be dynamically allocated between ingress and egress.

The IOM3 has a larger CPU capable of tracking active hardware queue utilization and adjusting memory allocation accordingly.

Uses standard Ethernet dot1q and QinQ encapsulation.

Requires IS-1S as the protocol to carry control information.

Ethernet Ring APS is a defined ITU standard.

Standard Ethernet forwarding, learning, and flooding rules apply.

PIR = 4Mbps. CIR = 1Mbps

PIR = 1Mbps, CIR = 1 Mbps

PIR = 10Mbps, CIR = 1Mbps

PIR = 5Mbps, CIR = 1.25Mbps

PIR = 1.25Mbps, CIR = 1.25Mbps

EXP markings on transit control traffic are not set correctly.

The priority of all self-generated traffic needs to be lowered to allow all other traffic to take precedence.

The priority of various control packets requires special treatment throughout the network.

The BGP process is consuming too many CPU cycles and is impacting OSPF performance.

Show router bgp routes

Show router bgp routes prefix

Show router bgp routes self-originated

Show router bgp routes hunt

Show router bgp neighbor advertised-routes

9100

9104

9108

9122

9126

010011

100010

010001

001100

010010

MP-BGP for exchanging customer routes with other PEs.

A routing protocol for exchanging customer routes with the CE.

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

MPLS for exchanging labels with other provider core devices.

TRUE

FALSE

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

An additional management VPLS.

Another set of LSPs between PE1 and PE3 and between PE2 and PE4.

Another set of SDPs between PE1 and PE3 and between PE2 and PE4.

Load balancing has to be enabled within the management VPLS.

ASBR1 includes label 131069 in the route update sent to ASBR2.

ASBR1 includes label 131068 in the route update sent to ASBR2.

ASBR1 includes label 131068 in the route update sent to PEL

ASBR1 includes labels 131068 and 131069 in the route update sent to ASBR2.

The BGP session from PE to P is not operational

The BGP session between PEs is operational

The BGP session between PE and CE is not operational

The BGP session from PE to CE is operational

The BGP session between PEs is not operational

Configuring labeled eBGP sessions between CSC-CE and CSC-PE routers.

Configuring a policy on each CSC-CE to advertise local PE addresses to the network provider.

Configuring labeled iBGP sessions between PEs residing in different customer carrier sites.

Advertising the received system addresses of remote PEs using either iBGP or IGP/LDP within each customer carrier site.

Marking/Remarking

Classification

Encapsulation

Scheduling

Sap 1/1/1 create

Sap 1/1/1 customer 10 create

No shutdown

Neighbor 192.168.1.2

64496 – 64511

1 – 56319

64512-65534

64513-65535

There are no defined private AS numbers; there are only private IP addresses.

A confederation is a collection of Autonomous Systems advertised as a single AS number to BGP speakers outside the confederation.

Each member AS must either maintain a full mesh of iBGP sessions, or use route reflection.

Confederations can be used to subdivide ASs that have a large number of BGP speakers into smaller domains.

A full mesh of intra-confederation eBGP sessions is required between the member ASs.

65540

65540 1

65540 65540

65550 65540

All routers with which it has a BGP session.

All routers with which it has a BGP session, except the router it received the update from, which is router B.

All routers with which it has a BGP session, except the router it received the update from, which is router C.

All routers with which it has a BGP session, except the router it received the update from, which is router D.

Only eBGP neighbors.

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.

The SoO attribute can be used to uniquely identify the site from which a PE learns routes.

Before a PE redistributes a VPN-IPv4 route, it can assign an SoO attribute to the route.

The SoO attribute can be used to prevent loops from a single site with multiple CE-PE connections.

The SoO attribute can be used as matching criteria when redistributing routes from the CE to the PE.

3

64

72

16

56

It is an optional transitive attribute.

It is an optional non-transitive attribute.

The atomic aggregate flag is always set if the aggregator attribute is set.

The atomic aggregate flag is always set if the AS Path information is lost due to aggregation.

There can only be one community associated with a route.

Community is an optional non-transitive attribute.

Community is an optional transitive attribute.

Community is a well-known discretionary attribute.

WRED

shapers

schedulers

markers

weighted fair queues (WFQ)

TRUE

FALSE

An LSP must be configured between PE-A and PE-D for this traffic to be forwarded.

A VPLS FDB lookup is done at PE-A of Metro A only

An SDP must be configured between PE-A of Metro A and PE-D of Metro D for this traffic to be forwarded

A VPLS FDB lookup is done at PE-A and PE-C of Metro A and PE-B of Metro B

1

5

15

30

45

The primary contributors to latency are distance, scheduling, and congestion.

The weighted round robin scheduling algorithm will result in more delay for high priority traffic than the regular round robin algorithm.

The round robin scheduling algorithm will result in less jitter for low priority traffic than a strict priority scheduler.

Packet loss can be reduced by decreasing the amount of buffer space available to a queue.

Latency can be reduced by increasing the amount of buffer space available to a queue.

The first 3 bits of the DSCP value are copied directly into the EXP field on the first network egress.

The EXP bits are set on the first network egress, based on a combination of the SAP-ingress classification and the network policy applied.

The 3 priority bits are copied directly from the dot1p header into the EXP field of the first MPLS header.

The EXP bits are set based on a default map that translates DSCP codes into internal forwarding classes on SAP-ingress.

The DSCP value will be set to af21.

The DSCP value will be set to af23.

The DSCP value will remain as ef.

The EXP value, in the MPLS headers, will be set to 4.

The EXP value, in the MPLS headers, will be set to 3.

"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.

65206 65202 65100

(65206 65202)65100

(65204 65206 65202) 65100

(65200) 65100

eBGP peers typically use system addresses for session establishment.

eBGP peers are managed under a single administration.

eBGP peers do not propagate updates learned via iBGP.

eBGP peers are usually directly connected to each other.

BGP version number.

The local AS number.

The Hold Time.

Authentication.

Option A

Option B

Option C

Option D

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.

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.

PE-A will require a SAP id of "sap 1/1/1:200" and PE-B will require a SAP id of "sap 1/1/1:300.

PE-A will require a SAP id of "sap 1/1/1" and PE-B will require a SAP id of "sap 1/1/1".

PE-A will require a SAP id of "sap 1/1/1:0" and PE-B will require a SAP id of "sap 1/1/1:0".

PE-A will require a SAP id of "sap 1/1/1:*" and PE-B will require a SAP id of "sap 1/1/1:*".

RSTP

Dynamic-cost

LACP active

Nothing, There are no loops in LAGs

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 lowest MED.

The route with the shortest AS Path.

The route received from the lowest peer IP address.

The route with the lowest Origin.

Show router bgp routes

Show router bgp routes address-family vpn-ipv4

Show router bgp routes

Show router bgp routes

The prefix is located in an Autonomous System directly connected to this router.

There is a single Autonomous System between the local AS and the AS that originated the prefix.

There are two Autonomous Systems between the local AS and the AS that originated the prefix.

The prefix is located in Autonomous System 65100.

Open

Update

Route Refresh

Notification

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

All out-of-profile traffic will be dropped before any in-profile is dropped.

The time average factor of 0 will discard all packets arriving in the shared buffer pool.

When the shared buffer utilization reaches 51%, in-profile packets might be dropped.

The highest probability with which an out-of-profile packet can be dropped is 20%.

When an in-profile packet arrives and the shared buffer utilization is at 69%, the packet will have approximately a 60% likelihood of being discarded.

The EXP bits in the MPLS header.

The packet's source and destination IP addresses.

The service ID of the service to which the SAP belongs.

The dot1p bits in the frame header.

The packet's Ethertype.

Native IP Packets will not be remarked.

Native IP Packets will be remarked.

Packets associated with a VPRN service on an upstream node will not be remarked.

Packets associated with an ES service on an upstream node will be remarked.

A single connection to a single service provider.

Two connections to a single service provider.

Two connections to two different service providers.

Multiple connections to different service providers.

Authentication is performed before establishing the BGP session.

Authentication can only be configuredon the group or neighbor level.

By default, MD5 authentication is disabled.

Peer authentication may be optionally requested in an open message.

A single route for 192.168.0.0/16 is advertised.

BGP routes 192.168.1.0/27, 192.168.2.0/27, and 192.168.0.0/16 are advertised.

BGP routes 192.168.1.0/27 and 192.168.2.0/27 are advertised, and 192.168.0.0/16 appears as a "Blackhole" route in the route table only.

The given export policy is invalid.

Option A

Option B

Option C

Option D

There will be increased memory usage on the PE

There will be increased CPU utilization on the PE

The CE will reject the overlapping prefix

The PE will not recognize the prefixes as being different

There is no issue with overlapping address space in a traditional Layer 3 VPN

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.

Model B does not require the configuration of VPRN instances on ASBRs.

The ASBRs peer with each other to transport VPN-IPv4 routes between autonomous systems.

PE routers distribute VPN-IPv4 routes to their local ASBR.

One single ASBR is required in each AS to hold the routes for all VPRNs.

Global, router

Router, router

Service, router

Router, service

Service, service

Router, global

Any CE device

Any PE device

Any P device

Any router in the service provider core

Any customer router

True

False

An MP-BGP update carries an MPLS label that is used as the service label for a VPRN.

There can be multiple Route Targets per route in an MP-BGP update.

There can only be one Route Distinguisher per route in an MP-BGP update.

On a specific PE, the MP-BGP updates for prefixes from a single VPRN carry different labels.

Traditional BGP attributes and MP-BGP attributes are present in an MP-BGP update.

VPN-IPv4 routes for all PE system addresses in AS 1000

BGP labeled IPv4 routes for all PE system addresses in AS 1000

VPN-IPv4 routes for all PE system addresses in AS 5000

BGP labeled IPv4 routes for all PE system addresses in AS 5000

A full mesh VPRN

APE hub and spoke VPRN

An extranet VPRN

ACE hub and spoke VPRN