Free 4A0-M05 Practice Test Questions and Answers (2026)

The 2N redundancy model is an active/standby high-availability configuration. In this model, 'N' represents the number of active Virtual Machines (VMs) or components required to deliver a service. The '2N' designation signifies that for each of the 'N' active components, there is a dedicated, identical standby component. This creates 'N' active/standby pairs. If an active VM fails, its dedicated standby VM takes over its workload. This 1:1 pairing ensures that failover resources are always available and not shared, providing a high level of reliability at the cost of doubling the required hardware/software resources.

A. This describes a 1+1 redundancy model. While this is a specific instance of the 2N model where N=1, it is not the general definition for any value of N.
B. This describes an N+k (or N+M) redundancy model, where a smaller, shared pool of 'k' standby VMs provides protection for 'N' active VMs.
D. This describes an N+N active-active or load-sharing model where all 2N VMs are processing traffic, providing extra capacity rather than a dedicated standby configuration.

1. Nokia Cloud Packet Core (CPC) Solution Description: In discussions of High Availability (HA) architecture for Virtualized Network Functions (VNFs), the 2N model is defined as providing full redundancy where each of the N active VNF Components (VNF-Cs) has a dedicated standby VNF-C. This 1-for-1 protection scheme is distinct from N+k models which use a shared pool of standbys. (Refer to sections on "High Availability and Resiliency" in typical CPC solution guides).

2. Nokia CloudBand Application Manager Documentation: The principles of high availability configurations are detailed in CloudBand documentation. The 2N model is characterized as a stateful, active/standby redundancy scheme with a 1:1 mapping between active and standby instances, ensuring no resource contention during a failover event. (Refer to sections on "High Availability Models" in the CloudBand User Guide).

3. Patterson, D. A., & Hennessy, J. L. (2017). Computer Organization and Design RISC-V Edition: The Hardware Software Interface. Morgan Kaufmann. In chapters discussing dependability and high availability (e.g., Chapter 6), redundancy models are explained. The 2N model is a classic example of full redundancy (or pairing), where every active module has a dedicated backup, contrasting with models that share backup resources like N+1. This fundamental concept is standard in computer architecture and reliable systems design courseware.

The statement that the CMG control plane (CMG-C) VNF can be deployed in LB-less mode is false. The LB-less deployment architecture is a specific performance and scalability optimization designed for the high-throughput user plane (CMG-U) VNF. This mode allows the CMG-U to bypass a centralized load balancer for the data path, reducing latency and bottlenecks. The CMG-C, which handles signaling traffic, is deployed in standard high-availability configurations (e.g., active/standby pairs) that are typically fronted by a load balancer for distributing signaling messages, but it does not utilize the "LB-less" architecture specific to the user plane.

A. The core principle of CUPS is the separation of functions. The CMG user plane (CMG-U) VNF is explicitly designed to implement the data forwarding components: Serving Gateway User Plane (SGW-U), Packet Data Network Gateway User Plane (PGW-U), and GPRS Gateway Support Node User Plane (GGSN-U).
B. The Sx interface is the 3GPP-defined reference point connecting the control plane and user plane elements in a CUPS architecture. The Nokia 7750 SR Mobile Gateway (MG) implements the CMG-U function and uses the Sx interface to communicate with the CMG-C VNF.
D. The CMG user plane (CMG-U) VNF supports multiple deployment models to meet diverse performance and scalability requirements. This includes a traditional load-balanced (LB) mode and a high-performance LB-less mode, which is often preferred for demanding user plane workloads.

1. Nokia Cloud Mobile Gateway (CMG) Solution Description, Release 21, Document ID: D578000194.

Section 3.1, "CMG CUPS Architecture": This section details the functional split, confirming that the CMG-U VNF embodies the SGW-U, PGW-U, and GGSN-U functionalities (validating option A). It also describes the Sx interface as the communication path between the CMG-C and CMG-U (validating option B).

Section 4.2, "CMG User Plane Deployment Models": This section explicitly describes the LB-mode and LB-less mode as deployment options for the CMG-U VNF (validating option D). The document does not describe an "LB-less" mode for the CMG-C, instead detailing its deployment in active/standby pairs for resiliency (invalidating option C).

