CCAO-F practice questions: Prompting and task execution.

The prompt "write something about our product" produced a vague result. What improves it most?

• Pasting the full product spec sheet and asking for a write-up that covers everything in it
• Telling Claude the result was vague and asking it to try again with more concrete detail
• Adding the audience, purpose, format, length, and an example of the tone you want
• Asking Claude to write three versions so you can pick the one closest to what you had in mind

The first draft is close but not right. What is the efficient next step?

• Start a fresh conversation and rewrite the prompt with the lessons from the first attempt
• Edit the draft by hand, since explaining the changes takes longer than making them
• Ask for ten alternative drafts and combine the best paragraphs from each yourself
• Give specific feedback on what to change and iterate on the same draft

Which prompt is most likely to produce a usable customer apology email?

• 'Draft a customer apology email. Use our standard tone. Include a credit. Do not make it too long.'
• 'Write an apology to a customer for a late order. Keep it professional and make sure they feel heard.'
• 'Write a 120-word apology to a customer whose order arrived a week late, warm but not groveling, offering a 15% credit; here is our tone guide.'
• 'Write a sincere apology for a shipping delay from a customer service manager, with a goodwill gesture.'

You want three distinct options rather than three variations of one idea. What do you say?

• 'Give me three options and make sure they are genuinely different from each other, not variations'
• 'Give me three options that differ in approach, for example one conservative, one bold, one unconventional'
• 'Give me three options. Be as creative as possible and avoid repeating yourself across them.'
• 'Give me three options, then rank them by how creative each one is so I can see the range'

Claude's draft uses jargon your audience will not understand. Best fix?

• Tell it the audience and ask for plain language with an example of the level you want
• Replace the jargon yourself before sending, since you know the audience best
• Ask it to add a glossary at the end so readers can look up the terms they do not know
• Ask for a shorter draft, since cutting length usually forces out the technical terms

What is the value of giving Claude the raw material (notes, data, previous versions) with your request?

• Grounded requests produce specific, accurate drafts instead of generic ones
• It lets the model learn your company's style for future conversations
• It shortens the conversation, since Claude can skip the clarifying questions
• It lets Claude verify its own claims against your documents before answering

When a task is large, what approach works better?

• Start with the hardest section so the remaining ones can follow its pattern
• Break it into steps: outline first, then sections, reviewing between steps
• Ask for the full deliverable twice and merge the stronger parts of each version
• Write one detailed prompt that covers every section so the output is consistent

Claude keeps adding a closing paragraph you do not want. What is the efficient instruction?

• 'Rewrite this without the fluff at the end'
• 'Keep it brief and skip anything that is not essential'
• 'End after the final bullet; do not add a closing paragraph'
• 'Match the length of the previous version exactly'