In which scenarios will a new version of a digital asset be created?

A new version of a digital asset is created when uploading a file through the user interface because this action typically triggers the versioning mechanism within the content management system. When a user uploads a new file that has the same name as an existing asset, the system recognizes it as an update and automatically creates a new version of that asset. This allows for version control, enabling users to track the history of changes made to the asset over time, which is crucial for maintaining content accuracy and ensuring that previous versions can be retrieved if needed.

In comparison, uploading a file via FTP does not inherently trigger the creation of a new version; it may simply replace the existing asset without creating an additional version in some configurations. Modifying the metadata of a digital asset may result in updates to the asset's information, but it does not generate a new version since the actual file content remains unchanged. Similarly, deleting an existing digital asset does not create a new version; rather, it removes the asset from the repository, which does not contribute to versioning at all. Therefore, uploading a file through the user interface is the correct scenario that results in a new version being created.