Free 4A0-100 Practice Test

The statement that the prefix length of the system interface's IP address must be /32 is false. While using a /32 prefix is the standard best practice and is what Nokia documentation describes for this special loopback interface, the Service Router Operating System (SR OS) does not strictly enforce this rule at the CLI. It is technically possible to configure a different prefix length. However, doing so is highly discouraged as it is logically incorrect for a host-specific loopback and can cause unpredictable behavior in routing and management. The absolute term "must" makes the statement factually incorrect because it is not a rigid system constraint.

A. The system interface is a special, software-only loopback interface. It is not tied to any physical hardware and provides a stable address for the router.
C. The system interface is a fundamental component of the SR OS. This interface context is always present and cannot be deleted, thus it exists by default.
D. By default, routing protocols like OSPF and BGP will use the IP address of the system interface as the router ID if a router ID is not explicitly configured.

1. Nokia 7750 SR OS Router Configuration Guide, Release 22.10.R1, Page 70, "Basic Configuration" section.

Reference for C: The description for the no interface command explicitly states: "The system interface cannot be deleted." This confirms the interface is a permanent, default entity.

2. Nokia 7750 SR OS Router Configuration Guide, Release 22.10.R1, Page 65, "System Interface" section.

Reference for A: This section states, "The system interface is a logical interface that is not associated with a physical port... The system interface is also referred to as the loopback interface."

3. Nokia 7750 SR OS Basic System Configuration Guide, Release 22.10.R1, Page 53, "Router ID" section.

Reference for D: This section states, "The router ID is by default the system interface IP address. If the system interface is not configured, the router ID is 0.0.0.0..."

4. Nokia 7750 SR OS Router Configuration Guide, Release 22.10.R1, Page 65, "System Interface" section.

Reference for B (as a descriptive best practice, not a constraint): The guide notes, "This address is a /32 address and is used as the router ID." The falsehood of statement B comes from the fact that this is a description of correct configuration, not a strictly enforced CLI rule, making the word "must" inaccurate. The other options are verifiably true system properties.

The Border Gateway Protocol (BGP) is a path-vector protocol that determines the best route to a destination by applying a sequential, multi-step decision process. This process evaluates a series of path attributes in a specific, fixed order. Key criteria include LOCALPREF, ASPATH length, origin type, and Multi-Exit Discriminator (MED). The first path that is superior based on a specific criterion is selected as the best path, and subsequent criteria are not considered for that comparison. This multi-criteria approach enables complex policy-based routing decisions, which is a primary function of BGP in the internet.

A. The SPF algorithm is used by link-state Interior Gateway Protocols (IGPs) like OSPF and IS-IS, not by BGP.
B. Link metrics (like cost or bandwidth) are used by IGPs to calculate paths. BGP uses a distinct set of path attributes.
D. While a preference value (specifically, the LOCALPREF attribute) is a key criterion, it is only one of many used in the overall selection process.

1. Nokia 7450 ESS, 7750 SR, 7950 XRS, and VSR Router Configuration Guide, Release 22.10.R1. In the "BGP" chapter, the section "BGP Best Path Selection Algorithm" details the sequential list of criteria used for path selection, stating, "When BGP receives multiple routes to the same destination, it must choose one of those routes as the best path. The best path is then eligible to be installed in the routing table." It then lists the multiple steps of the algorithm.

2. RFC 4271 - A Border Gateway Protocol 4 (BGP-4). Section 9.1, "Decision Process," outlines the multi-phase process for route selection. It specifies the exact order of rules, starting with LOCALPREF, followed by ASPATH, ORIGIN, MED, and others, confirming the use of multiple criteria.

3. Kurose, J. F., & Ross, K. W. (2017). Computer Networking: A Top-Down Approach (7th ed.). Chapter 4.6.3, "Determining the Best Routes," explains that BGP routers use an elimination-based process based on multiple attributes: "A router may learn of more than one route to any given prefix. The router’s BGP then invokes its route-selection algorithm... The algorithm has a number of rules...". This university-level textbook confirms the multi-criteria nature of the selection.

