Free Nokia BL0-220 Practice Exam with Questions & Answers | Set: 2

A YAML XML template file contains the configuration of a VNF or CNF. A VNF stands for Virtual Network Function, which is a software-based network function that runs on a virtual machine or a container. A CNF stands for Cloud-native Network Function, which is a network function that is designed and implemented using cloud-native principles and technologies, such as microservices, containers, and Kubernetes. A YAML XML template file is a file that defines the structure, parameters, and dependencies of a VNF or CNF, as well as the resources and policies required to deploy and manage it. A YAML XML template file is based on the TOSCA (Topology and Orchestration Specification for Cloud Applications) standard, which is a language for describing the components and relationships of complex cloud applications. A YAML XML template file is used by the MANO (Management and Orchestration) system to instantiate, configure, and operate a VNF or CNF on the cloud infrastructure. References: Nokia Bell Labs 5G Professional Certification - Distributed Cloud Networks, Unit 2: Cloud Technologies and Features, Section 2.4: Cloud Software and Hardware Resources.

The properties related to a private cloud are high CAPEX and full control. CAPEX stands for capital expenditure, which is the money spent on acquiring or upgrading physical assets such as servers, storage, and network equipment. A private cloud requires high CAPEX because the cloud owner has to invest in building and maintaining the cloud infrastructure. Full control means that the cloud owner has the exclusive authority and responsibility over the cloud resources, security, and operations. A private cloud offers full control because the cloud owner can customize the cloud according to their specific needs and preferences, and can ensure the privacy and compliance of their data and applications. References: Nokia Cloud Platform, Module by Module - Self Study Note Guide

The ETSI MANO Model operational stack is defined as Orchestration above Network Function Management above Infrastructure Management. The ETSI MANO Model is a framework that defines the architecture and interfaces for the management and orchestration of network functions virtualization (NFV) in cloud networks1. The ETSI MANO Model consists of three main components: Infrastructure Management, Network Function Management, and Orchestration2. Infrastructure Management is responsible for managing the physical and virtual resources that host the network functions, such as servers, storage, switches, hypervisors, andvirtual machines2. Network Function Management is responsible for managing the configuration, monitoring, and optimization of the network functions, such as scaling, healing, and updating2. Orchestration is responsible for coordinating the allocation and release of resources for network services and network slices, such as instantiation, termination, and modification2. The ETSI MANO Model operational stack is defined as Orchestration above Network Function Management above Infrastructure Management, meaning that Orchestration is the highest level of abstraction and control, Network Function Management is the intermediate level, and Infrastructure Management is the lowest level2. References: 1: Nokia Bell Labs Distributed Cloud Networks, Unit 5: New Services Automation, Section 5.3: Orchestration 2: Module by Module - Self Study Note Guide - training2

Single and consistent point of management. Comprehensive Explanation and References of Correct Answer: Network Function Management provides different network slices for different companies and a single and consistent point of management. Network slicing is a technique that allows the creation of multiple logical networks on top of a shared physical infrastructure1. Each network slice can have its own characteristics, requirements, and services, tailored to the needs of different customers or applications1. Network Function Management is a component that handles the configuration, monitoring, and optimization of the network functions that compose each network slice2. It provides a single and consistent point of management for the network functions, regardless of their location, type, or vendor2. Multiple Orchestrators required for deployments is not a correct option. An Orchestrator is a component that coordinates the allocation and release of resources for network services and network slices3. There are different types of Orchestrators, such as NFV Orchestrator, NS Orchestrator, and Slice Orchestrator, but they are not part of the Network Function Management3. References: 1: Nokia Bell Labs Distributed Cloud Networks, Unit 5: New Services Automation, Section 5.1: Network Slicing 2: Nokia Bell Labs Distributed Cloud Networks, Unit 5: New Services Automation, Section 5.2: Network Function Management 3: Nokia Bell Labs Distributed Cloud Networks, Unit 5: New Services Automation, Section 5.3: Orchestration

 OCP stands for Open Compute Project, which is an initiative to design and enable the delivery of the most efficient server, storage and data center hardware designs for scalable computing1. OCP is the primary cloud infrastructure platform to develop, test and deliver Nokia’s core network applications and business applications, benefiting from its scalability, flexibility, and advanced orchestration capabilities2. OCP is also part of the Nokia Cloud Platform, which is a TCO optimized solution that combines OCP with Nokia’s reference hardware andblueprint architecture2. References: 1: Open Compute Project, Home Page 2: Nokia Cloud Platform,

The main parameters of policy-based auto-scaling are threshold and min/max values. Threshold is the value of a metric that triggers the scaling action, such as CPU utilization or memory usage1. Min/max values are the minimum and maximum number of instances or resources that can be scaled up or down1. Priority and description are not parameters of policy-based auto-scaling. Priority is the order of execution of policies in case of conflicting or overlapping conditions2. Description is the optional text that provides additional information about the policy2. References: 1: Nokia Bell Labs Distributed Cloud Networks, Unit 4: Operating Your Cloud, slide 24 2: Nokia CloudBand Application Manager User Guide, Chapter 9: Scaling Policies, page 151

Different paths for a NF providing Cloud Resilience are defined in a Network Service Descriptor. A Network Service Descriptor (NSD) is a document that describes the topology, configuration, and requirements of a network service. It specifies the network functions (NFs) that compose the service, the virtual links that connect them, and the forwarding graphs that define the traffic flows between them1. A NSD also defines the resilience policies for each NF, such as the number of instances, the scaling triggers, the fault management actions, and the alternative paths in case of failures2. A Network Function template, an NS Orchestrator configuration, and an NFV Orchestrator configuration are not the correct options to complete the sentence. A Network Function template is a document that describes the characteristics and requirements of a single network function, such as the virtualization environment, the resources, the interfaces, and the dependencies1. An NS Orchestrator configuration is a set of parameters that control the behavior and operation of the NS Orchestrator, which is a component that manages the lifecycle of network services3. An NFV Orchestrator configuration is a set of parameters that control the behavior and operation of the NFV Orchestrator, which is a component that coordinates the allocation and release of resources for network services3. References: 1: Nokia Bell Labs Distributed Cloud Networks, Unit 3: Cloud Resource Planning, Section 3.2: Network Function 2: Nokia Bell Labs Distributed Cloud Networks, Unit 3: Cloud Resource Planning, Section 3.3: Network Service Descriptor Role 3: Nokia Bell Labs Distributed Cloud Networks, Unit 4: Operating Your Cloud, Section 4.1: Industry Trends in Data Center Hardware

Cloud resource management provides management of the resources quota and the ability to scale resources up and down. Resource quota is the limit on the amount of resources that atenant can use in a cloud environment, such as CPU, memory, storage, network, etc. Resource quota helps to prevent overconsumption of resources by a single tenant and to ensure fair allocation of resources among multiple tenants. The ability to scale resources up and down means that the cloud can dynamically adjust the amount of resources allocated to a tenant based on the demand and availability. Scaling resources up and down helps to optimize the performance and efficiency of the cloud, as well as to reduce the cost and waste of resources. References: Nokia Bell Labs Distributed Cloud Networks, Cloud Resource Planning