What information does an asset log detail for each asset?

• A. Owner's email and password.
• B. Origin, properties, and copyright issues.
• C. File size, creation date, and update history.
• D. Location in folder structure.

Answer: (B)

The main idea is that an asset log should capture who created or supplied the asset, what the asset is like, and what rights you have to use it. Origin tells you where the asset came from, which supports provenance and licensing checks. Properties cover the technical and descriptive details of the asset (such as format, size, dimensions, duration, metadata) that you need for proper handling and compatibility. Copyright issues track the licensing status, usage rights, and any restrictions or attribution requirements, which is crucial to use the asset legally. Other options miss one or more of these essential pieces—login credentials aren’t stored in asset logs, folder location relates to organization rather than per-asset data, and isolated metrics like file size or creation date don’t cover rights and provenance.