The Nokia 7750 Service Router (SR) architecture distinctly separates the control plane and the data plane. The Control Processor Module (CPM) constitutes the control plane. It runs the Service Router Operating System (SR OS) and is responsible for all management and control functions, such as running routing protocols (OSPF, BGP), managing signaling protocols (LDP, RSVP), and providing user access via CLI or SNMP. The CPM programs the forwarding information base (FIB) but does not forward user traffic itself. The data plane, responsible for high-speed packet forwarding, is composed of the Input/Output Modules (IOMs) and their associated Media Dependent Adapters (MDAs) or eXpandable Media Adapters (XMAs).

A. The Media Dependent Adapter (MDA) is a data plane component that provides the physical network interfaces and performs link-level processing before passing traffic to the IOM.
B. The Input/Output Module (IOM) is a core data plane component containing the forwarding engine (ASICs) that makes packet forwarding decisions based on the FIB provided by the CPM.
C. The eXpandable Media Adapter (XMA) is a newer, higher-density version of an MDA. It serves the same function within the data plane, providing physical interfaces for traffic.

1. Nokia 7750 Service Router Data Sheet: "The 7750 SR has a physical and functional separation of the control and data planes. The control plane functions are performed by the Control Processor Module (CPM), and the data plane functions are performed by the IOMs and MDAs." (Nokia 7750 Service Router Data Sheet, 2021, Page 4, "Architecture").

2. Nokia Service Routing Architect (SRA) Self-Study Guide: Preparing for the BGP, VPRN and Multicast Exams (Nokia Press): "The control plane is centralized on the Control Processor Module (CPM), which is the brains of the router... The data plane, also known as the forwarding plane, is a distributed architecture. Each IOM has its own forwarding engine..." (ISBN: 978-0-470-94771-9, Chapter 1, Section "7x50 Hardware Architecture", pp. 4-5).

3. Nokia SR OS R19.10.R1 System Management Guide: "The SR OS is the operating system that runs on the Control Processor Module (CPM) of the 7450 ESS, 7750 SR, and 7950 XRS. The CPM is responsible for managing the system and running the various control protocols..." (Section: "System Management Overview", Paragraph 1). This document implicitly separates the CPM's management/control role from the data forwarding hardware.

VLAN Stacking, also known as Q-in-Q or IEEE 802.1ad, is the technology that enables this functionality. It works by adding a second VLAN tag, called the Service VLAN tag (S-VLAN or S-TAG), to the customer's original Ethernet frame, which already contains a Customer VLAN tag (C-VLAN or C-TAG). The service provider's backbone network then forwards the frame based solely on the outer S-VLAN tag, which is unique per customer. The inner C-VLAN tag is ignored by the provider's core but preserved, allowing different customers to use the same VLAN IDs without conflict. This effectively creates a tunnel for each customer's VLAN traffic across the shared provider network.

A. VLAN Trunking: Standard 802.1Q trunking carries multiple VLANs but cannot distinguish between identical VLAN IDs originating from different customers on the same backbone.
C. VLAN Tagging: This is the fundamental process of adding a single 802.1Q tag. It is the source of the problem (limited, overlapping VLAN space), not the solution.
D. VLAN Routing: This is a Layer 3 function for forwarding traffic between different VLANs. It does not address the Layer 2 transport of overlapping VLANs across a backbone.

1. Nokia 7750 SR OS Services Guide, Release 22.10.R1, Section: "QinQ (802.1ad)". The document states, "QinQ is a technique, also known as VLAN stacking, that is used by service providers to keep customer VLAN traffic segregated and to expand the number of VLANs supported in their network... The provider network transports customer traffic, keeping the customer’s VLANs separate, using a single provider-assigned VLAN."

2. IEEE Std 802.1ad-2005, "IEEE Standard for Local and metropolitan area networks - Virtual Bridged Local Area Networks - Amendment 4: Provider Bridges". Clause 6, "Provider Bridge architecture," describes the addition of a Service VLAN (S-VLAN) component and S-TAG to encapsulate Customer VLAN (C-VLAN) tagged frames, enabling the scaling and isolation required by service providers.

