Examine this scenario:
* Joe adds an existing asset to a new project.
* You add the same asset to a different project
* Joe edits his working version of the asset and deploys his project.
* The assets in Joe’s project are checked in and constitute a new base version of those assets.
What is the expected default behavior of the BCC?
A.
You must resolve the conflict before a production deployment can be made.
B.
Your project will need to be started over againas there is a version conflict.
C.
You can deploy your project to production but you must resolve the conflict before you can
check your changesin.
D.
The deployment will start but will not complete throwing a version mismatch exception that
needs to be resolved by the administrators.
E.
Joe will not be able to use the same assetina different project.
Explanation:
Asset Version Numbering
The versioning system maintains two types of version numbers:
Base version number: The latest checked-in version of the asset. When an asset is created, its
initial base version number is 1.
Potential version number: The version number that is conditionally assigned to each checked-out
version of an asset.
When you add an asset to a project, the system assigns it a potential version number. When the
project checks in its asset, the system converts the potential version number to the new base
version. If another project checked in the same asset earlier, the system assigns the next available
number to the new base version.
For example:ATG Content Administration Guide for Business Users, Asset Version Numbering