Question 180
A secret needed by a custom tool is written directly in settings.json checked into Git. What should change?
- Reference a secure external credential source instead of committing secret values.
- Verify environment-specific endpoint mappings and credentials before deployment.
- Position team-wide rules in the repository's CLAUDE.md and review changes.
- Place the security requirement in a higher-priority managed policy and actual tool permissions.
Explanation
Correct Answer
A:Configuration files can be reviewed and copied; secret lifecycle belongs in a credential manager or protected environment.
Incorrect Answers
B:The correct tool schema can still cause damage when its endpoint is misconfigured; environment segregation must include targets and identity; the effect concerns environment endpoint isolation; the success condition is secret externalization.
C:Versioned project instructions are visible to collaborators, whereas personal configuration can vary across machines; even if shared project instruction source succeeds, secret externalization still needs separate verification.
D:Advisory instructions can conflict; enforceable organizational controls must not be overridden by user-local customization; where secret externalization matters, a control for nonoverridable organizational policy leaves that test unmet.
Question 181
A connector upgrade changes tool argument names. How should the dependency be handled?
- Check environment-specific endpoint mappings and credentials before deployment.
- Capture model identifier, prompt revision, tool schema version, and safe request correlation IDs.
- Fix a tested model version where the platform provides versioned identifiers.
- Version or pin the connector dependency and run tool-contract regression tests.
Explanation
Correct Answer
D:Tool schemas are part of the application interface; uncontrolled plugin updates can break dispatch or model selection.
Incorrect Answers
A:The correct tool schema can still cause damage when its endpoint is misconfigured; environment segregation must include targets and identity; because environment endpoint isolation is its concern, connector version compatibility remains outside its effect here.
B:Behavior depends on a combination of versioned inputs; isolated text logs may not identify which configuration was active; it changes inference incident provenance; it does not prove connector version compatibility in this case.
C:An unpinned alias can change behavior without an application deployment; version pinning enables controlled evaluation and rollback; the effect concerns stable production model identity; the success condition is connector version compatibility.
Question 182
A developer lets Claude Code propose a pull request that touches authentication and billing files. Which SDLC gate should precede merge?
- Require an independent diff review, scoped test results, and human approval for sensitive changes.
- Partition versioned static instructions from typed runtime variables.
- For this workflow, manage prompt templates as versioned deployment artifacts.
- Employ the managed configuration layer supported by the organization.
Explanation
Correct Answer
A:Generated code remains subject to ordinary repository controls; reviewing the actual file changes and tests prevents an assistant's confident summary from granting merge authority.
Incorrect Answers
B:Controlled templates make prompt revisions auditable, and validated variables reduce accidental changes to governing instructions; this targets static versus dynamic prompt values, while the system must demonstrate human review gate for AI-generated changes.
C:Reviewed, traceable templates connect observed behavior to a release and allow reversal of regressions; for this request, human review gate for AI-generated changes is the missing piece, not prompt template change tracking.
D:Central policy has authority over developer preferences; ordinary repo files should not be relied on to enforce enterprise security limits; where human review gate for AI-generated changes matters, a control for managed configuration precedence leaves that test unmet.
Question 183
An organization wants to override a risky local setting for all managed development machines. What layer should implement the enforced policy?
- Use the managed configuration layer supported by the organization.
- Log both version identifiers and compare them on the same evaluation set before switching traffic.
- Establish the server command or endpoint and its needed scoped credentials in the appropriate project settings.
- Employ environment-appropriate settings and restrict the CI permission mode.
Explanation
Correct Answer
A:Central policy has authority over developer preferences; ordinary repo files should not be relied on to enforce enterprise security limits.
Incorrect Answers
B:Behavior changes across model versions are deployment changes; a tested rollout prevents silent production regressions; the effect concerns multi-criterion integration; the success condition is managed configuration precedence.
C:MCP clients need a connection definition and authentication path; a tool name alone does not create a working integration; for this request, managed configuration precedence is the missing piece, not project MCP connection configuration.
D:Automation runs without the same human supervision as local sessions, so its authority should be explicitly narrower; when the goal is managed configuration precedence, optimizing environment-specific Claude Code permissions misses that operational boundary.
Question 184
A project has conflicting instructions across nested CLAUDE.md files. What should a maintainer investigate?
- Inspect which instruction files load for the current working path and resolve conflicts explicitly.
- Adopt the managed configuration layer supported by the organization.
- Adopt environment-appropriate settings and restrict the CI permission mode.
- Track versions of or pin the connector dependency and run tool-contract regression tests.
- Use a secure external credential source instead of committing secret values.
Explanation
Correct Answer
A:File location and instruction hierarchy affect applicable context; copying more directions into chat can mask the root conflict.
Incorrect Answers
B:Central policy has authority over developer preferences; ordinary repo files should not be relied on to enforce enterprise security limits; the scoped instruction hierarchy criterion differs from managed configuration precedence; the gap persists.
C:Automation runs without the same human supervision as local sessions, so its authority should be explicitly narrower; the scenario's controlling requirement is scoped instruction hierarchy, not the related environment-specific Claude Code permissions concern.
D:Tool schemas are part of the application interface; uncontrolled plugin updates can break dispatch or model selection; it improves connector version compatibility only, leaving scoped instruction hierarchy unproven.
E:Configuration files can be reviewed and copied; secret lifecycle belongs in a credential manager or protected environment; this targets secret externalization, while the system must demonstrate scoped instruction hierarchy.
Question 185
A team adds a new MCP integration for a single repository. What should deployment configuration specify?
- Define the server command or endpoint and its needed scoped credentials in the appropriate project settings.
- Point to a secure external credential source instead of committing secret values.
- Apply environment-appropriate settings and restrict the CI permission mode.
- Label versions of or pin the connector dependency and run tool-contract regression tests.
Explanation
Correct Answer
A:MCP clients need a connection definition and authentication path; a tool name alone does not create a working integration.
Incorrect Answers
B:Configuration files can be reviewed and copied; secret lifecycle belongs in a credential manager or protected environment; a remedy for secret externalization is not a substitute for project MCP connection configuration.
C:Automation runs without the same human supervision as local sessions, so its authority should be explicitly narrower; for this request, project MCP connection configuration is the missing piece, not environment-specific Claude Code permissions.
D:Tool schemas are part of the application interface; uncontrolled plugin updates can break dispatch or model selection; changing connector version compatibility does not establish project MCP connection configuration in this application.
Question 186
A prompt template includes a date, customer ID, and dynamic policy text in a single mutable string. What change aids debugging?
- Add the security requirement in a higher-priority managed policy and actual tool permissions.
- Store model identifier, prompt revision, tool schema version, and safe request correlation IDs.
- Confirm environment-specific endpoint mappings and credentials before deployment.
- Separate versioned static instructions from typed runtime variables.
Explanation
Correct Answer
D:Controlled templates make prompt revisions auditable, and validated variables reduce accidental changes to governing instructions.
Incorrect Answers
A:Advisory instructions can conflict; enforceable organizational controls must not be overridden by user-local customization; this may help nonoverridable organizational policy but cannot by itself deliver static versus dynamic prompt values.
B:Behavior depends on a combination of versioned inputs; isolated text logs may not identify which configuration was active; changing inference incident provenance does not establish static versus dynamic prompt values in this application.
C:The correct tool schema can still cause damage when its endpoint is misconfigured; environment segregation must include targets and identity; it follows environment endpoint isolation constraints but leaves static versus dynamic prompt values unspecified.
Question 187
A release modifies a response schema but leaves frontend parsers untouched. What configuration process would catch it?
- Ship schema and consumer changes with compatibility tests under a coordinated release.
- At the application layer, manage prompt templates as versioned deployment artifacts.
- Store the security requirement in a higher-priority managed policy and actual tool permissions.
- Locate team-wide rules in the repository's CLAUDE.md and review changes.
Explanation
Correct Answer
A:Generated output contracts span both sides of the interface; configuration drift can break consumers even when API calls succeed.
Incorrect Answers
B:Reviewed, traceable templates connect observed behavior to a release and allow reversal of regressions; where schema release coordination matters, a control for prompt template change tracking leaves that test unmet.
C:Advisory instructions can conflict; enforceable organizational controls must not be overridden by user-local customization; for schema release coordination, this instead manages nonoverridable organizational policy; the requested decision remains unresolved.
D:Versioned project instructions are visible to collaborators, whereas personal configuration can vary across machines; this may help shared project instruction source but cannot by itself deliver schema release coordination.
Question 188
A development team wants to reproduce a model incident from last month. Which metadata should request logs retain?
- Document the server command or endpoint and its needed scoped credentials in the appropriate project settings.
- Capture both version identifiers and compare them on the same evaluation set before switching traffic.
- Check which instruction files load for the current working path and resolve conflicts explicitly.
- Record model identifier, prompt revision, tool schema version, and safe request correlation IDs.
Explanation
Correct Answer
D:Behavior depends on a combination of versioned inputs; isolated text logs may not identify which configuration was active.
Incorrect Answers
A:MCP clients need a connection definition and authentication path; a tool name alone does not create a working integration; where inference incident provenance matters, a control for project MCP connection configuration leaves that test unmet.
B:Behavior changes across model versions are deployment changes; a tested rollout prevents silent production regressions; the inference incident provenance criterion differs from multi-criterion integration; the gap persists.
C:File location and instruction hierarchy affect applicable context; copying more directions into chat can mask the root conflict; it follows scoped instruction hierarchy constraints but leaves inference incident provenance unspecified.
Question 189
A user adds personal instructions that tell Claude Code to bypass repository security checks. What should enforce the nonnegotiable rule?
- Make mandatory an independent diff review, scoped test results, and human approval for sensitive changes.
- Put the security requirement in a higher-priority managed policy and actual tool permissions.
- Publish schema and consumer changes with compatibility tests under a coordinated release.
- Cite a secure external credential source instead of committing secret values.
Explanation
Correct Answer
B:Advisory instructions can conflict; enforceable organizational controls must not be overridden by user-local customization.
Incorrect Answers
A:Generated code remains subject to ordinary repository controls; reviewing the actual file changes and tests prevents an assistant's confident summary from granting merge authority; this implements human review gate for AI-generated changes rather than the demanded nonoverridable organizational policy.
C:Generated output contracts span both sides of the interface; configuration drift can break consumers even when API calls succeed; for this request, nonoverridable organizational policy is the missing piece, not schema release coordination.
D:Configuration files can be reviewed and copied; secret lifecycle belongs in a credential manager or protected environment; the consequence is improved secret externalization, not verified nonoverridable organizational policy.
Question 190
A staging environment silently points at production data through a shared MCP URL. What configuration check would prevent this?
- Store both version identifiers and compare them on the same evaluation set before switching traffic.
- Validate environment-specific endpoint mappings and credentials before deployment.
- Test connector compatibility without checking the staging environment endpoint or credentials.
- Deploy schema and consumer changes with compatibility tests under a coordinated release.
- Choose environment-appropriate settings and restrict the CI permission mode.
Explanation
Correct Answer
B:The correct tool schema can still cause damage when its endpoint is misconfigured; environment segregation must include targets and identity.
Incorrect Answers
A:Behavior changes across model versions are deployment changes; a tested rollout prevents silent production regressions; it changes multi-criterion integration; it does not prove environment endpoint isolation in this case.
C:Dependency compatibility does not establish which environment the application connects to. A connector can pass every schema test while its staging endpoint still points at production.
D:Generated output contracts span both sides of the interface; configuration drift can break consumers even when API calls succeed; the consequence is improved schema release coordination, not verified environment endpoint isolation.
E:Automation runs without the same human supervision as local sessions, so its authority should be explicitly narrower; where environment endpoint isolation matters, a control for environment-specific Claude Code permissions leaves that test unmet.