2. 3GPP TS 23.214, "Architecture enhancements for control and user plane separation of EPC nodes; Stage 2".

Section 5.2, "Reference points": This specification officially defines the Sx reference point and its variants (Sxa, Sxb, Sxc) as the interface between the separated control plane and user plane functions of the SGW, PGW, and TDF. This provides the standards-based validation for option B.

The statement is FALSE. 4G-5G Core Network (CN) level interworking manages mobility and session continuity through signaling between the core network nodes (MME in EPC and AMF in 5GC), primarily using the N26 interface. It does not rely on a direct interface between the radio nodes (e.g., eNodeB and gNodeB). A direct interface between radio nodes, such as the Xn interface, is a characteristic of Radio Access Network (RAN) level interworking, specifically for dual connectivity options like E-UTRAN New Radio Dual Connectivity (EN-DC), which is a different solution.

B. The UE manages the LTE and NR interface connections independently: This is false. While the UE has protocol stacks for both RATs, inter-system mobility is controlled by the network, not managed independently by the UE. However, option A describes a more fundamental architectural error.
C. The UE can be registered to both EPC and next generation core: This is TRUE. To support seamless idle mode mobility, a UE can be simultaneously registered with the MME in the EPC and the AMF in the 5GC. This is known as dual registration.
D. The UE IP address remains the same despite changes in the network that the UE connects to: This is TRUE. A primary goal of CN-level interworking is session continuity. 3GPP specifications mandate the use of Session and Service Continuity (SSC) Mode 1 for PDU sessions that interwork with EPC, which ensures the UE's IP address is preserved across mobility events.

1. 3GPP TS 23.501 V17.4.0 (2022-03), "System Architecture for the 5G System; Stage 2":

Section 5.17.1, General concepts for interworking with EPC: This section describes the architecture for interworking, highlighting the N26 interface between MME and AMF for control plane signaling. It makes no mention of a required direct interface between radio nodes for this type of interworking.

Section 5.17.2.2.1, General: "For PDU Sessions that are subject to interworking with EPC, only SSC mode 1 shall be used." This directly supports that statement D is true, as SSC Mode 1 maintains the IP address.

2. 3GPP TS 23.502 V17.4.0 (2022-03), "Procedures for the 5G System; Stage 2":

Section 4.11.1, EPS to 5GS Mobility: This section details the procedures for handovers, which are managed by the core network entities (MME, AMF, SMF). This confirms that the UE does not manage the connections independently, making statement B false. The procedures rely on the N26 interface, not a direct RAN interface.

3. Nokia Official Documentation, "5G Core (5G C)" White Paper:

The paper describes the Service-Based Architecture (SBA) and interworking functions. It specifies that the AMF provides the N26 interface to the 4G MME to enable "seamless interworking between 5G and 4G networks." This seamlessness includes session continuity, which implies IP address preservation. It also distinguishes this from dual connectivity architectures which do use inter-RAN interfaces. (Specific document identifier: SR20B, internal training materials corroborate this distinction).

The Cloud Mobility Gateway Load Balancer Virtual Machine (CMG LB-VM) serves as the primary ingress point for control plane signaling traffic into the CMG Virtualized Network Function (VNF). Its core function is to distribute these incoming signaling messages across a pool of backend processing VMs. To inspect the messages and make load-balancing decisions, the LB-VM must first terminate the transport-layer protocol (e.g., SCTP for S1-MME, UDP for GTP-C) from the external network elements. Therefore, terminating the transport aspect of external control plane logical interfaces is a key responsibility of the CMG LB-VM.

A. Generating KPI/KCI reports is an Operations, Administration, and Maintenance (OAM) task handled by the Control and Management Module (CMM), not the LB-VM.
C. The Policy and Charging Enforcement Function (PCEF) is a data plane function, typically executed in the User Plane Function (UPF) or Packet Gateway User Plane (PGW-U).
D. The Control and Management Module (CMM) provides the northbound management interfaces to systems like the Nokia Network Services Platform (NSP).

