An analyst is working in a long Claude conversation. The conversation contains roughly 60 turns covering an initial requirements analysis, several rounds of data review, and a current drafting phase. Recent responses have started to drift from the agreed requirements.
Which step most directly addresses the drift while preserving the analyst's progress?

• A. Move the source data and requirements into a Project knowledge base, then continue the drafting work in a new chat inside that Project.
• B. Open a new chat and paste only the current draft, then continue refining it there without the prior requirements and data-review context.
• C. Summarize the agreed requirements, key data findings, and current draft state, then continue in the same chat by reasserting the summary as the working context.
• D. Switch the conversation to a model with a larger context window so the accumulated history no longer causes drift, and continue without restructuring the inputs.

A business analyst has been asked to use Claude to extract requirements from a recorded stakeholder interview transcript. The transcript is approximately 90 minutes long and covers multiple topics.
Which approach is most likely to produce a usable structured output?

• A. Provide the transcript and ask Claude to produce a chronological list of every statement that contains a verb, then classify each statement as a requirement or not.
• B. Provide the transcript and ask Claude to produce a single ranked list of requirements, since a single list is easier for stakeholders to review than separate sections.
• C. Provide the transcript and ask Claude to summarize it; extract requirements from the summary in a second pass since two passes catch more detail.
• D. Provide the transcript along with a structured prompt that requests must-haves, nice-to-haves, open questions, and conflicts as separate sections.

You are a project manager working through a long planning conversation with Claude and must keep the conversation productive as it grows.
Which two practices keep a long planning conversation productive? (Select two.) Each correct answer presents a complete solution.

• A. Avoid summarizing so the model retains every original word it has produced.
• B. Switch context aggressively between unrelated planning topics within one thread.
• C. Open a new thread for every minor follow-up question to keep threads short.
• D. Periodically summarize decisions made so far to compress the working state.
• E. Restate constraints and goals when the focus shifts to a new subtopic.

A learning specialist is configuring a Claude Project for a recurring course-design workflow.
Which configuration approach best leverages a Skill alongside other Project elements?

• A. Configure the Project with custom instructions that contradict the Skill ' s documented purpose, creating ambiguity about which guidance Claude should follow within the recurring course-design workflow.
• B. Add the Skill to the Project but omit the supporting knowledge sources and any custom instructions, so the Project lacks the reference content and persistent guidance the workflow requires.
• C. Add the relevant Skill to the Project, upload the supporting knowledge sources, and write custom instructions that reference both the Skill and the knowledge.
• D. Upload the supporting knowledge sources but disable the relevant Skill, eliminating the packaged capability the workflow needs and forcing each chat to reconstruct the procedure manually.

You are an operations lead evaluating prompting strategies that teammates have proposed for various task types.
Which two strategies represent appropriate matches between strategy and task type? (Select two.) Each correct answer presents part of the solution.

• A. rigid templated prompting for early-stage creative naming and tagline ideation
• B. open exploratory prompting for early-stage strategic brainstorming on a new market
• C. open exploratory prompting for legal contract redlining against a clause library
• D. rigid templated prompting for monthly compliance reports against a fixed schema
• E. rigid templated prompting for casual customer-feedback summarization with no schema