In order to ensure versioning integrity, a deploying project obtains exclusive locks on its assets
when deployment starts. What is the effect of these locks?
A.
Until a project’s asset looks are released, other projects that share those assets cannot add the
asset to the project.
B.
Until a project’s asset locks are released, other projects that share those assets cannot
heinauthor mode and are shown as lockedinthe BCC UI.
C.
Until a project’s asset locks are released, other projects that share those Assets cannot deploy.
D.
It is a database lock and has no effect on the UI. Other projects will net a concurrent update
exception it a database save is issued for the shared assets.
Explanation:
In order to ensure versioning integrity, a deploying project obtains exclusive locks on
its assets when deployment starts. It releases those locks only after deployment is complete and
project assets are checked in, or when the deployment is reverted. Until a project’s asset locks are
released, other projects that share those assets cannot deploy.
ATG Content Administration Guide for Business Users,Resolving Asset Locks