The water utility releases a new meter-reading app that talks to Intersight. Two engineers ship builds with different unofficial and official client library versions because the SDK was left unpinned. What should the release process treat the platform client library as?
Select an answer to reveal the explanation.
Short Explanation
Cisco platform SDKs are ingredients in the meal kit, not free air in the kitchen. Pinning them documents the API surface you actually tested and keeps both engineers shipping the same client behavior.
Full Explanation
Dependency management includes official controller and compute client libraries, not only web frameworks. Bumping an SDK documents a new minimum API surface; leaving it unpinned lets two builds diverge. Secrets rotation and campus switching concerns are different domains and do not replace versioning the client library in the release.