Why is it good playbook design to create smaller and more focused playbooks? (select all that apply)

Question

Options

• AReduces amount of playbook data stored in each repo.
• BReduce large complex playbooks which become difficult to maintain.
• CEncourages code reuse in a more compartmentalized form.
• DTo avoid duplication of code across multiple playbooks.

• A
  12% (4)
• B
  88% (30)

Explanation

Smaller, focused playbooks reduce complexity and improve maintainability (B) because large monolithic playbooks become tangled, hard to debug, and risky to modify. They encourage reuse (C) by making individual playbooks importable components that other playbooks can call, and they eliminate code duplication (D) because a shared, focused playbook becomes the single source of truth instead of copy-pasted logic spread across many files.

Why A is wrong: Storage size is not a meaningful design concern for playbooks - the files are small text, and repos handle them trivially. Good design is driven by maintainability and reuse, not storage optimization.

Memory tip: Think of playbooks like functions in code - small, single-purpose functions are easier to maintain, reuse, and deduplicate than one giant function that does everything. If you remember "good function design = good playbook design," B/C/D follow naturally.

No community discussion yet for this question.