How should attachments be managed in relation to their parent documents under UAP Document 301?

How should attachments be managed in relation to their parent documents under UAP Document 301?

• A. Attachments inherit parent document IDs; track versions of attachments; preserve linkage across edits.
• B. Attachments get independent IDs; no lineage.
• C. Attachments are deleted when parent is edited.
• D. Attachments cannot be linked.

Answer: (A)

The main idea here is to maintain a durable, auditable link between a document and its attachments. Attachments should inherit the parent document’s ID so they remain clearly tied to that specific document, and each attachment should have its own version history so changes to the attachment itself can be tracked over time. Preserving this linkage across edits ensures that even as the parent document evolves, the attachment stays associated with the correct document version, preserving the relationship and the ability to audit what was attached and when.

This approach creates a complete trail that supports accurate retrieval and change history. It avoids breaking the connection if the parent is revised and ensures attachments aren’t left orphaned or disconnected from their source. In contrast, giving attachments independent IDs with no lineage would sever the link to the parent; deleting attachments when the parent is edited would erase history; and saying attachments cannot be linked ignores a fundamental need for traceability in document management.