Question: What happens when independent units are signaled in an FDT Instance, in relation to Content-Encoding, according to MBMS protocols?
Option 1: The attribute `mbms2015: IndependentUnitPositions` must be used in conjunction with Content-Encoding for efficient data transfer.
Option 2: The use of Content-Encoding is optional but recommended when signaling independent units with `mbms2015: IndependentUnitPositions`.
Option 3: Signaling independent units with `mbms2015: IndependentUnitPositions` has no implications for Content-Encoding usage.
Option 4: The attribute `mbms2015: IndependentUnitPositions` shall not be used in combination with the use of Content-Encoding.
Explanation: This is correct because, according to the MBMS protocols specified in the context of FDT Instance signaling, there's a specific restriction that prohibits the simultaneous use of `mbms2015: IndependentUnitPositions` (for signaling independent units) and Content-Encoding. This ensures predictable handling and access to file content based on the signaled independent units without the potential complexities introduced by encoding.