3. Stallings, W. (2016). Foundations of Modern Networking: SDN, NFV, and Cloud Computing. Pearson Education. Chapter 4.3, "IEEE 802.1 VLANs," discusses the limitations of the 12-bit VLAN ID and introduces IEEE 802.1ad (Q-in-Q) as the solution for service providers to handle traffic from multiple customers, each with their own set of VLAN IDs. This is a widely used textbook in university networking courses.

A core function of a Virtual Private Network (VPN) is to provide transparent connectivity for a customer across a shared service provider infrastructure. This transparency means the customer's data payload is encapsulated for transport but is not modified or altered in any way. The original customer packet is delivered to the destination site exactly as it was sent from the source site. Altering the customer's data would violate the integrity of the communication and disrupt applications, defeating the purpose of the transport service.

A. Traffic isolation is a fundamental characteristic of a VPN, ensuring that one customer's traffic is logically separated and secured from all other customers using the same shared infrastructure.
B. The "Virtual" aspect of a VPN explicitly means it is a logical network built upon a shared physical infrastructure, allowing service providers to offer private network services cost-effectively.
D. VPNs are highly customizable and are provisioned to meet the specific requirements of each customer, including topology (e.g., hub-and-spoke, full-mesh), bandwidth, and Quality of Service (QoS).

1. Nokia Networks. (2015). Nokia Scalable IP Networks Self-Study Guide: Preparing for the Network Routing Specialist I (NRS I) Certification (4A0-100). Chapter 7, "Virtual Private Network (VPN) Services," Section 7.1, "VPN Concepts." This section explains that a VPN emulates a private network over a shared infrastructure. The process described involves encapsulating customer packets for transport, which preserves the original customer data without alteration.

2. Rosen, E., & Rekhter, Y. (2006). BGP/MPLS IP Virtual Private Networks (VPNs). RFC 4364. Section 1, "Introduction." The document describes the architecture for provider-provisioned VPNs, where the goal is to forward packets from one customer site to another. The mechanisms detailed, such as MPLS label stacking, are designed to transport the original IP packet transparently without modifying its content.

3. Kurose, J. F., & Ross, K. W. (2021). Computer Networking: A Top-Down Approach (8th ed.). Pearson. Chapter 8.3, "Network Layer Security: IPsec and Virtual Private Networks." The text describes how IPsec, a common VPN technology, operates in tunnel mode by taking an entire IP datagram, encrypting it, and appending a new IP header. This process encapsulates the original data, it does not alter it.

IP route summarization, also known as route aggregation or supernetting, is the process of combining multiple contiguous IP network prefixes into a single, more general prefix advertisement. This is done to reduce the number of routes in routing tables across a network. The statement in option A describes subnetting, which is the inverse process of dividing a large, contiguous IP address block into multiple smaller, more specific sub-networks. Therefore, the statement is false as it misrepresents the function of route summarization.

B. Summarization's primary purpose is to advertise one route instead of many, which directly reduces the size of routing tables on downstream routers.
C. By reducing routing table size and the amount of routing protocol traffic, summarization decreases router processing load, thus improving network scalability.
D. Summarization contains the advertisement of individual link failures. If a specific subnet within a summary flaps, the change is not propagated as long as the summary route remains valid.

1. Nokia 7750 SR OS R19.10.R1 OSPF and IS-IS Guide: In the "OSPF Route Summarization" section, it states, "Route summarization is the consolidation of multiple routes into a single advertisement. This is done at the area border routers (ABRs)... Summarization reduces the amount of routing information that is advertised between areas..." This supports that summarization combines routes (opposite of A) and reduces routing table size (B), which improves scalability (C) and stability (D). (Reference to general concept within OSPF configuration).