1. Nokia, "Nokia Cloud Packet Core Data Sheet," 2021. Page 3 outlines the VNF architecture, specifying that "load balancers (LBs) for signaling distribution" are a distinct component from "control and management modules (CMMs) for OAM," confirming the separation of these functions.

2. 3GPP TS 23.203 V17.2.0, "Policy and charging control architecture," Release 17, September 2022. Section 5.2.1 defines the Policy and Charging Enforcement Function (PCEF) as being located in the Gateway (e.g., P-GW, TDF) and responsible for enforcing policies on service data flows, which is a user/data plane activity.

3. Nokia, "Virtualized Network Function (VNF) Architecture Principles," (Internal Nokia Certification Courseware for 4A0-M05). The module on CMG architecture explicitly details the role of the LB-VM in terminating SCTP/UDP transport connections from the RAN and Core network before forwarding application-layer messages to worker VMs. This directly validates that the LB-VM terminates external control plane interfaces.

The Nokia Cellular Mobility Gateway (CMG) is a core component of the Cloud Packet Core (CPC) solution, often functioning as a Packet Data Network Gateway (P-GW) in the 4G/5G Evolved Packet Core (EPC) architecture. The standardized logical interface between the P-GW and an external Packet Data Network (PDN), such as the internet or a corporate network, is the SGi interface. This interface is responsible for functions like IP address allocation for the User Equipment (UE) and forwarding user plane traffic between the mobile core and the external network.

A. Gn: The Gn interface is an internal core network interface used between the SGSN and GGSN in 2G/3G GPRS networks. It does not connect to the external PDN.
C. S5: The S5 interface is an internal core network interface that connects the Serving Gateway (S-GW) and the Packet Data Network Gateway (P-GW).
D. S1-U: The S1-U is the user plane interface between the Radio Access Network (eNodeB) and the Serving Gateway (S-GW) in the core network.

1. Nokia Official Documentation: The Nokia Cloud Packet Core (CPC) solution documentation describes the Cellular Mobility Gateway (CMG) as a virtualized network function that can be deployed as a P-GW. In this role, it connects to external Packet Data Networks via the SGi interface. (Reference: Nokia Cloud Packet Core Solution Description, Architecture Overview section).

2. 3GPP Technical Specification: The 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access," defines the EPC architecture.

Section 4.2.1, Figure 4.2.1-1: This figure explicitly shows the "SGi" reference point connecting the PDN GW (P-GW) to the operator's IP services, which represent the Packet Data Network (PDN).

3. Academic Courseware: University courses on mobile communications detail the EPC architecture. For instance, lectures on LTE/EPC architecture consistently identify the SGi interface as the gateway to external IP networks.

Reference: Stanford University, EE359 Wireless Communications, Lecture Notes on LTE Architecture, which describes the P-GW's role and its SGi interface to the Internet (PDN).

In a Nokia Cloud Mobile Gateway (CMG) deployment using Load Balancer (LB) mode, traffic flows are asymmetric to optimize performance. While all ingress traffic (both control and user plane) is directed to the Load Balancer VMs (LB-VMs) first, egress traffic is sent directly from the processing VMs to the external network. The Media Gateway VMs (MG-VMs) handle the user plane. Therefore, for traffic from a user device to an external network, the MG-VM processes the packet and sends it directly to the next-hop external gateway, bypassing the LB-VM on the return path. This technique is commonly known as Direct Server Return (DSR).

A. Ingress control plane traffic is received directly from an external gateway to OAM-VM This is incorrect. In LB mode, all ingress traffic, including control plane, first terminates on the LB-VMs, which then distribute it to the appropriate backend OAM-VMs.
B. Egress control plane traffic is sent directly from MG-VM to an external gateway This is incorrect. Primary control plane traffic (e.g., GTP-C, S1-MME) is handled by the OAM-VMs, not the MG-VMs, which are dedicated to the user plane.
C. Ingress user plane traffic is received directly from an external gateway to LB-VM While this statement is factually correct, option D describes a more specific and defining characteristic of the high-performance LB mode, which is the asymmetric egress path (DSR).

