CCDV-F - Applications and Integration (33.1% of the exam) - Section 2.2
Apply systems life cycle management concepts and frameworks to Claude-based systems.
Published skill weight 2.8 percent. Covers the concepts and frameworks used to develop, implement, operate and maintain IT systems, applied to a system that has a model in the middle of it and therefore changes as models and prompts are revised.
systems life cycle managementdevelop, implement, operate, maintainlife cycle frameworks
Practice question for this objective
lock_openFree sampleApplications and Integrationeasy
A retail company plans to replace a manual returns triage process with a Claude-based assistant. Leadership has asked for a defensible answer to whether the project is worth funding, and the team has only a general belief that the assistant will be faster than the existing staff process. Which step belongs at the start of the life cycle, before any build work begins?
ADefine the use case and its success criteria, including the baseline the current manual process achieves and the measurable target the assistant must beat.check_circle Correct
BSelect the model and set its generation parameters first, since the choice of model determines what the assistant is capable of doing for the returns team.
CBuild a Model Context Protocol server exposing the returns database, so that integration work is finished before the assistant's behaviour is designed.
DWrite the production deployment and rollback procedure now, so the operations team can approve the release path well ahead of the first build milestone.
The first life cycle phase defines the use case, its baseline and its measurable success criteria, before any model or integration choice. Every later phase depends on knowing what success means. A measured baseline from the existing manual process plus a target the assistant must beat converts a general belief into a funding decision and gives evaluation, release and operation a shared definition of correct.
Why A is correct: A defined use case with a measured baseline and a target is what makes the funding decision defensible and gives every later phase something concrete to test against.
Why B is wrong: Model selection does bound capability and has to happen eventually, but choosing one before the success criteria exist means there is no bar against which the choice can be judged.
Why C is wrong: An MCP server is the right shape for a reusable integration, but building it first commits engineering effort to a data surface whose requirements have not been established.
Why D is wrong: A rollback procedure is genuinely needed before release, so this feels prudent, but it is a later-phase artefact and cannot answer whether the project should be funded.
Answers that look right on this material and are not. Each one is a distractor from a different question in the CCDV-F bank for this domain.
Raise the model's output token allowance so answers are never truncated during review, and treat a full-length answer as the release signal for each prompt change.
errorWhy it is wrong: Truncation is a real production defect, so this sounds like release hygiene, but a full-length answer says nothing about whether the content regressed against known-good cases.
Freeze the prompt and the model configuration for a further six months so that summary behaviour stays stable while the new clause category is studied by the business.
errorWhy it is wrong: Stability limits the number of variables in play, which is appealing during an investigation, but the input distribution has already shifted, so freezing preserves the failure rather than detecting it.
Publish the new phrasing to all staff at once and ask them to report anything that looks wrong, since the assistant is internal and the audience is cooperative.
errorWhy it is wrong: An internal audience is more forgiving than customers, which makes a full release feel low risk, but it exposes every user at once and leaves detection dependent on reports arriving.