The statement is false in the intended examination context because resource allocation type 0 uses Resource Block Group (RBG) granularity, which is generally coarser than the individual Resource Block (RB) allocation granularity available through type 1.
In NR downlink scheduling, the gNodeB allocates Physical Downlink Shared Channel (PDSCH) resources according to the configured frequency-domain resource-allocation method.
According to 3GPP TS 38.214, type 0 allocation uses a bitmap in which each bit indicates whether a corresponding RBG is assigned to the scheduled UE.
An RBG normally contains multiple consecutive RBs, with its nominal size determined by the Bandwidth Part (BWP) size and the configured RBG-size parameter.
For example, standardized nominal RBG sizes include 2, 4, 8, and 16 RBs.
Type 0 supports flexible selection of adjacent or nonadjacent RBGs, making it useful for scheduling across separated frequency-domain resources.
However, it may allocate more bandwidth than necessary when only a small amount of data must be transmitted.
Type 1 allocation identifies a starting RB and a contiguous allocation length, permitting finer control of the assigned resource quantity.
Therefore, type 0 is not inherently preferable for small-data scheduling merely because its minimum normal allocation is one RBG.
Official Reference: 3GPP TS 38.214, Sections 5.1.2.2.1 and 5.1.2.2.2, Downlink Resource Allocation Types 0 and 1 .
Technical warning / qualification: Type 0 is not prohibited for small packets. The incorrect part is the conclusion that RBG-level granularity makes it particularly suitable for small-data scheduling.