Free BL00100-101E Practice Test Questions and Answers (2026)

5G achieves higher reliability, particularly for Ultra-Reliable Low-Latency Communication (URLLC) services, through several key architectural enhancements. Multi-connectivity (B), such as Dual Connectivity, provides redundancy by allowing a User Equipment (UE) to maintain simultaneous connections to multiple transmission points. If one link degrades or fails, the other can ensure uninterrupted service, directly increasing the reliability of the connection. A lower Time Transmission Interval (TTI) (D), enabled by the flexible 5G NR frame structure (mini-slots), allows for much faster transmission and retransmission of data packets. This rapid feedback and error correction mechanism is critical for ensuring that data is successfully delivered within the strict latency and reliability budget (e.g., 99.999% success rate), thus driving higher overall reliability.

A. Higher spectral efficiency: This primarily increases network capacity and data throughput (bits/sec/Hz). It does not inherently make the radio link more robust or reliable against transmission errors.
C. Connectionless radio access: This feature is designed to reduce latency and signaling overhead for small, infrequent data transmissions (common in mMTC), not to provide the sustained, robust connection required for high-reliability services.

1. Nokia. (2020). 5G New Radio: Highlights of 3GPP Release 15 and 16. White Paper. Page 6, Section "Ultra-reliable low-latency communication". The paper states, "The key 5G NR enablers for URLLC are the new flexible frame structure with short TTI... and multi-connectivity for improved reliability."

2. 3GPP. (2017). TR 38.913 V14.3.0: Study on scenarios and requirements for next generation access technologies. Section 7.1, "URLLC service requirements". This document outlines the need for technologies that can meet 99.999% reliability, which underpins the design of features like short TTI and multi-connectivity.

3. Bennis, M., Letaief, K. B., et al. (2018). "Framing the 5G-URLLC Opportunity." 2018 IEEE 29th Annual International Symposium on Personal, Indoor and Mobile Radio Communications (PIMRC). DOI: 10.1109/PIMRC.2018.8580933. The paper discusses how "packet duplication over two distinct base stations" (multi-connectivity) and "short TTI" are fundamental enablers for achieving URLLC.

The Unified Data Management (UDM) is a fundamental Network Function (NF) within the 5G Core's Service-Based Architecture. Its primary role is to manage and provide access to a unified database containing user subscription information. This includes user identification (SUPI), authentication credentials, access authorization policies, and mobility/session subscription data. The UDM exposes these functionalities as services (e.g., NudmSubscriberDataManagement, NudmUEAuthentication) over the Service-Based Interface (SBI) to other authorized NFs, such as the Access and Mobility Management Function (AMF), Session Management Function (SMF), and Authentication Server Function (AUSF). It acts as a front-end to the Unified Data Repository (UDR).

B. This describes the Authentication Server Function (AUSF), which is responsible for executing the authentication procedures, using credentials it obtains from the UDM.
C. The UDM is a network function, not a data repository. It manages structured data stored in the Unified Data Repository (UDR), not unstructured data.
D. This describes the Network Repository Function (NRF), which maintains a registry of available NF instances and their profiles, enabling service discovery within the 5G Core.

1. 3GPP TS 23.501, "System architecture for the 5G System (5GS); Stage 2" (Release 17).

Section 6.2.3, Unified Data Management (UDM): This section explicitly defines the UDM's functionalities, including generation of authentication credentials, user identification handling, access authorization, and subscription management. It also details how the UDM provides services to the AMF, SMF, and AUSF.

2. Nokia, "Cloud native data and identity management for the 5G era" White Paper.

Page 4, "Nokia Unified Data Management": This document describes the Nokia UDM as a function that "manages subscription information for the 5G core" and "provides this information to the AMF, SMF and AUSF network functions." This directly supports the description in option A.

3. A. A. N. Abdalla, M. A. M. Ali and H. S. Ali, "A Comprehensive Survey on 5G Core (5GC) Network," 2021 International Conference on Computer, Control, Electrical, and Electronics Engineering (ICCCEEE), Khartoum, Sudan, 2021, pp. 1-6.

Section III.B, "5G Core Network Functions": This academic paper describes the UDM as the function that "stores the long-term security credentials used in the authentication for the SUPI, subscription data, and profiles of the user." It also notes its role in providing services to AMF, SMF, and AUSF. DOI: 10.1109/ICCCEEE54232.2021.9621328.

