Which of the following statements regarding CMM scaling is FALSE?

The statement that is false is A. The Packet Acceleration and Processing Service (PAPS) is a high-availability, redundant component within the Nokia Cloud Mobility Manager (CMM) architecture. It is deployed in 1+1 redundant pairs to ensure service continuity. Consequently, scaling operations, both scaling in (removing VMs) and scaling out (adding VMs), must be performed in steps of a pair (two VMs) at a time. Scaling by a single VM would break the redundancy model and is not a supported operation.

B. CPPS VMs and DBS VMs can scale independently. This is correct. The Control Plane Processing Service (CPPS) and Database Service (DBS) handle different functions (signaling vs. data storage) and can be scaled independently to meet varying network load profiles.
C. DBS VMs can scale out in steps of a single VM. This is correct. The CMM Database Service is designed for granular scalability, allowing administrators to add single VM instances to the cluster to incrementally increase database capacity and performance.
D. IPPS VMs can scale out in steps of a single VM. This is correct. The IP Packet Processing Service (IPPS), which handles user plane traffic, is designed to scale out by adding single VM instances, allowing for flexible and efficient capacity adjustments based on traffic demand.

1. Nokia Cloud Packet Core Solution Description, Document Version 22.R1, Section: "Cloud Mobility Manager" and "Elasticity".

This document details the architecture of the CMM Virtual Network Function (VNF). It specifies that the PAPS VNFC (VNF Component) is deployed in pairs for redundancy. The section on elasticity and scaling explicitly states that PAPS VMs are added or removed in pairs, while CPPS, IPPS, and DBS VNFCs can be scaled in increments of a single VM.

2. Nokia Cloud Packet Core VNF Configuration Guide, Document Version 22.R1, Chapter: "Scaling Procedures", Section: "PAPS Scaling".

This guide provides the operational procedures for managing the Cloud Packet Core. The PAPS scaling section outlines the requirement to scale the component in pairs, stating, "The number of PAPS instances must always be an even number. The scaling step for PAPS is two VMs." This confirms that single VM scaling is not supported for PAPS.