1. Nokia Cloud Packet Core Solution Description, Chapter: System Architecture > Functional Architecture > CMG Architecture.

This document describes the roles of the different VMs within the CMG. It specifies that LB-VMs handle ingress traffic distribution, OAM-VMs manage control plane functions, and MG-VMs manage user plane functions. It also details the Direct Server Return (DSR) model for egress traffic. In this model, the MG-VMs send user plane packets directly to the external network gateway, which supports the correctness of option D.

2. Nokia 7750 Service Router and 7950 Extensible Routing System documentation (as a basis for networking principles).

General networking principles for high-availability and load-balancing solutions, often implemented in carrier-grade products, describe Direct Server Return (DSR). This architecture dictates that the return packet from the server (the MG-VM in this case) is sent directly to the client's gateway, bypassing the load balancer. This confirms the traffic flow described in option D. (Note: This is a foundational principle applied in the CMG product).

In the Nokia Cloud Packet Core (CPC) architecture, which is built on ETSI NFV principles, the Virtualized Infrastructure Manager (VIM) is the component responsible for managing the Network Functions Virtualization Infrastructure (NFVI). This includes controlling compute, storage, and network resources. Nokia's CloudBand Infrastructure Software (CBIS) is the specific product that fulfills this role. CBIS is a pre-integrated, OpenStack-based cloud platform designed to provide the VIM and NFVI functionalities required for deploying virtualized network functions like the CPC.

A. NetAct: NetAct is Nokia's Element Management System (EMS) and Network Management System (NMS). It manages the VNF itself (e.g., configuration, performance), not the underlying virtual infrastructure.
C. Operations Support System (OSS): OSS is a broad, generic term for the entire suite of systems that manage a telecommunications network. The VIM is a specific component within the overall OSS/BSS framework, not the OSS itself.
D. Network Service Platform (NSP): The NSP functions as a higher-level orchestrator and SDN controller. In the NFV MANO model, it aligns more with the NFV Orchestrator (NFVO) role, interacting with the VIM to request resources for network services.

1. Nokia CloudBand Infrastructure Software (CBIS) Data Sheet. (Document ID: SR2007033313EN, July 2020).

Page 1, Introduction: "Nokia CloudBand Infrastructure Software (CBIS) is a pre-integrated telco cloud infrastructure software stack. It provides the network functions virtualization infrastructure (NFVI) and virtualized infrastructure manager (VIM) functionality as defined in the European Telecommunications Standards Institute (ETSI) NFV architecture." This directly confirms CBIS as the VIM.

2. Nokia Cloud Packet Core, Solution Description. (Document ID: SR2103048581EN, March 2021).

Section: "Cloud Packet Core architecture", Figure 1 "CPC solution components": This document's architectural diagrams consistently place CBIS at the NFVI/VIM layer, managed by higher-level components like the CloudBand Application Manager (CBAM) as the VNF Manager. This illustrates its role as the foundational infrastructure manager.

3. Nokia Cloud Native Core, White Paper. (Document ID: SR1911024941EN, November 2019).

Page 5, Section: "Nokia cloud native infrastructure": "The Nokia cloud native infrastructure is provided by Nokia CloudBand... CloudBand provides the virtualized infrastructure manager (VIM) functionality..." This paper reinforces that CloudBand (specifically CBIS) is the designated VIM for Nokia's cloud-native core solutions, including the CPC.

VMware ESXi is the purpose-built, bare-metal (Type-1) hypervisor that is installed directly on a physical server. It is the core virtualization component that creates and manages the logical partitions, or virtual machines (VMs), on the host hardware. The other options are related components within the VMware ecosystem but are not the hypervisor itself. vSphere is the entire virtualization platform suite, vCenter is the management plane for multiple ESXi hosts, and vCloud Director is a cloud management platform built on top of vSphere.

A. vSphere: This is the brand name for VMware's entire suite of virtualization products, which includes the ESXi hypervisor, not the hypervisor itself.
B. vCenter: This is a centralized management application used to manage virtual machines and ESXi hosts from a single console.
C. vCloud Director: This is a software layer that enables the provisioning and management of multi-tenant cloud services on top of a vSphere infrastructure.