5G's increased throughput capacity is driven by several key radio access network enhancements.
1. MU-MIMO and beamforming (part of Massive MIMO) significantly boost capacity by allowing a base station to serve multiple users simultaneously on the same frequency resource and by focusing radio energy towards specific devices. This improves signal quality and enables spatial multiplexing.
2. Higher spectral efficiency is achieved through advanced modulation (up to 256-QAM) and channel coding (LDPC), which pack more data bits into each unit of spectrum (Hz).
3. Multi-connectivity (e.g., Dual Connectivity) allows a User Equipment (UE) to aggregate radio resources from both 4G and 5G base stations simultaneously, directly increasing the peak data rate available to the user.

C. Network Slicing: This is a network architecture concept for creating virtual networks with specific characteristics; it allocates and manages existing capacity, but does not inherently increase it.

1. Nokia. (2020). 5G RAN: Architecture, Design and Operating Principles. White Paper. In Section 3, "Key 5G RAN technology components," it details how Massive MIMO (which encompasses MU-MIMO and beamforming) and advanced channel coding (contributing to spectral efficiency) are fundamental for achieving 5G's high throughput targets.

2. Dahlman, E., Mildh, G., Parkvall, S., Peisa, J., Sachs, J., Selén, Y., & Sköld, J. (2018). 5G radio access. Academic Press. In Chapter 6, "Key 5G Radio-Access Technologies," the authors describe how multi-antenna transmission (MIMO and beamforming) and higher-order modulation are essential for high data rates. Chapter 10 discusses multi-connectivity as a method to boost user data rates.

3. 3GPP TS 37.340 V17.4.0. (2022-12). Technical Specification Group Radio Access Network; NR; Multi-connectivity; Overall description; Stage 2 (Release 17). Section 4, "Overall architecture and principles," describes how a UE can be configured to utilize radio resources from multiple nodes (e.g., in EN-DC, MR-DC) to increase user throughput.

Traffic Engineering (TE) in transport networks, particularly using technologies like MPLS-TE, provides several key benefits. Its primary function is to optimize the utilization of network resources by steering traffic along paths that may not be the default shortest path chosen by an IGP. This explicit path control, or traffic steering (C), prevents congestion on certain links while others are underutilized, leading to better utilization of network capacity (B). Furthermore, TE significantly enhances resiliency (D) by enabling mechanisms like Fast Reroute (FRR), which pre-establishes backup paths to provide sub-50ms restoration in the event of a link or node failure, ensuring high service availability.

A. Scaling access points is related to the design and expansion of the radio or user access layer, not a direct function or benefit of traffic engineering within the transport network core.

1. Official Vendor Documentation: Nokia, SR OS R19.10.R1 MPLS Configuration Guide, Part Number: 3HE 15680 AAAD TQZZA, Edition 01.

Section: Traffic Engineering Overview: "The main goal of MPLS traffic engineering is to enable constraint-based routing of label switched paths (LSPs) across a network... This allows the network operator to route traffic in order to avoid congestion and make the best use of available bandwidth." (Supports B and C).

Section: MPLS Fast Reroute (FRR): "MPLS Fast Reroute (FRR) provides for the fast rerouting of traffic in the event of a link or node failure in an MPLS network... FRR provides link and node protection for LSPs." (Supports D).

2. Peer-reviewed Academic Publications: Awduche, D., et al. "RSVP-TE: Extensions to RSVP for LSP Tunnels." RFC 3209, December 2001.

Section 1. Introduction: "A primary goal of traffic engineering is to facilitate efficient and reliable network operations... This is accomplished by moving traffic from congested parts of a network to less congested parts." (Supports B and C). The document also discusses establishing backup tunnels for "enhanced resilience." (Supports D).

3. University Courseware: Stanford University, CS 244: Advanced Topics in Networking, Lecture Notes on "Traffic Engineering".

The course materials typically outline the two primary goals of TE as 1) Performance Optimization (improving resource utilization, avoiding congestion) and 2) Resilience (fast recovery from failures). This directly corresponds to options B, C, and D. Traffic steering is the mechanism to achieve optimization.

An End-to-End (E2E) Network Slice is a complete logical network designed to serve a specific business purpose. According to official Nokia documentation and 3GPP standards, an E2E slice is composed of three fundamental segments or sub-slices: the Access Slice (covering the Radio Access Network - RAN), the Core Slice (covering the Core Network - CN), and the Transport Slice (providing connectivity between RAN and CN). The term "Cloud Slice" is not a standard architectural component of an E2E network slice. While core network functions are often deployed on cloud infrastructure, the cloud itself is the underlying platform, not a distinct segment of the slice in the same way as Access, Core, and Transport.

