AEM Sites Architect Master Mock Test 3 — AD0-E117

Question 1

A client wants a clear view of what the site must do. Which document should be created first?

A. A list of server brands B. A marketing calendar C. A functional requirements list traced to business goals D. An invoice template

Question 2

Which finding describes an architecture gap?

A. A logo with a new colour B. Single author instance with no backup or DR plan C. A blog post with a typo D. A new hire on the team

Question 3

Which non-functional requirement is related to data residency?

A. Logo colour must be blue B. Customer data must be stored in a specific region C. Author must use a specific font D. Editor must write in English

Question 4

Which question best uncovers current-state performance problems?

A. What are the slowest pages and when do they occur? B. What is your favourite colour? C. Which browser is installed? D. How many coffee breaks are taken?

Question 5

Which requirement describes recoverability?

A. The number of images per page B. The default language C. The author's preferred editor D. Recovery point and recovery time objectives are defined

Question 6

Which design decision best supports a regulated industry?

A. Audit logging, encryption and access reviews are designed in B. Security added after launch C. No logging D. Shared accounts

Question 7

Which pattern supports independent scaling of author and publish?

A. One combined server B. Publish inside author C. Separate author and publish tiers with their own capacity D. No separation

Question 8

Which design choice supports content reuse between a website and an app?

A. Duplicated copy in each app B. Headless content fragments delivered via API C. Hard-coded strings in the app D. Content inside screenshots

Question 9

Which design approach supports a global rollout?

A. Regional deployments with localised content and shared components B. One region for all users C. Separate code bases per country D. Manual translation at each release

Question 10

What is the best way to design for an integration with an unreliable legacy system?

A. Call it synchronously with no timeout B. Cache responses and use circuit breakers C. Remove the integration D. Ask users to retry manually

Question 11

Which design supports a consistent brand across many sites?

A. Independent styling per site B. Shared design system and component library C. Manual CSS per page D. Screenshots instead of components

Question 12

Which design choice improves the security of published content?

A. Allow direct publish by anyone B. Publish only approved content through a controlled workflow C. Disable approvals D. Share credentials

Question 13

Which requirement is best for an event-driven integration?

A. Idempotent handlers to avoid duplicate processing B. Non-idempotent writes with no checks C. Single-threaded processing only D. No logging

Question 14

Which design approach supports fast experimentation?

A. Changes without measurement B. Editing live content without a plan C. No feature control D. Feature toggles combined with analytics

Question 15

Which design improves the reliability of publishing at scale?

A. Synchronous replication with no monitoring B. No replication C. Asynchronous replication with monitoring of the queue D. Manual copying of files

Question 16

Which approach should be used for role design in a large enterprise?

A. Group-based roles aligned to job functions B. Individual permissions for every user C. One admin for everyone D. No roles

Question 17

Which solution attribute supports disaster recovery?

A. Backups never tested B. No backup retention C. Backups tested with documented restore procedure D. Backups stored only on the author

Question 18

Which design choice reduces the blast radius of a faulty release?

A. Release to all at once B. Release without testing C. Skip rollback plans D. Canary releases to a subset of traffic

Question 19

Which practice reduces the risk when deploying a custom component?

A. Deploy from a laptop B. Skip review C. Edit production directly D. Code review with automated tests in a pipeline

Question 20

A build fails only in the pipeline. Which action helps most?

A. Retry until it passes B. Delete the pipeline C. Compare build environment and dependency versions D. Ignore the failure

Question 21

Which practice supports a smooth handover to the operations team?

A. No documentation B. Tribal knowledge only C. Undocumented deployments D. Runbooks with monitoring and escalation paths

Question 22

Which step should come before a large content import?

A. Import directly into production B. Skip validation C. Delete existing content D. Dry run in staging with validation

Question 23

Which approach resolves a slow author UI?

A. Add more pages B. Review repository size and index health C. Disable indexing permanently D. Restart without analysis

Question 24

Which action should be taken when a workflow step times out?

A. Investigate the step, fix the cause and resume B. Cancel all content C. Publish without approval D. Ignore the timeout

Question 25

Which practice improves quality of a delivered solution?

A. Done when code is merged B. No acceptance criteria C. Skip QA D. Definition of done with test evidence

Question 26

Which practice keeps a solution stable through regular change?

A. Change without notice B. No freeze periods C. Change calendar with freeze windows D. Deploy during peak traffic

Question 27

Which maintenance task reduces security risk over time?

A. Scheduled dependency and certificate updates B. Ignore expiring certificates C. Never update libraries D. Use default passwords

Question 28

Which practice supports capacity planning?

A. Trend analysis of traffic and resource usage B. Guess capacity once C. Ignore growth D. Buy the largest server

Question 29

Which action helps when a new upgrade introduces a regression?

A. Keep the regression B. Rollback to the last known good version C. Remove monitoring D. Blame the users

Question 30

Which practice improves long-term maintainability?

A. Never refactor B. Add shortcuts permanently C. Refactoring technical debt on a planned schedule D. Ignore code quality