Question: When storing an MMS notification that exceeds the maximum possible number of bytes for EFMMSN, how does the Mobile Equipment (ME) handle the storage process in relation to EFEXT8?
Option 1: The ME stores the entire MMS notification in a single record within EFEXT8, overwriting any existing data if necessary.
Option 2: The ME splits the MMS notification across multiple records in EFMMSN, without using EFEXT8 for additional storage.
Option 3: The ME stores as many bytes as possible in EFMMSN and then seeks a sufficient number of free records in EFEXT8 to store the remaining bytes, chaining records if necessary.
Option 4: The ME aborts the storage process if the MMS notification exceeds EFMMSN's capacity, without attempting to use EFEXT8.
Explanation: This option correctly describes the procedure for handling MMS notifications too large for EFMMSN. By storing as much of the notification as possible in EFMMSN and utilizing EFEXT8 for the remaining data (potentially chaining multiple records), the ME efficiently manages storage, adhering to each file type's constraints without overwriting existing data unnecessarily or aborting prematurely.