Regarding deployment to Exchange via the Exchange Maven Facade API, which statement is true about versioning?

• A. SNAPSHOT versions are allowed for deployment without restrictions
• B. SNAPSHOT versions are not allowed for deployment to Exchange
• C. Only stable releases can be deployed to Exchange
• D. Versioning has no impact on Exchange deployment

Answer: (B)

When deploying to Exchange via the Maven Facade API, the version you publish must be an immutable, released artifact. SNAPSHOT versions are designed for in-development work and can change over time, which would lead to unstable, non-deterministic deployments for downstream users. Requiring only released versions ensures consistency, reproducibility, and trust in what is deployed to Exchange. So SNAPSHOT versions are not allowed for deployment to Exchange; use a finalized release version (for example, 1.0.0) for deployment. If you need to prototype or test, keep SNAPSHOTs in your internal or development repositories rather than in Exchange, since versioning directly impacts stability and artifact integrity.