What is the primary purpose of configuring a link aggregation group (LAG) on a Junos device?

To combine multiple physical links into a single logical link, increasing bandwidth and providing link redundancy

To increase the maximum transmission unit (MTU) of a physical interface

To provide a backup path that is used only when the primary link fails

To enable a single physical link to carry traffic for multiple VLANs

A service provider is considering using a LAG to connect two routers. The primary goals are to increase bandwidth and provide redundancy. Which statement accurately describes the benefits of a LAG?

A LAG provides both increased bandwidth and redundancy by aggregating multiple physical links into a single logical interface.

A LAG provides redundancy by allowing traffic to fail over to a backup link, but it does not increase bandwidth.

A LAG provides increased bandwidth by combining the capacity of multiple links, but it does not provide redundancy.

A LAG provides increased bandwidth and redundancy, but only if LACP is enabled.

A data center operator has a LAG with four 10-Gigabit links between two switches. Traffic analysis shows that one link is carrying approximately 40% of the traffic while the other three links share the remaining 60%. The traffic consists of many flows between a few high-volume servers. What is the most effective way to improve load balancing across the LAG?

Configure the load-balancing hash to include Layer 4 source and destination ports.

Change the LACP mode from passive to active.

Set the link speed to 40-Gigabit on all members.

Increase the number of member links in the LAG.

Which Junos statement is used to configure the load-balancing hash for an aggregated Ethernet interface?

set interfaces ae0 aggregated-ether-options load-balance

set interfaces ae0 unit 0 family inet load-balance

set forwarding-options hash-key family inet layer-3

set chassis forwarding-options load-balance

Which statement about LAG load balancing is true?

Traffic is distributed based on the destination MAC address only

All traffic is sent on the first available link until it is full

Traffic is distributed across member links based on a hash of packet header fields

Traffic is distributed round-robin, one packet at a time

Juniper NetworksCertified Specialist, Service Provider Routing and Switching (JNCIS-SP)

Domain 10Objective 1

Link Aggregation Groups (LAGs) JN0-364 Practice Questions (Page 2)

Part of the High Availability domain, which makes up ~12% of our current practice bank. Juniper Networks does not publish an official question count, but from its 90-minute exam (~35–60 total, ~4–7 in this domain), expect 1–1 from this objective — we provide 13 practice questions to prepare you well beyond it. (estimate)

13questions here

3free pages

5concepts

Questions 6–10

6foundation · easy
What is the primary purpose of configuring a link aggregation group (LAG) on a Junos device?
Select an answer first
7application · easy
A service provider is considering using a LAG to connect two routers. The primary goals are to increase bandwidth and provide redundancy. Which statement accurately describes the benefits of a LAG?
Select an answer first
8application · medium
A data center operator has a LAG with four 10-Gigabit links between two switches. Traffic analysis shows that one link is carrying approximately 40% of the traffic while the other three links share the remaining 60%. The traffic consists of many flows between a few high-volume servers. What is the most effective way to improve load balancing across the LAG?
Select an answer first
9foundation · easy
Which Junos statement is used to configure the load-balancing hash for an aggregated Ethernet interface?
Select an answer first
10foundation · easy
Which statement about LAG load balancing is true?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to JN0-364

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Juniper Networks. “JN0-364” is a trademark of its owner, used for identification only.