2. Nokia SRC-PE (Policy Engine) 12.0 CDRouter Guide, Section: Route Aggregation: "Route aggregation (also called route summarization or supernetting) is a method to minimize the number of routing tables in an IP network. It works by consolidating selected multiple routes into a single route advertisement." This definition directly contradicts option A and supports option B.

3. Kurose, J. F., & Ross, K. W. (2017). Computer Networking: A Top-Down Approach (7th ed.). Pearson. Chapter 5, Section 5.2.3, "The Internet Control Message Protocol (ICMP)," and related routing protocol sections describe how route aggregation (summarization) is a key technique for achieving scalability in the Internet. It explicitly states that aggregation combines prefixes to reduce the size of forwarding tables in routers. This supports options B and C.

A Virtual Private Routed Network (VPRN) is a Layer 3 VPN service. From the customer's perspective, the service provider's network functions as a single, private IP router. The customer's sites connect to this virtual router, allowing them to exchange IP traffic as if they were part of a single, private routed network. The underlying complexity of the provider's MPLS backbone is completely transparent to the customer, who only needs to manage the IP routing between their Customer Edge (CE) devices and the provider's network.

A. All sites are connected to a single wire. This describes a shared medium or bus topology, which is a Layer 1/2 concept and does not accurately represent a routed IP network like a VPRN.
B. All sites are connected to a switched network. This describes a Layer 2 VPN service, such as a Virtual Private LAN Service (VPLS), where all sites share the same broadcast domain, not a Layer 3 VPRN.
D. All sites are connected to the Internet. A VPRN provides private, isolated connectivity between a customer's sites. It is distinct from the public Internet, although access to the Internet can be provided as a separate feature.

1. Nokia 7750 SR OS Services Guide, Release 22.10.R1, Document Part Number: 3HE 18146 AAAD TQZZA, Edition 01.

Section: Virtual Private Routed Network (VPRN) Services: "A VPRN is a Layer 3 virtual private network (VPN). A VPRN emulates a private IP routing domain for a customer... From the customer’s perspective, the VPRN is a private routed network." This statement directly confirms that the customer views the service as a routed network.

Section: VPRN Service Overview: "The PE routers that attach to the VPRN are aware of only the routes that lead to the other sites that are in the same VPRN. Each VPRN has its own routing table." This reinforces the concept of a private, isolated routed domain.

The Internet Assigned Numbers Authority (IANA) is responsible for the global coordination of IP addressing and other Internet protocol resources. IANA manages the unallocated global pool of IP addresses and Autonomous System (AS) numbers. Its primary function in this capacity is to allocate large blocks of these number resources to the five Regional Internet Registries (RIRs). The RIRs then handle the subsequent allocation and registration of these resources to Local Internet Registries (LIRs), such as ISPs and large enterprises, within their specific geographical regions.

A. The allocation of enterprise IP address space is handled by Regional or Local Internet Registries (RIRs/LIRs), not directly by IANA.
B. The allocation of residential IP address space is managed by Internet Service Providers (ISPs), which obtain their address blocks from RIRs.
D. The allocation of North American IP address space is the responsibility of ARIN (American Registry for Internet Numbers), the RIR for that region.

1. Nokia Corporation, Nokia Scalable IP Networks Student Guide 4A0-100 R19, Module 1: Internet and L3 Addressing, Section: "IP Address Management". This section details the hierarchical structure of IP address allocation, placing IANA at the top responsible for global allocation to RIRs.

2. Internet Engineering Task Force (IETF), RFC 7020, "The Internet Numbers Registry System", Section 2: "The IANA Function". This document states, "The IANA function is to allocate blocks of numbers to the RIRs from the unallocated number resource pool that is held in reserve by the IANA function operator."

3. IANA (Internet Assigned Numbers Authority), "Number Resources", Official Website. Retrieved from https://www.iana.org/numbers. The site explicitly states: "We are responsible for coordinating the global pool of IP and AS numbers... We allocate blocks of IP addresses and AS numbers to Regional Internet Registries (RIRs)."

