Page and Component Management
Pages are built from components placed into paragraph systems (the responsive grid containers). A component's behavior is defined by its resource type, which maps to an HTL script and a dialog (cq:dialog) or design dialog. Candidates should understand core components (Button, Text, Image, Teaser, Container, Experience Fragment) versus custom components, and know that core components are extensible via the policy system rather than editing code.
Editable templates are central: a template defines the page structure (header, footer, layout container), allowed components, and policies that control component options. Templates are associated with a page via Page Properties. Static templates (older) live under /apps and cannot be edited by authors; editable templates live under /conf and can be modified in the Template Editor. This distinction is a frequent exam trap.
Know Experience Fragments (reusable content blocks that can be exported to other channels) versus Content Fragments (structured, schema-driven data for headless delivery). Mixing these up is a classic distractor. Also know the Layout Container and how responsive grid column resizing works in Layout mode.
Rule of thumb: if a question asks how to restrict which components an author can drop on a page, the answer is a policy on the template's container, not a code change. If it asks how to reuse a hero across pages, use an Experience Fragment.