AEM Sites Architect Master study materials
AEM Sites Architect Master study resources

AEM Sites Architect Master study plan

AEM Sites Architect Master · Give each week a clear focus.

8 weeks · About 8 hours per week

Week 1

AEM Sites implementation and component architecture

  • Diagram the request-to-render path of an AEM Sites page from Dispatcher through the Sling engine to the client library include

  • Build a working component (HTL, Sling Model, dialog) in a local SDK project and explain each annotation you used

  • Compare Sling Model delegation, inheritance, and interface-based injection patterns and choose one for a multi-component scenario

  • List the component-level responsibilities that belong to the model layer versus the HTL layer and justify each split

Your checkpoint

A one-page architecture diagram of the AEM request/render pipeline plus a working three-component sample project pushed to a personal Git repository

Week 2

AEM Sites implementation and component architecture & Templates, policies, and editable template design

  • Author an editable template with a layout container, policy-mapped allowed components, and at least two responsive breakpoints

  • Explain the difference between static, editable, and experience-fragment-backed templates and when each is appropriate

  • Configure a policy so that one component behaves differently across two template instances without code changes

  • Trace how template structure, policies, and the content tree combine at render time and document the inheritance order

Your checkpoint

Two editable templates sharing one component set but differentiated by policy, with a written explanation of the policy resolution order

Week 3

Solution architecture and requirements analysis & Content modeling, content fragments, and experience fragments

  • Translate a fictional stakeholder brief into a content model with entity types, relationships, and reuse points

  • Model a Content Fragment with nested fragment references and a JSON export consumed by an external client

  • Design an Experience Fragment variation strategy for a multi-locale campaign and justify the variation-versus-copy decision

  • Identify where Content Fragment and Experience Fragment responsibilities overlap and document a boundary rule

Your checkpoint

A content model document covering Content Fragments and Experience Fragments, including a sample GraphQL query and its expected JSON shape

Week 4

Integration, APIs, and headless delivery

  • Implement a headless delivery path using the Content Fragment GraphQL endpoint and a persisted query

  • Compare server-side HTL rendering, Sling Model Exporter JSON, and GraphQL for three delivery scenarios and pick a default

  • Design an integration with an external system using a service user, a dedicated configuration, and idempotent retry handling

  • Document API versioning and error-contract conventions for the integration surface

Your checkpoint

A headless delivery proof of concept with one persisted GraphQL query and one Sling Model Exporter endpoint, plus a short trade-off write-up

Week 5

Performance, caching, and Dispatcher configuration

  • Write Dispatcher rules that allow a specific path while blocking query-string abuse and default GET parameters

  • Configure and verify client library handling, including debug-mode exclusions and long-cache headers for versioned clientlibs

  • Identify the top five caching mistakes in AEM projects and state the correct configuration for each

  • Measure the effect of caching decisions by comparing cold and warm request behavior in a local Dispatcher setup

Your checkpoint

A Dispatcher configuration with annotated filter and cache rules, plus a checklist mapping each rule to the risk it mitigates

Week 6

Cloud Service and on-premise deployment, environments, and DevOps & Security, users, groups, and permissions

  • Map a code and content deployment through Cloud Manager pipelines and describe what each pipeline stage validates

  • Compare Cloud Service and on-premise constraints for run modes, mutable content, and repository size and document the operational differences

  • Design a permission model using groups, ACLs, and a service user that satisfies least privilege for an authoring team and an integration

  • Explain how the immutable-versus-mutable repository split affects deployment and backup strategy

Your checkpoint

A deployment and permissions runbook covering pipeline stages, environment topology, and a group-to-ACL matrix for three personas

Week 7

Migration, upgrade, and multi-site management & Troubleshooting, governance, and best practices

  • Plan a migration of legacy components and content to a current template model, including a rollback checkpoint

  • Design a multi-site structure using language copies, live copies, and MSM rollout configurations and predict inheritance conflicts

  • Build a troubleshooting decision tree for the five most common production symptoms (blank component, stale cache, permission denial, missing clientlib, failed replication)

  • Define a governance checklist for component and template changes that includes review gates and deprecation policy

Your checkpoint

A multi-site and migration plan with an MSM rollout configuration table and a one-page troubleshooting decision tree

Week 8

Solution architecture and requirements analysis & AEM Sites implementation and component architecture & Templates, policies, and editable template design & Content modeling, content fragments, and experience fragments & Integration, APIs, and headless delivery & Cloud Service and on-premise deployment, environments, and DevOps & Performance, caching, and Dispatcher configuration & Security, users, groups, and permissions & Migration, upgrade, and multi-site management & Troubleshooting, governance, and best practices

  • Synthesize all domains into a single end-to-end reference architecture for a fictional global brand site

  • Re-derive the highest-risk decisions from each domain and state the trade-off you would defend in a design review

  • Identify your three weakest sub-topics from prior weeks and close each gap with a written explanation from memory

  • Rehearse articulating architecture decisions aloud within a time limit to simulate a review setting

Your checkpoint

A complete reference architecture document with decision records for at least ten cross-domain trade-offs and a personal gap-closure log

Milestones

Week 2: Can build an editable template with policy-differentiated components from scratch without referring to notes

Week 4: Can explain and demonstrate a headless delivery path end to end and justify it against an HTL alternative

Week 5: Can write Dispatcher filter and cache rules that pass a self-authored abuse checklist

Week 6: Can describe every Cloud Manager pipeline stage and map a permission model to least-privilege groups

Week 8: Can present the full reference architecture and defend ten cross-domain trade-offs from memory