Which components are typically found in a protocol message for the EPD Pilot?

• A. Envelope, signature, and routing.
• B. Control tokens and metadata only.
• C. Header, payload, and footer.
• D. Header and payload with no error-checking.

Answer: (C)

A protocol message is built to separate how the message is handled from the data it carries, and to mark the message boundaries for reliable processing. The header provides routing information, the message type, and length so the receiver knows how to interpret and route the data. The payload is where the actual information or content goes. The footer typically includes an end marker or a checksum to help detect truncation or corruption and to verify integrity as the message is processed. This trio—header for control, payload for content, and footer for integrity—gives a complete, practical, and reliable message structure, which is why it’s the best fit.

The other options miss one or more essential pieces: they either emphasize security or packaging features over the actual data, omit the data portion, or lack an error-checking component, making them incomplete for a standard protocol message.