Practice Free BL0-100 Nokia Bell Labs 5G Foundation Exam Questions Answers With Explanation

TS.33.501

OTS 23.501

06.25.14

KZW.TY67

Fronthaul Core

Access Backhaul

Metropolitan or Regional Core

Backbone Core

Spatial

Data Center

Vertical

Horizontal

By implementing resource isolation and security isolation on the network slice

By implementing virtual firewall on the network slice

By implementing traffic isolation on the network slice

By implementing user and control planes separation on the network slice

Increased cell coverage

Better latency

Reduced cost by centralizing some radio functionalities

Increase radio throughput

Hijack attack on hypervisor

DDoS attack on the SDN switches

Poor NFV implementation

Hypervisor resources leakage

Network Slicing is just like the OSI model. It is the division of the network into layers horizontally from the physical to the application. It is needed to specify which layer a service resides.

Network Slicing is a technology that allows the network to serve applications with different sets of requirements in terms of latency, reliability, capacity, density, and such. Every application has a set of requirements different from others. With network slicing, we give every application what it needs from the network.

Network Slicing is an end-to-end “virtual private service”, extending across access, transport, core, and cloud. It is a general term used to define in which piece of the network we are.

Network slicing is a new technology to divide the network among users. It is needed for confidentiality purposes.

The “sweet spot” for industry 4.0 is the intersection of URLLC, eMBB and mMTC.

The “sweet spot” for industry 4.0 is a double-digit revenue growth.

The “sweet spot” for industry 4.0 is a deployment strategy for delivering the required capacity and coverage for industrials.

The “sweet spot” for industry 4.0 is the intersection of operational, information and communications technologies.

IPSec

Access Control List

SSH

X25

It should run in the central cloud as latency is not very important here. Reliability is guaranteed by the central cloud.

The application should run in the central cloud, with very high access throughput to support low latency.

It should be installed locally on the car computer and the company operator should remotely connect to it. This approach is more secure.

It should be running in the edge cloud because latency is very important for the remote control of vehicles in motion and also for reliability purposes.

Option 4

Option 2

Option 3x

Option 7

Low latency characteristics in the range of 5 to 10 ms for High Speed Discrete Automation Applications.

Low latency characteristics in the range of 0.1 to 1 ms for Video Monitoring and AR.

Low latency characteristics in the range of 100 to 200 ms for Remote Control Tele-operation Applications.

Low latency characteristics in the range of 50 to 100 ms for Discrete and Process Automation Applications.

Increased spectral density

Increased transmission robustness with transmit diversity

Increased throughput per user

Reduced latency

Low peak and end-user-experience throughput

Low reliability

High latency

Beamforming is not supported