Question: In an MBMS (Multimedia Broadcast/Multicast Service) scenario, what constitutes a 'partial file' when a file cannot be fully recovered by the MBMS Client?
Option 1: Only the received bytes of the original file, without any associated metadata.
Option 2: The collection of all FDT Instance data (including Content-Location, Content-Length, Content-Type) and all received bytes with their position in the original file.
Option 3: Files that are intentionally truncated by the server for bandwidth optimization.
Option 4: Files that are fully recovered but lack the mbms2015:IndependentUnitPositions attribute.
Explanation: A partial file in MBMS includes not just the received bytes of the file but also associated metadata from the FDT Instance (like Content-Location, Content-Length, and Content-Type), along with positional information of the received bytes within the original file, providing context for handling.