AZ400-Q: choose a package version strategy
A public library promises that consumers can reason about backward compatibility from its version. A separate internal operational image is released on a fixed monthly cadence. Which strategy is most appropriate?
- A) Use SemVer for the compatibility-oriented library and consider date-based versioning for the cadence-driven internal image. ✓
- B) Use random numbers for both.
- C) Reuse one version name for every release.
- D) Use a Git branch name as the immutable package version.
Answer: A. Semantic versioning communicates compatibility intent; calendar versioning can communicate a time-based release cadence. Both need immutable published artifacts.
Why not the others: Random/reused names destroy predictable dependency selection and traceability. Branches move and are not immutable package versions.
Related
semantic-versioning · upstream-and-versioning · build-artifact