Skip to course content
Free CrewAI course

CrewAI for Multi-Agent Automation

Module 01 Knowledge Check

5 questions. Pass mark 4 out of 5. Answer every question before checking the answer key below, then retry after reading the feedback.

1. In CrewAI terms, a task is best understood as…

2. The strongest reason to use multiple agents rather than one is…

3. A Flow differs from a Crew mainly in that it…

4. Multi-agent systems most commonly disappoint because…

5. Before building a crew you should first define…

---

Answer Key and Explanations

Check these only after attempting every question.

1. B - A unit of work with a defined expected output

Tasks carry the expected output; agents carry the capability. Confusing the two produces vague results.

2. B - Genuinely distinct roles need different tools, permissions, or context

More agents add coordination overhead and new failure modes. The separation must earn its cost.

3. B - Gives explicit, deterministic control over execution order

Flows are for when you want the sequence decided by you, not inferred at runtime.

4. B - Coordination overhead and looping outweigh the benefit of specialisation

Start with the simplest structure that works and add agents only when a real boundary appears.

5. B - The output you need and how you will judge whether it is acceptable

Without a defined acceptable output, no amount of agent design converges on anything.

Practical Check

Apply this module to your own work: complete the module activity for *CrewAI Concepts: Agents, Tasks, Crews, and Flows*, then write one sentence naming what your result shows and one naming what it does not.

Strong Answer Pattern

A strong answer names the task, the evidence used, the check performed, and the remaining limitation. It avoids "proved", "guaranteed", or "always" unless the evidence genuinely supports it.