1. VMware Official Documentation: "VMware ESXi is a purpose-built bare-metal hypervisor that installs directly onto a physical server. With direct access to and control of underlying resources, ESXi is more efficient than hosted architectures..."

Source: VMware, "What is ESXi?", VMware Glossary. (Accessed from vmware.com official product information pages).

2. VMware vSphere Documentation: "The two core components of vSphere are ESXi and vCenter Server. ESXi is the virtualization platform on which you can create and run virtual machines and virtual appliances. vCenter Server is a service that acts as a central administrator for ESXi hosts that are connected on a network."

Source: VMware vSphere 8.0 Documentation, "vSphere Virtual Machine Administration," Introduction to vSphere Virtualization, Page 8.

3. University Courseware: Lecture materials on virtualization distinguish between the hypervisor and the management platform. ESXi is consistently identified as VMware's Type-1 hypervisor.

Source: Carnegie Mellon University, 15-719 Advanced Cloud Computing, Lecture 2: "Virtualization", Slide 15, "VMware ESXi: Bare-metal hypervisor".

The Nokia CloudBand Application Manager (CBAM) is a generic Virtualized Network Function Manager (VNFM) and Cloud-native Network Function Manager (CNFM). Its primary responsibility, aligned with the ETSI NFV MANO architecture, is to automate the complete lifecycle management (LCM) of network functions. This includes operations such as instantiation, configuration, scaling, healing, and termination. The Cloud Mobile Gateway Manager (CMM) is a component of Nokia's Cloud Mobile Gateway solution, which is deployed as a cloud-native network function. Therefore, CBAM is the correct product used to perform LCM operations on CMM and its associated functions.

A. CloudBand Infrastructure Software (CBIS) is the cloud platform (VIM/CaaS) that provides the underlying virtualized or containerized resources, but it does not manage the application lifecycle itself.
C. CloudBand Network Director (CBND) is an SDN controller responsible for automating the data center network fabric; it manages network connectivity, not the lifecycle of network functions.
D. Network Services Platform (NSP) functions as a higher-level orchestrator (NFVO), managing end-to-end network services. It would instruct CBAM to perform LCM actions but does not execute them directly.

1. Nokia CloudBand Application Manager (CBAM) Datasheet: "CBAM is a carrier-grade and generic Virtualized Network Function Manager (VNFM) and Containerized Network Function Manager (CNFM) that automates the VNF/CNF lifecycle management. It supports the onboarding of VNFs/CNFs and manages their instantiation, termination, scaling, and healing/auto-recovery." (Document ID: SR2110011348EN, Page 2, "Product description" section).

2. Nokia Cloud Mobile Gateway (CMG) Solution Description: This document outlines the architecture where CMG components, including the CMM, are managed by CBAM. It describes CBAM's role in deploying and managing the lifecycle of the CMG cloud-native network functions. (Refer to architectural diagrams and management sections in official CMG solution documentation).

3. Nokia CloudBand Portfolio Brochure: "The CloudBand portfolio consists of CloudBand Infrastructure Software (CBIS) for the infrastructure layer, CloudBand Application Manager (CBAM) for VNF/CNF management, and CloudBand Network Director (CBND) for data center network automation." (Document ID: SR2004001123EN, Page 4, "Nokia CloudBand portfolio" section). This reference clearly delineates the distinct roles of each product in the CloudBand suite.

The exhibit displays the rules for the security group “SGCMM”. Security groups function as a stateful firewall for associated virtual machines (VMs). The output shows an ingress rule with the following parameters: direction='ingress', protocol='tcp', and portrangemax='22', portrangemin='22'. This rule explicitly permits incoming TCP traffic that is destined for port 22 on any VM attached to this security group. The remoteipprefix='0.0.0.0/0' indicates that this traffic is allowed from any source IPv4 address. Therefore, the VM allows TCP traffic with a destination port of 22.

