Select all that apply.

• A

  Version statuses must be used in conjunction with tokens to mark which versions are ready for deployment.

• B

  Version statuses must be used in conjunction with environment gates to govern which versions are allowed into specific environments.

• C

  Version statuses must be used in conjunction with locks to identify which environments are locked for marked versions.

• D

  Version statuses must be used in conjunction with component tags to tag which versions can be deployed.