The correct answer is B .
In contention-based random access , the UE chooses a random access preamble by itself from a configured pool of available contention-based preambles. This is typically used when the UE does not yet have a dedicated connection or when the network has not assigned a dedicated preamble.
Because multiple UEs may choose the same preamble at the same time, preamble collision is possible . That is why CBRA requires a contention resolution step.
Option C describes contention-free random access , not CBRA. In contention-free random access, the network assigns a dedicated preamble to the UE, so collision risk is avoided and contention resolution is not required.
Option A is not the correct CBRA principle being tested. RACH false detection can be a receiver/design issue, but it does not define the CBRA procedure.
Option D describes a possible NSA signaling behavior around access failure handling, but it is not the core correct definition of CBRA.
Therefore, the correct CBRA statement is:
The UE autonomously selects a preamble from the configured range and starts the random access procedure.

The correct answer is Format 1 / Type B .
For PRACH planning, the selected preamble format must support the required cell radius. Format 0 is too short for a 33 km cell because it is typically suitable only up to around 14.5 km . Format 2 is also not suitable because its practical maximum cell radius is around 29.5 km , which is below the required 33 km . Therefore, a longer PRACH format is needed.
Because the scenario mentions high mobility , an unrestricted PRACH set is not preferred. High-mobility environments require a restricted set to handle Doppler effects and reduce ambiguity in PRACH preamble detection. Between the restricted-set options, Type B is the correct choice for this 33 km high-mobility case.
A matching Nokia-style question source also lists this exact scenario with Format 1 / Type B as option A.

The correct answer is C .
Scheduling Request , or SR , is used by the UE to request uplink resources when it has uplink data to send.
The SR periodicity defines how often the UE gets an opportunity to send this scheduling request.
A shorter SR periodicity means the UE can request uplink resources more quickly, which improves uplink latency. However, it consumes more PUCCH/control-channel resources, reducing the number of UEs that can be efficiently supported.
A longer SR periodicity saves control-channel resources and can support more connected users, but it increases uplink access delay.
Therefore, SR periodicity is important because it creates a trade-off between:
Lower latency and higher connected-user capacity.

The correct answer is C .
At mmWave / FR2 frequencies , radio propagation is more challenging than in low-band or mid-band spectrum. Diffraction becomes weaker, blockage is more severe, foliage attenuation is high, and building penetration loss is significant. This is why mmWave networks usually require dense site grids, line-of-sight or near-line-of-sight paths, and strong beamforming. Industry mmWave references consistently describe high path loss, high penetration loss, and the need for directional antenna systems to compensate for these losses.
Option C does not apply because water absorption and atmospheric absorption generally become more relevant at higher frequencies, not lower. Rain, humidity, and oxygen/water-vapor absorption are important considerations for mmWave link budgets.
So the statement that does not apply to mmWave propagation is:
Low water absorption at high frequencies.

The correct answer is A .
During an intra-gNB DU handover , the UE is moved from one cell/DU resource to another under the same gNB-CU control. The gNB-CU coordinates the handover preparation and sends an RRC Reconfiguration message to the UE.
The role of this message is to provide the UE with the required handover command information, such as:
Target PCell configuration
Radio resource configuration
Mobility control information
Random access configuration, when needed
Measurement or reconfiguration-related information
After receiving the RRC Reconfiguration , the UE performs the handover execution procedure toward the target cell and later responds with RRC Reconfiguration Complete .
Option B is incorrect because admission control and source-cell scheduling suspension are internal network- side procedures, not the UE-facing role of the RRC Reconfiguration message.
Option C is not the best answer because user-plane resource transfer is handled between gNB-CU/gNB-DU functions, while dedicated preamble allocation may be part of the configuration but is not the main purpose of the message.
Option D is incorrect because RLC reestablishment and PDCP recovery are lower-layer/user-plane handling actions, not the primary purpose of the RRC Reconfiguration message.
Therefore, the correct role is:
It instructs the UE to perform handover to the target PCell and provides measurement/configuration information.