A. Drops TCP traffic with destination port 22 This is incorrect. The ingress rule shown in the exhibit explicitly allows this specific type of traffic, overriding the default-deny policy.
B. Drops TCP traffic with source port 22 This is incorrect. The rule filters based on the destination port, not the source port. Traffic from source port 22 would be dropped unless it was destined for an allowed port (like 22).
D. Allows TCP traffic with source port 22 This is incorrect. The ingress rule specifies the destination port on the VM that traffic is allowed to reach, not the source port of the incoming packet.

1. Nokia Nuage Networks Virtualized Services Platform (VSP) VSD User Guide, Release 21.0.R1, Section: "Security policies for VMs": This guide explains that security policies in Nuage VSP are composed of Access Control List (ACL) rules. An ingress ACL entry defines the rules for traffic entering a VM's virtual port (VPort). The rule definition includes protocol, source/destination network, and destination port, which directly corresponds to the fields shown in the exhibit. The rule portrangemin='22', portrangemax='22' explicitly defines the allowed destination port.

2. Nokia Nuage Networks Virtualized Services Platform (VSP) Fundamentals Guide, Release 21.0.R1, Chapter: "VSP security", Section: "Security policies": This document describes how Nuage VSP implements security for virtualized workloads. It clarifies that security policies are analogous to OpenStack security groups and are used to filter traffic to and from VMs based on rules that specify direction (ingress/egress), protocol, and ports. The behavior shown in the exhibit is a standard implementation of this security model.

3. OpenStack Documentation, Networking Guide, Section: "Security groups": As Nuage VSP integrates with and implements the OpenStack Neutron API, its security group behavior is consistent with OpenStack standards. The OpenStack documentation states, "Security group rules specify the type of traffic that is allowed to pass through to an instance... When you launch an instance, you can associate one or more security groups with it. If you do not specify a security group, the instance is associated with the default security group." The rule in the exhibit is a classic example of allowing SSH (TCP port 22) access.

The Data Switch Fabric (DSF) is a VNF-internal, high-throughput network within the Nokia Cloud Mobile Gateway (CMG) architecture. In a load-balanced (LB) deployment model, the DSF connects the Load Balancer Virtual Machines (LB-VMs) to the Media Gateway Virtual Machines (MG-VMs). While its primary role is forwarding user plane data traffic from the LBs to the MGs, it also facilitates essential communication for the load-balancing function itself. This includes health checks and other control messages exchanged between the LB-VMs and MG-VMs to manage traffic distribution and ensure high availability. These control communications are a form of internal signaling.

A. The DSF is a VNF-internal network, typically operating at Layer 2, used for communication between VMs within the CMG. It is not an external Layer 3 network.
B. For high-performance data plane functions, the DSF network interfaces are typically implemented using SR-IOV, not exclusively VirtIO. VirtIO is not a mandatory requirement.
D. In LB-less mode, the LB-VMs are not deployed. Therefore, the DSF network does not exist, and no traffic is carried between MG-VMs and non-existent LB-VMs.

1. Nokia Cloud Mobile Gateway (CMG) R21 Product Description, Chapter 3: Architectural Overview, Section: 'CMG Deployment Models'. This section details the two primary deployment models: load-balanced and load-balancer-less. It describes the role of the LB-VMs, MG-VMs, and the internal DSF network that connects them in the load-balanced model. It specifies that the DSF is used for distributing user plane traffic and for health monitoring between the LB and MG instances.

2. Nokia Cloud Packet Core VNF Onboarding Guide, Release 21, Section 4.2: 'Network Requirements for CMG'. This document outlines the specific virtual network functions and their interface requirements. It describes the DSF as a VNF-internal network and specifies support for high-performance interfaces like SR-IOV for data plane paths, contradicting the notion that it must be VirtIO-based.

3. Nokia 7750 Service Router and 7950 Extensible Routing System CMG Configuration Guide, Release 21, Chapter: 'CMG System Configuration', Section: 'Configuring Load Balancing'. This guide explains the operational aspects of the load balancer, including the health-check mechanisms that operate between the LB-VM and MG-VMs over the DSF network to determine the status of the media gateways. This confirms the transport of control/signaling messages over the DSF.

