Q48 of 60 — CCA Practice Exam

Claude Code for Continuous Integration

Your team ships a Claude Code plugin that bundles a custom MCP server for interacting with your CI pipeline. The plugin is distributed via an internal git-hosted marketplace and its plugin.json contains "version": "1.4.0". Engineers report that after you pushed a critical fix to the plugin's gate-check script last week, CI jobs on several machines are still running the old, broken script — even after they ran /plugin update, which reported "already at the latest version." No one bumped the version field. What is the root cause of this update failure, and what is the correct fix going forward?

A. The plugin's MCP server does not restart automatically after an update; engineers must manually restart their Claude Code sessions to reload the new server binary and pick up the gate-check script fix.

B. Because "version": "1.4.0" is set in plugin.json, Claude Code uses that string as the cache key and skips the update when the string hasn't changed — regardless of new commits. The fix is to bump the version field on every release, or remove it so the git commit SHA is used as the cache key instead.

C. The internal git-hosted marketplace caches the old plugin archive on its server and must be manually cleared before /plugin update can detect new commits. The fix is to configure the marketplace server to disable HTTP caching headers so fresh archives are always served.

D. The version field in plugin.json takes precedence over the marketplace entry, so the marketplace's version was never consulted. The fix is to remove the version from plugin.json and set it only in marketplace.json, making the marketplace the single authoritative source for the version string.