A /31 prefix, as defined by RFC 3021, is used for point-to-point links to conserve IPv4 address space. A /31 subnet mask leaves only one bit for the host portion, yielding two possible addresses. Instead of designating these as network and broadcast addresses (which would leave no usable host addresses), RFC 3021 allows both addresses to be assigned to the two endpoints of the link. Consequently, this type of subnet has no traditional network or broadcast address. Packets that would normally be sent to a broadcast address must be handled by other means, such as sending them to the all-hosts multicast address (224.0.0.1).

B. A loopback address is a single host address represented by a /32 prefix, not a /31 prefix which defines a two-address link.
C. A /32 prefix specifies a single host address. A /31 prefix specifies a subnet containing two usable host addresses.
D. A router ID is a 32-bit number, often configured as a /32 loopback address, used to uniquely identify a router within a routing domain, not a /31 link prefix.

1. Internet Engineering Task Force (IETF) RFC 3021: "Using 31-Bit Prefixes on IPv4 Point-to-Point Links", December 2000.

Section 2, "The Solution", Paragraph 1: "For a point-to-point link, it is not necessary to have a network and a broadcast address... A 31-bit subnet mask allows for exactly two host addresses, and does not have a network or broadcast address. This is the most efficient way to number a point-to-point link, as it uses only two addresses." This directly supports the correct answer (A) and refutes the concept of a broadcast address in a /31 subnet.

2. Nokia 7750 SR OS Router Configuration Guide, Release 22.10.R1: "IP Router Configuration > Network Interfaces > IP Address Attributes".

Section: "Assigning an IP Address to a Network Interface": This section details the configuration of IP addresses on Nokia routers. It specifies that a 31-bit prefix length is supported on point-to-point interface types, aligning with the behavior described in RFC 3021. This confirms the technology is relevant to the Nokia certification context.

3. Fall, K. R., & Stevens, W. R. (2011). TCP/IP Illustrated, Volume 1: The Protocols (2nd ed.). Addison-Wesley Professional.

Chapter 3, "IP: Internet Protocol", Section 3.4.2 "Special-Use IPv4 Addresses": While not a direct Nokia source, this foundational academic text discusses special IP addressing cases. It explains that /32 prefixes are used for host-specific routes (like loopbacks) and references RFC 3021 for the use of /31 prefixes on point-to-point links to avoid wasting addresses on network and broadcast identifiers. This supports the reasoning for why options B and C are incorrect.

A standard 48-bit MAC (Media Access Control) address is globally unique and composed of two distinct parts. The first 24 bits (3 bytes) constitute the Organisationally Unique Identifier (OUI). The IEEE assigns this OUI to a specific hardware manufacturer. The manufacturer then assigns the remaining 24 bits (3 bytes) to create a unique identifier for each network interface controller (NIC) they produce. In the given MAC address 00-20-60-CE-2B-28, the first three bytes, 00-20-60, represent the OUI.

A. 2B-28 is only the last two bytes of the vendor-assigned portion of the MAC address.
B. 00-20 represents only the first two bytes of the OUI, making it an incomplete identifier.
C. CE-2B-28 is the entire 24-bit vendor-assigned portion, also known as the NIC-specific part, not the OUI.

1. Nokia Corporation. (2020). Nokia Scalable IP Networks Student Guide (Course Number: TTP32001V4.0). Module 2: The Data Link Layer, Section: "Ethernet Encapsulation". This section details the structure of an Ethernet frame, including the 6-byte (48-bit) MAC address and the division between the 3-byte OUI and the 3-byte vendor-assigned portion.

2. IEEE Std 802-2014. IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture. Section 8.2.1, "Universal addresses," page 43. The standard states, "The first three octets of a universal address are the Organizationally Unique Identifier (OUI) that is assigned by the IEEE Registration Authority..."

3. Kurose, J. F., & Ross, K. W. (2017). Computer Networking: A Top-Down Approach (7th ed.). Pearson. Chapter 6, "The Link Layer and LANs," Section 6.4.1, "MAC Addresses," page 528. This university-level textbook explains that the first 24 bits of a MAC address identify the manufacturer and are assigned by the IEEE.