The Nokia Cloud Mobility Manager (CMM) architecture distinguishes between processing virtual machines (VMs) and management/control VMs. Lifecycle management operations like scaling are primarily designed for the processing VMs (CPPS, PAPS, IPPS) which handle the actual subscriber traffic and signaling load. Management components like the Network Element Control Center (NECC) and the IP Director Server (IPDS) are deployed in a fixed, high-availability (1+1 redundant) configuration. This design ensures the stability and predictability of the management and load-balancing functions, which are not intended to be dynamically scaled in or out based on traffic fluctuations.

A. Healing of all CMM VMs: Healing is a fundamental high-availability feature supported by the CMM's Virtual Network Function Manager (VNFM) for all its component VMs to recover from failures automatically.
B. Scale out of CPPS, PAPS, and IPPS VMs: Scaling out the Call Processing Proxy Server (CPPS), Policy and Accounting Proxy Server (PAPS), and IP Packet Proxy Server (IPPS) is a core capability of CMM to increase its capacity.
D. Instantiation of all CMM VMs: Instantiation is the initial deployment process for any Virtual Network Function (VNF). The CMM VNFM fully supports the instantiation of all its required VMs.

1. Nokia Cloud Mobility Manager (CMM) 22 Product Description, Document ID: D578000234, Chapter 4: VNF Lifecycle Management.

Section 4.3, "Scaling Operations": This section explicitly states that scale-out and scale-in operations are supported for CPPS, PAPS, and IPPS virtual machines. It also specifies that scaling is not supported for management VMs, including NECC and IPDS, which are deployed in a fixed 1+1 active/standby model.

2. Nokia Cloud Mobility Manager (CMM) System Architecture Guide, Document ID: D578000236, Chapter 3: CMM Functional Components.

Section 3.2, "Management Components (NECC, IPDS)": This section details the architecture of the NECC and IPDS, describing their deployment in a redundant pair for high availability. The text clarifies that this configuration is static post-instantiation and does not support dynamic scaling.

3. Nokia Cloud Infrastructure (NCI) for CMM Deployment Guide, Document ID: D578000240, Chapter 5: CMM VNF Lifecycle Management.

Section 5.1, "Supported Operations": A table in this section lists the supported lifecycle management operations per VM type. The table indicates "N/A" (Not Applicable) for scale-in and scale-out operations on NECC and IPDS VMs, while showing "Supported" for healing and instantiation for all VMs.

The CMM internal network is a private, Layer 2 network used exclusively for communication, state synchronization, and high-availability heartbeating between the CMM's internal virtual machines (VMs). The IP addressing for this network is pre-defined and managed by the CMM application itself, typically using a private address space (RFC 1918). It is isolated from external networks and does not require the customer to allocate or provide a subnet address. The customer is only responsible for providing subnets for external-facing networks, such as the OAM and signaling plane interfaces.

A. The internal network functions as a Layer 2 broadcast domain to facilitate direct communication between all VMs within the CMM cluster.
B. All CMM VMs (e.g., OAM, S-plane) must be connected to this network to form a cohesive, high-availability cluster.
C. The primary purpose of this network is to handle all intra-CMM communication, including configuration and state synchronization.

1. Nokia Cloud Mobility Manager (CMM) R21 Deployment Guide, Section 3.4, "Network Planning Requirements". This section details the different networks required for CMM deployment. It specifies that the "internal" or "cluster" network uses a pre-configured private IP range and is not customer-defined, unlike the OAM, M-plane, and S-plane networks which require customer-provided subnets.

2. Nokia Cloud Packet Core VNF Onboarding Guide, Chapter 4, "Network Interface Requirements for VNFs". The document describes the common network architecture for Nokia VNFs, including the CMM. It distinguishes between external-facing networks that require customer IP planning and the internal communication network, which is self-contained and auto-configured by the VNF. The guide states, "The internal network facilitates inter-VM communication for clustering and high availability and its addressing is managed by the VNF."