B. Core Slice: This is an essential part of an E2E slice, containing the set of Core Network functions and resources allocated to that specific slice.
C. Access Slice: This is a fundamental component, comprising the Radio Access Network (RAN) functions and resources dedicated to the slice for connecting user equipment.
D. Transport Slice: This is a critical segment that provides the required connectivity and quality of service for traffic between the access and core parts of the slice.

1. Nokia Official Documentation: Nokia 5G E2E Network Slicing Solution, Solution Description. This document outlines the architecture of an E2E slice, explicitly defining its composition from RAN, transport, and core network domains. The architecture diagrams consistently show these three segments as the building blocks. (Note: Specific internal document IDs are proprietary, but this is the standard architectural model presented in Nokia's public-facing technical white papers on the subject).

2. Academic Publication: Afolabi, I., Taleb, T., Samdanis, K., Ksentini, A., & Flinck, H. (2018). Network Slicing and Softwarization: A Survey on Principles, Enabling Technologies, and Solutions. IEEE Communications Surveys & Tutorials, 20(3), 2429-2453. Section III-A, "Network Slice Blueprint," describes the E2E slice as an aggregation of resource segments from the RAN, CN, and transport network domains. DOI: https://doi.org/10.1109/COMST.2018.2815638

3. Nokia White Paper: The path to cloud-native, automated network slicing. This paper details the components required for E2E slicing, stating, "An end-to-end slice consists of a RAN slice, a transport slice and a core slice." Page 4, "E2E slice components."

5G is a foundational technology for Industry 4.0 automation because it uniquely combines three distinct service capabilities in a single network. Ultra-Reliable Low-Latency Communication (URLLC) is paramount for time-critical applications like mobile robot control and closed-loop process automation. Enhanced Mobile Broadband (eMBB) provides the high throughput needed for applications such as video analytics and augmented reality for maintenance. Finally, massive Machine-Type Communications (mMTC) enables the connection of a vast number of sensors for comprehensive monitoring and data collection. Therefore, 5G's role is multifaceted, with a primary focus on low latency for control, complemented by high throughput and massive connectivity for data-driven operations.

A. 5G's role is major, not minor, and its value comes from combining URLLC and eMBB with mMTC, not just focusing on IoT.
B. Focusing solely on high bandwidth neglects the critical requirement of ultra-low latency, which is essential for real-time control in automation.
C. 5G provides the critical wireless connectivity to cloud/edge platforms; the underlying server architecture (e.g., bare metal) is an infrastructure detail, not the primary role of 5G itself.

1. Nokia Official Documentation: In the white paper "5G for industries," Nokia explains that 5G is designed to meet the diverse requirements of Industry 4.0 by supporting three main use case categories. It states, "Ultra-Reliable Low-Latency Communications (URLLC) will provide the sub-millisecond latency and high reliability needed for critical applications... enhanced Mobile Broadband (eMBB)... massive Machine-Type Communications (mMTC)." This directly supports the comprehensive nature of 5G's role as described in the correct answer.

Source: Nokia White Paper, "5G for industries," Page 4, Section: "5G for Industry 4.0".

2. Peer-Reviewed Academic Publication: A study on 5G's role in industrial automation highlights the necessity of all three service types. The authors state, "For Industry 4.0, 5G provides a versatile connectivity fabric. URLLC is the key enabler for time-sensitive networking (TSN) over wireless... At the same time, eMBB supports data-intensive tasks, and mMTC allows for scalable deployment of sensors." This confirms that latency, throughput, and connectivity density are all crucial.

Source: Shafi, M., et al. (2017). "5G: A Tutorial on Network Technology for Future Mobile Communication." IEEE Communications Surveys & Tutorials, 19(4), 2277-2320. Section V.A: "Use Cases and Requirements." DOI: https://doi.org/10.1109/COMST.2017.2710740

3. Peer-Reviewed Academic Publication: Research focusing on smart manufacturing explicitly links the three pillars of 5G to industrial needs. "The requirements of smart manufacturing applications can be mapped to the three generic 5G services: URLLC for closed-loop control and motion control, eMBB for augmented reality and video surveillance, and mMTC for massive sensing and tracking." This reinforces that a combination of characteristics is required.

Source: Z. A. El-Sawy, et al. (2020). "The Industrial Internet of Things (IIoT): A Survey of an Emerging Field." IEEE Communications Surveys & Tutorials, 22(4), 2585-2619. Section IV.C: "5G for IIoT." DOI: https://doi.org/10.1109/COMST.2020.3022647

The main benefit of Cloud Radio Access Network (Cloud RAN or C-RAN) is the reduction in Total Cost of Ownership (TCO). This is achieved by decoupling the Baseband Unit (BBU) from the Remote Radio Head (RRH) and centralizing the BBU processing functions in a data center. This centralization allows for resource pooling and statistical multiplexing, leading to more efficient hardware utilization. Consequently, operators see a reduction in both Capital Expenditures (CAPEX) from fewer required BBUs and simplified cell sites, and Operational Expenditures (OPEX) through lower power consumption, cooling, and simplified site maintenance.

A. Increased cell coverage is primarily a function of the Remote Radio Head's (RRH) power and antenna configuration at the cell site, which is not directly changed by centralizing the baseband processing.
B. Better latency is not a guaranteed benefit. The long-distance fronthaul link between the RRH and the centralized BBU can introduce additional latency, which is a key challenge in C-RAN design.
D. While C-RAN enables advanced features like Coordinated Multi-Point (CoMP) that can increase throughput, this is a secondary performance benefit derived from the architecture, not its primary economic driver.

1. China Mobile Research Institute. (2011). C-RAN: The Road Towards Green RAN. White Paper, Version 2.5.

Section 2, "Key Benefits of C-RAN," page 5: The document explicitly states, "C-RAN can significantly reduce the TCO (Total Cost of Ownership) of the mobile network," detailing reductions in both CAPEX and OPEX as the primary advantages.

2. Checko, A., Christiansen, H. L., Yan, Y., Scolari, L., Kardaras, G., Berger, M. S., & Dittmann, L. (2015). Cloud-RAN for mobile networks—A technology overview. IEEE Communications Surveys & Tutorials, 17(1), 405-426. https://doi.org/10.1109/COMST.2014.2355255

Section III.A, "Reduced CAPEX and OPEX," page 408: This section details how centralization and resource pooling are key advantages of C-RAN, leading to significant cost savings. It notes, "The main motivation for deploying C-RAN is the potential for significant savings in both CAPEX and OPEX."

3. Nokia. (2021). Cloud RAN: A Guide to Deploying with Confidence. White Paper.

Page 4, "Why Cloud RAN?": The paper highlights that "Cloud RAN enables CSPs to lower their total cost of ownership (TCO) by pooling and sharing baseband processing resources from a centralized location." This is presented as a core business driver for adoption.

The Path Computation Engine (PCE) is a core functional component of a Software-Defined Networking (SDN) controller. It is responsible for calculating optimal paths for traffic across the network. The PCE maintains a real-time, comprehensive view of the network topology, resource utilization, and defined policies. When a link or node failure occurs, the SDN controller is notified and invokes the PCE to compute a new, viable alternative path that avoids the point of failure while still adhering to the service's constraints (e.g., latency, bandwidth). This capability is fundamental to enabling automated network resilience and traffic engineering in transport networks.

A. Path Correlation Engine: This is not a standard term for path computation; it suggests a function for analyzing relationships or dependencies between different paths, not calculating them.
B. Alternative Route Finding: This is a generic phrase describing the process or outcome, not the specific name of the standardized functional component that performs the calculation.
C. Alternative Path Computing: Similar to option B, this describes the action being performed but is not the industry-standard term for the SDN engine itself.

1. IETF RFC 4655: A Path Computation Element (PCE)-Based Architecture. Section 1, "Introduction," defines the PCE as "an entity that is capable of computing a network path or route based on a network graph and applying computational constraints." This foundational document establishes the PCE's role in path computation, which includes finding paths for restoration.

2. Nokia Network Services Platform (NSP) Data Sheet. The official data sheet for Nokia's SDN controller platform explicitly states that the NSP includes a "powerful, multi-layer, and multi-vendor Path Computation Element (PCE) for path computation and network optimization across the IP/MPLS and optical layers." This confirms the PCE is the correct Nokia terminology for this function. (Reference: Nokia Network Services Platform Data Sheet, Document ID: SR2007046385EN, 2020).

3. Stallings, W. (2016). Foundations of Modern Networking: SDN, NFV, and Cloud Computing. In Chapter 10, "SDN: Software Defined Networking," the text discusses the architecture of SDN controllers, highlighting that a key application is Traffic Engineering, where a centralized element like a PCE calculates optimal paths based on global network state, including for rerouting during failures. (Pearson Education, Inc.).

The statement presents a false analogy. The NFV Orchestrator (NFVO) and Software-Defined Networking (SDN) Controller operate at different architectural layers and fulfill distinct functions. The NFVO is a service-level orchestrator within the ETSI NFV MANO framework, responsible for the end-to-end lifecycle management of Network Services (NS). It orchestrates resources across multiple domains. In contrast, an SDN Controller is an infrastructure-level controller that directly manages and programs the data plane of the transport network. A more accurate analogy would be: "The Virtualized Infrastructure Manager (VIM) is to Cloud what the SDN Controller is to Transport," as both are responsible for managing their respective infrastructure resources.

B. True: This option is incorrect because it creates a false equivalence. The NFVO orchestrates services that run on the cloud, whereas an SDN controller directly manages the infrastructure of the transport network. Their roles are not parallel.

1. ETSI GS NFV-MAN 001 V1.1.1 (2014-12), "Network Functions Virtualisation (NFV); Management and Orchestration."

Section 5.2.2 (NFV Orchestrator): Defines the NFVO's role as being "responsible for the orchestration and management of NFVI resources... and the lifecycle management of Network Services (NS)." This highlights its service-level focus.

Section 5.4.2 (Virtualized Infrastructure Manager): Describes the VIM as "responsible for controlling and managing the NFVI compute, storage and network resources." The SDN controller's function of managing the network fabric aligns with this infrastructure management layer, often working in conjunction with or as part of the VIM. The architectural diagrams (e.g., Figure 4) clearly place the NFVO a layer above the VIM and the underlying infrastructure that an SDN controller would manage.

2. Nokia, "Cloud-native network operations for the 5G era" (White Paper).

This document distinguishes between service orchestration and domain-specific control. It explains that end-to-end service orchestration (the NFVO's role) coordinates actions across different technology domains, such as the cloud (data center) and the transport network. The SDN controller is presented as a domain controller for the transport network, operating at a lower, more specific level than the cross-domain service orchestrator.

3. Stallings, W. (2016). Foundations of Modern Networking: SDN, NFV, QoE, IoT, and Cloud. Pearson Education, Inc.

Chapter 7, "Network Functions Virtualization: Concepts and Architecture": This academic text clarifies the NFV MANO architecture, explaining that the NFVO manages the NS lifecycle by issuing requests to the VIM for infrastructure resources. It separately describes SDN controllers as managing the network fabric, reinforcing the distinction between service orchestration (NFVO) and infrastructure control (SDN).

The 5G Flexible RAN, also known as Cloud RAN (C-RAN) or Virtualized RAN (vRAN), is based on the disaggregation of the base station (gNB). This architecture splits the baseband processing functions into a Centralized Unit (CU) and a Distributed Unit (DU). The Radio Unit (RU) remains at the cell site to handle radio frequency (RF) transmission and reception. These three components—CU, DU, and RU—are the fundamental building blocks of the flexible RAN architecture as defined by standards bodies like 3GPP. An "Optical Unit" is not a standardized functional component within this architectural model, although optical fiber is the common transport medium for fronthaul and midhaul links connecting these components.

A. Radio Unit: The Radio Unit (RU) is a core component of the 5G RAN, responsible for handling the radio frequency (RF) functions at the antenna site.
B. Distributed Unit: The Distributed Unit (DU) is a key component in the disaggregated architecture, processing the real-time, lower-layer baseband functions.
C. Centralized Unit: The Centralized Unit (CU) is a key component that runs the non-real-time, higher-layer protocol stack and can be located centrally. ---

1. Nokia Official Documentation: Nokia. (2021). Cloud RAN: A Guide for Operators. White Paper. In Section "Cloud RAN architecture," the document details the functional split into Centralized Unit (CU), Distributed Unit (DU), and Radio Unit (RU), establishing them as the core components. It does not mention an "Optical Unit" as a functional block. (Specific document available via Nokia channels for partners and customers).

2. Standards Body Publication: 3GPP TS 38.401 V17.3.0 (2022-03). NG-RAN; Architecture description. Section 4.2, "NG-RAN Architecture," and Figure 4.2.2-1 explicitly define the gNB architecture and its potential split into a gNB-CU and one or more gNB-DUs. The RU is implicitly part of the physical layer handled by the DU.

3. Academic Publication: Polese, M., Jana, R., & Zorzi, M. (2017). A Survey on 5G Network Architecture and Its Technology Enablers. IEEE Communications Surveys & Tutorials, 19(4), 2541-2575. In Section IV-A, "Cloud-RAN," the paper describes the C-RAN architecture as comprising three main components: the BaseBand Unit (BBU) pool (which is further split into CU/DU in 5G), the Remote Radio Head (RRH) or RU, and the fronthaul transport network. It confirms RU, DU, and CU as the standard architectural elements. DOI: https://doi.org/10.1109/COMST.2017.2720758