Question bank
Adobe Experience Manager Sites Architect Master
42 Adobe Experience Manager Sites Architect Master questions with the correct answer and a written explanation, organised across 5 exam domains.
- 42 questions
- 5 domains
- Foundation level
certilumQuestion index
Jump straight to any question. Answers and explanations are inline.
Architecture
11 questions in this domain
- Question 1Single Choice
Which analysis documents the current content production state and the desired automated AEM end state?
- AAs-Is vs. To-Be AnalysisCorrect answer
- BStakeholder Requirement Gathering
- CWorkflow Orchestration
- DBottleneck Identification
Why this is the answer
As-Is vs. To-Be Analysis records the current fragmented content production and the optimized AEM-driven state.
- Question 2Multiple Select
Which of the following are common traps identified when designing AEM architecture?
- AFeature-First ThinkingCorrect answer
- BIgnoring Non-Technical PersonasCorrect answer
- COver-Engineering WorkflowsCorrect answer
- DAs-Is vs. To-Be Analysis
Why this is the answer
Feature-first thinking, ignoring non-technical personas, and over-engineering workflows are traps; gap analysis is a core method.
- Question 3Interactive
In the displayed configuration, which AEM architecture concept is being illustrated?
- AWorkflow OrchestrationCorrect answer
- BGovernance Framework Integration
- CTechnical Constraint Mapping
- DBottleneck Identification
Why this is the answer
The code block maps content movement through create, review, approve, and publish, matching workflow orchestration.
- Question 4Single Choice
Which process identifies persona needs and maps them to AEM features such as Granular Permissions and Experience Fragments?
- AStakeholder Requirement GatheringCorrect answer
- BBottleneck Identification
- CIntegration Viability
- DGovernance Framework Integration
Why this is the answer
Stakeholder Requirement Gathering maps persona needs to AEM features such as Granular Permissions, Workflow Models, and Experience Fragments.
- Question 5Multiple Select
Which AEM features are named as mappings for stakeholder requirements?
- AGranular PermissionsCorrect answer
- BAsset Compute
- CWorkflow ModelsCorrect answer
- DExperience FragmentsCorrect answer
Why this is the answer
Granular Permissions, Workflow Models, and Experience Fragments are listed as AEM features for stakeholder mapping; Asset Compute addresses bottlenecks.
- Question 6Interactive
The code block enforces business rules inside a process. Which architecture concept is illustrated?
- AGovernance Framework IntegrationCorrect answer
- BWorkflow Orchestration
- CCost-Benefit Modeling
- DCloud-Native Oversight
Why this is the answer
Governance Framework Integration embeds business rules and compliance checkpoints directly into the AEM workflow.
- Question 7Single Choice
Which practice focuses on finding points in the content lifecycle where delays occur?
- ABottleneck IdentificationCorrect answer
- BTechnical Constraint Mapping
- CIntegration Viability
- DFeature-First Thinking
Why this is the answer
Bottleneck Identification finds lifecycle delays and supports AEM solutions such as Asset Compute and automated translation workflows.
- Question 8Multiple Select
Which scenarios are considered when projecting AEM scalability and performance?
- AProjected traffic spikesCorrect answer
- BLarge-scale asset ingestionsCorrect answer
- CDispatcher caching rules
- DOSGi bundle dependencies
Why this is the answer
Scalability projections evaluate traffic spikes and asset ingestion; dispatcher caching and OSGi dependencies are technical constraints.
- Question 9Interactive
Which architecture mapping concept is represented by the constraints in the code block?
- ATechnical Constraint MappingCorrect answer
- BIntegration Viability
- CResource and Skillset Alignment
- DCost-Benefit Modeling
Why this is the answer
Dispatcher cache rules are technical AEM constraints that architects map against client requirements.
- Question 10Single Choice
Which trap selects a custom solution that breaks the AEM upgrade path and increases TCO?
- ACustomization TrapCorrect answer
- BIntegration Fallacy
- CCloud-Native Oversight
- DFeature-First Thinking
Why this is the answer
The customization trap favors full requirement coverage but breaks the upgrade path and increases total cost of ownership.
- Question 11Multiple Select
Which common AEM architecture traps involve requirement prioritization or integration complexity?
- ATreating all requirements as equal priorityCorrect answer
- BIgnoring Non-Functional RequirementsCorrect answer
- CUnderestimating Integration ComplexityCorrect answer
- DPerforming As-Is vs. To-Be Analysis
Why this is the answer
Equal priority, NFR neglect, and integration complexity are common traps; gap analysis is a recommended practice.
Business & Analytics
5 questions in this domain
- Question 12Single Choice
In AEM architecture, what does an As-Is vs. To-Be analysis primarily document?
- AThe current manual state and the optimized automated stateCorrect answer
- BThe server infrastructure specifications
- CThe code deployment pipeline details
- DThe list of AEM product packages
Why this is the answer
As-Is vs. To-Be analysis documents the current fragmented production state and the future AEM-optimized state, validating architecture and migration decisions.
- Question 13Multiple Select
Which of the following are recognized AEM process-mapping traps?
- AFeature-First ThinkingCorrect answer
- BIgnoring Non-Technical PersonasCorrect answer
- COver-Engineering WorkflowsCorrect answer
- DUsing Out-of-the-Box Workflow Models
Why this is the answer
Feature-first thinking, ignoring non-technical personas, and over-engineering workflows are common traps; using OOTB models is not a trap.
- Question 14Interactive
In the workflow logic shown, what term describes the point where a draft item remains delayed until approval?
- ABottleneckCorrect answer
- BIntegration Fallacy
- CTo-Be State
- DWorkflow Orchestration
Why this is the answer
A bottleneck is a point in the content lifecycle where delays occur, such as a draft item waiting for approval.
- Question 15Single Choice
Why is Feature-First Thinking considered a trap in AEM architecture?
- AIt selects a feature before fully understanding the business processCorrect answer
- BIt adds too many approval nodes to the workflow
- CIt focuses only on non-technical personas
- DIt ignores the As-Is documentation
Why this is the answer
Feature-First Thinking attempts to solve a business problem before the business process steps are understood, leading to poor architecture.
- Question 16Multiple Select
Which constraints must an AEM architect map against client requirements?
- ADispatcher caching rulesCorrect answer
- BRepository structure limitsCorrect answer
- COSGi bundle dependenciesCorrect answer
- DMarketing campaign budget
Why this is the answer
Dispatcher rules, repository structure limits, and OSGi dependencies are technical constraints; marketing budget is not an environment constraint.
Deployment & Operations
9 questions in this domain
- Question 17Single Choice
What is the primary purpose of performing an As-Is vs. To-Be analysis in an AEM deployment?
- ADocument current state and design automated targetCorrect answer
- BSelect AEM features before mapping business process
- CList every stakeholder objection to change
- DCompare AEM Managed Services deployment costs
Why this is the answer
The As-Is vs. To-Be analysis documents the current manual or fragmented state and designs the optimized, automated AEM target state to justify architecture decisions.
- Question 18Multiple Select
Which personas should be included when gathering stakeholder requirements for an AEM content production solution? Select all that apply.
- AAuthorsCorrect answer
- BApproversCorrect answer
- CAdministratorsCorrect answer
- DAdobe support staff
Why this is the answer
Stakeholder requirements must include Authors, Approvers, and Admins, mapping their needs to features such as granular permissions, workflows, and Experience Fragments.
- Question 19Interactive
Review the approach shown in the code block. Which AEM architecture trap is represented by the order of steps?
- AFeature-First ThinkingCorrect answer
- BIgnoring Non-Technical Personas
- COver-Engineering Workflows
- DThe Customization Trap
Why this is the answer
Choosing AEM Workflow before fully understanding the business process exemplifies Feature-First Thinking, a common trap identified in the playbook.
- Question 20Single Choice
What is the main purpose of workflow orchestration in Adobe Experience Manager?
- AMap logical steps, decision nodes, and triggersCorrect answer
- BEstablish Dispatcher caching rules
- CDefine OSGi bundle dependencies
- DCreate custom repository structures
Why this is the answer
Workflow orchestration maps how content moves through creation, review, translation, and activation, including logical steps, decision nodes, and automated triggers.
- Question 21Multiple Select
Which practices are examples of integrating governance into an AEM workflow? Select all that apply.
- AEmbed brand consistency checkpoints in workflow stepsCorrect answer
- BEnforce legal requirements in AEM workflow nodesCorrect answer
- CUse external manual spreadsheets for compliance
- DDocument governance rules outside AEM
Why this is the answer
Governance framework integration embeds brand and legal checkpoints directly into AEM workflows rather than relying on external manual compliance checks.
- Question 22Interactive
Review the workflow stages in the code block. Which two concerns best characterize this design?
- AThe workflow is over-engineeredCorrect answer
- BExcessive friction slows content velocityCorrect answer
- CContent velocity will improve
- DUnnecessary approval nodes are reduced
Why this is the answer
Mapping too many approval nodes creates excessive friction and slows content velocity, a clear sign of an over-engineered workflow.
- Question 23Single Choice
What does technical constraint mapping identify in an AEM environment?
- ADispatcher caching rules, repository limits, OSGi dependenciesCorrect answer
- BMarketing budget and campaign timeline
- CAuthor interface visual preferences
- DExternal API vendor pricing
Why this is the answer
Technical constraint mapping identifies AEM limitations such as Dispatcher caching rules, repository structure limits, and OSGi bundle dependencies.
- Question 24Multiple Select
Which factors should be evaluated when assessing AEM integration viability with an external system? Select all that apply.
- AAPI availabilityCorrect answer
- BLatency impactsCorrect answer
- CTeam office location
- DData synchronization potentialCorrect answer
Why this is the answer
Integration viability includes API availability, latency impacts, and data synchronization potential, especially in headless or hybrid architectures.
- Question 25Interactive
Review the design statement in the code block. Which AEM architecture mistake is being made?
- ACloud-Native OversightCorrect answer
- BThe Customization Trap
- CThe Integration Fallacy
- DFeature-First Thinking
Why this is the answer
Using local file system access is an on-premise pattern that is fundamentally incompatible with AEM as a Cloud Service, representing the Cloud-Native Oversight.
Development
9 questions in this domain
- Question 26Single Choice
In an AEM project, what does the As-Is vs. To-Be analysis primarily document?
- ACurrent and future content production statesCorrect answer
- BHardware inventory lists
- CCustomer browser statistics
- DAdvertising budget forecasts
Why this is the answer
It documents the current manual or fragmented content production state and the optimized automated state within AEM, supporting gap analysis and architectural decisions.
- Question 27Multiple Select
Which of the following are common traps in AEM process mapping? Select all that apply.
- AFeature-First ThinkingCorrect answer
- BIgnoring Non-Technical PersonasCorrect answer
- COver-Engineering WorkflowsCorrect answer
- DFrequent User Testing
Why this is the answer
Feature-first thinking, ignoring non-technical personas, and over-engineering workflows are documented traps; frequent user testing is not.
- Question 28Interactive
Review the code block. Which AEM concept does this process sequence represent?
- AWorkflow OrchestrationCorrect answer
- BDispatcher Caching
- CRepository Design
- DIMS Authentication
Why this is the answer
The block maps logical steps, decision nodes, and automated triggers, which is workflow orchestration.
- Question 29Single Choice
What is the primary goal of integrating a governance framework into AEM workflows?
- ABrand and legal complianceCorrect answer
- BFaster page load times
- CLower infrastructure costs
- DHigher server uptime
Why this is the answer
Governance integration embeds business rules and compliance checkpoints so brand consistency and legal requirements are enforced automatically.
- Question 30Multiple Select
Which items are AEM technical constraints an architect should map? Select all that apply.
- ADispatcher caching rulesCorrect answer
- BRepository structure limitsCorrect answer
- COSGi bundle dependenciesCorrect answer
- DExternal brand color palette
Why this is the answer
Dispatcher caching, repository limits, and OSGi bundles are technical constraints; brand colors are not AEM technical constraints.
- Question 31Interactive
The code block shows delays caused by manual hand-offs. Which analytical practice identifies these problem points?
- ABottleneck IdentificationCorrect answer
- BResource and Skillset Alignment
- CCost-Benefit Modeling
- DIntegration Viability
Why this is the answer
Bottleneck identification finds delays like manual hand-offs and asset unavailability to propose solutions such as automation.
- Question 32Single Choice
What should an architect assess when evaluating integration viability with external systems?
- AAPI availability and latencyCorrect answer
- BBrand color consistency
- COffice furniture procurement
- DEmployee holiday schedules
Why this is the answer
Architects must assess API availability, latency impacts, and data synchronization issues in headless or hybrid architectures.
- Question 33Multiple Select
Which elements are part of scalability and performance projections for an AEM architecture? Select all that apply.
- ADeployment strategyCorrect answer
- BProjected traffic spikesCorrect answer
- CLarge-scale asset ingestionsCorrect answer
- DLocal office hours
Why this is the answer
Architects must evaluate deployment strategy, traffic spikes, and large-scale asset ingestion to avoid degrading authoring or delivery.
- Question 34Interactive
The code block uses a local file system pattern. Which AEM trap does this represent?
- ACloud-Native OversightCorrect answer
- BIntegration Fallacy
- CCustomization Trap
- DFeature-First Thinking
Why this is the answer
Local file system access is incompatible with AEM as a Cloud Service, making this a cloud-native oversight.
Discovery
8 questions in this domain
- Question 35Single Choice
What is the primary purpose of an As-Is vs. To-Be analysis in the Discovery phase?
- ADocumenting current state and designing optimized AEM stateCorrect answer
- BSelecting AEM features before understanding processes
- CBuilding custom components to meet all requirements
- DMigrating content without a defined architecture
Why this is the answer
As-Is vs. To-Be analysis records the current fragmented production process and maps it to an optimized automated AEM workflow, forming the basis for architectural decisions.
- Question 36Multiple Select
Which stakeholder personas are explicitly named in the Discovery phase for requirement gathering?
- AAuthorsCorrect answer
- BApproversCorrect answer
- CAdminsCorrect answer
- DExternal Customers
Why this is the answer
The playbook lists Authors, Approvers, and Admins as the personas whose requirements are mapped to AEM capabilities such as permissions, workflows, and Experience Fragments.
- Question 37Interactive
Reviewing the workflow snippet, which missing step is most consistent with AEM Workflow Orchestration?
- AApproval by designated reviewerCorrect answer
- BDelete old content
- CDisable dispatcher cache
- DCreate user groups
Why this is the answer
Workflow orchestration maps logical steps and decision nodes; in the playbook, content passes through creation, review, translation, and activation, with review/approval as a central stage.
- Question 38Single Choice
In content lifecycle analysis, what is bottleneck identification used to find?
- APoints where delays occur in content productionCorrect answer
- BAreas where AEM features should be removed
- CLocations where code can be reused
- DMethods for reducing user training
Why this is the answer
Bottleneck identification finds points in the content lifecycle where delays occur, such as manual hand-offs or missing assets, so AEM solutions like automation and translation workflows can be proposed.
- Question 39Multiple Select
Which of the following are explicitly listed as traps to avoid when mapping AEM business processes?
- AFeature-First ThinkingCorrect answer
- BIgnoring Non-Technical PersonasCorrect answer
- COver-Engineering WorkflowsCorrect answer
- DDeploying to AEM as a Cloud Service
Why this is the answer
The playbook labels Feature-First Thinking, Ignoring Non-Technical Personas, and Over-Engineering Workflows as process traps. Deploying to Cloud Service is not listed as a process trap.
- Question 40Interactive
Based on the coded governance requirements, which AEM feature should be mapped to ensure automated enforcement?
- AWorkflow models with approval and compliance checkpointsCorrect answer
- BDispatcher cache invalidation rules
- CContent Fragment structures
- DOSGi bundle configuration only
Why this is the answer
Governance Framework Integration requires business rules and compliance checkpoints to be enforced automatically; AEM Workflows provide the technical mechanism to ensure legal review and brand consistency are applied.
- Question 41Single Choice
What is the purpose of Technical Constraint Mapping in the AEM Discovery phase?
- AIdentify environment limitations that shape designCorrect answer
- BDefine the client's content taxonomy
- CChoose AEM features without considering process
- DDocument user acceptance tests
Why this is the answer
Technical Constraint Mapping identifies AEM limitations such as Dispatcher caching, repository limits, and OSGi dependencies so the implementation design prevents architectural bottlenecks.
- Question 42Multiple Select
Which items are named as technical constraints that AEM architects must map against client requirements?
- ADispatcher caching rulesCorrect answer
- BRepository structure limitsCorrect answer
- COSGi bundle dependenciesCorrect answer
- DExperience Fragments
Why this is the answer
The playbook specifically mentions Dispatcher caching rules, repository structure limits, and OSGi bundle dependencies as technical constraints an architect must map.
Frequently asked questions
Everything about the Adobe Experience Manager Sites Architect Master question bank and how to use it.