A developer has created a custom policy with version "1.0.0-SNAPSHOT". The developer attempts to publish the policy to Exchange using the Exchange Maven Facade API version 3 and then apply the policy in API Manager. What will happen?

• A. The policy will deploy successfully to Exchange.
• B. The policy will not successfully deploy to Exchange.
• C. The policy will deploy but fail to apply in API Manager.
• D. The policy will be accepted but marked as SNAPSHOT in API Manager.

Answer: (B)

SNAPSHOT versions indicate a work-in-progress or evolving artifact, not a finalized release. Exchange enforces that published policies are stable release versions, so a version like 1.0.0-SNAPSHOT is rejected when publishing via the Exchange Maven Facade API v3. Because the publish attempt fails, the policy isn’t deployed to Exchange, and there’s nothing for API Manager to apply. To succeed, use a release version such as 1.0.0, publish it to Exchange, and then apply that deployed policy in API Manager.