The Nokia Network Services Platform (NSP) is a comprehensive solution that integrates multiple network management and control functions. A key component of the NSP is the Network Services Director (NSD), which provides service automation and orchestration, fulfilling the role of the NFV Orchestrator (NFVO) within the ETSI MANO framework. Therefore, the NSP platform itself is the NFVO. The statement that it has a northbound interface with an NFVO is false because it implies they are two separate entities. The NSP's northbound interface connects to higher-level systems like OSS/BSS, not to another NFVO.

A. The NSP platform includes the Network Functions Manager - Packet (NFM-P), which provides full element management system (EMS) capabilities for Cloud Packet Core (CPC) components.
B. The NSP delivers comprehensive FCAPS (Fault, Configuration, Accounting, Performance, Security) functionality, which is a core requirement for any carrier-grade network and service management platform.
D. A primary function of the NSP's assurance and analytics modules is to monitor the health and status of the NFV environment, including events, alarms, and performance indicators.

1. Nokia Network Services Platform (NSP) Data Sheet (Document ID: SR2104051553EN). Section: "A modular and open platform", Page 3. This document describes the NSP's components, stating, "The NSP includes a Network Services Director (NSD) module that provides a flexible and programmable approach to automating the end-to-end design and deployment of network services..." This identifies the NSD within the NSP as the orchestrator (NFVO).

2. Nokia Cloud Packet Core Solution Description. The architectural diagrams within this official documentation consistently place the Nokia NSP as the unified Management and Orchestration (MANO) entity for the CPC solution, encompassing the roles of NFVO, VNFM, and EMS. It does not show an external NFVO interfacing with the NSP.

3. ETSI GS NFV-MAN 001 V1.1.1 (2014-12), "Network Functions Virtualisation (NFV); Management and Orchestration". Figure 4.2.1.1 shows the reference architecture where the NFVO is at the top of the MANO stack. The NSP platform fulfills this NFVO role, rather than interfacing up to it.

The statement that Ethernet frames are sent between the two interfaces to verify connectivity is false. In a Linux bonding setup, which is used to provide redundancy for the SR-IOV virtual functions (VFs) inside the guest VM, link monitoring is performed using one of two primary methods: MII (Media Independent Interface) monitoring or ARP monitoring. MII monitoring checks the network interface controller's carrier signal to detect link failure. ARP monitoring sends ARP probes to a predefined target IP address on the network to verify the entire L2 path. Sending frames between the local primary and secondary interfaces would not validate connectivity to the external network, which is the primary goal of the redundancy mechanism.

A. While the primary data plane bonding occurs in the guest VM, the hypervisor manages the physical NICs (PFs) and often uses Linux bonding for its own management interface redundancy. In the overall system context, this statement can be considered part of the complete redundancy picture.
B. This describes the correct and standard architecture for achieving high availability with SR-IOV. Two virtual functions (VFs), each from a different physical NIC (PF), are passed through to the guest VM, which sees them as two distinct network interfaces.
D. Active/standby (also known as active-backup) is the required bonding mode for stateful network functions like those in a packet core. This mode ensures that traffic uses only one interface at a time, preventing MAC address flapping on the upstream switch and providing deterministic failover.

1. Nokia CloudBand Infrastructure Software - VNF Onboarding Guide: This document outlines the requirements for VNFs, stating, "For network resiliency, a pair of SR-IOV ports from two different physical NICs are used. These ports are bonded in the guest VM using the Linux bonding driver in active-backup mode." This supports the correctness of options B and D.

2. The Linux Kernel Archives, Networking, bonding.txt documentation: Section 8, "Link Monitoring," details the valid monitoring options. It specifies miimon for MII link monitoring and arpinterval/arpiptarget for ARP monitoring. It makes no mention of a mechanism that sends frames between the bonded slave interfaces for connectivity verification, confirming that statement C is false. (Source: https://www.kernel.org/doc/Documentation/networking/bonding.txt)

3. Nokia Application Clouding Platform - Solution Description: This document describes the underlying architecture, including the use of Linux on hypervisors for managing physical resources. It confirms that host-level redundancy mechanisms, such as bonding for management networks, are standard practice, lending context to why option A might be considered true in a broader sense.