Question: 1 / 75

Which two asset types do NOT have revision histories?

Documents

Core Assets

Completion

The reason "Completion" is the correct answer is that it typically refers to a status or a checklist that tracks the progress of tasks or projects rather than representing a tangible asset or resource. Unlike documents or core assets, which often require version control due to their content changes or updates, completions are often considered transient. They don't need a revision history since they merely indicate whether a particular task has been finished. On the other hand, documents and core assets often undergo multiple iterations and updates, necessitating the ability to refer back to previous versions. Organizations, while they might not change frequently, also have properties that can evolve over time, thereby justifying the need for a revision history to document those changes and ensure accurate record-keeping.

Organizations

Next

Report this question