Adobe Commerce Developer Professional study plan

Trace a request through the Adobe Commerce bootstrap sequence from index.php through the front controller to layout rendering, writing out each stage in your own notes

Diagram how dependency injection, the object manager, and di.xml preferences/interceptors wire classes together

Explain the module load order (app/etc/config.php, module.xml sequence) and predict which module's di.xml wins

Identify the roles of the major directory roots (app/code, app/etc, lib/internal, pub, var, generated) and what belongs in each

Build a minimal custom module from scratch with registration.php, module.xml, and a routes.xml frontend route

Add a controller, block, and template that render a page and verify it loads at its route

Write a plugin (before/around/after) and an observer for a core event, then confirm both fire by logging

Declare a preference in di.xml to swap a core interface implementation and verify the swap

Create a module that adds a new table via declarative schema (db_schema.xml) and a Setup Patch for data

Expose the module's data through a repository, interface, and web API (webapi.xml) and query it with curl

Add a CLI command and a cron job to the module and run both

Add system.xml configuration and read it back through ScopeConfigInterface with a config.xml default

Write raw SQL against a scratch database to inspect core tables and map how an entity's data spreads across entity tables and EAV tables

Describe the EAV model (entity, attribute, value tables, backend/frontend/source models) and trace where a product attribute value is stored for each backend type

Create a custom EAV entity type with setup code and store/load a record through it

Use the collection API with filters, joins, and pagination and compare the generated SQL to hand-written SQL

Install Adobe Commerce locally from Composer and configure the database, search engine, cache, and message queue

Switch between developer, default, and production modes and record the behavioral differences you observe in static files, caching, and error output

Run the indexers, cron, and cache flush commands and explain what each does

Practice safe data manipulation: import/export products and customers and verify results in the database

Create a custom theme with theme.xml, registration, and a parent inheritance chain and apply it in admin

Override a layout XML file and a template in the theme and confirm the override takes precedence without touching core

Add and position blocks using layout XML (referenceBlock, referenceContainer, arguments) and verify order in the rendered page

Configure a store view, locale, and design exception and confirm the theme applies per store scope

Build a UI component grid and form for your module's data and wire it to the repository from week 3

Add Knockout-based frontend behavior to a template and verify it with the JS bundling/requirejs config

Create a page builder or widget type that renders configurable content

Audit your module for extension best practices: no core edits, plugins over rewrites, declarative schema, and proper ACL

Take two full-length practice exams under timed conditions and log every missed question by domain

Re-study the two weakest domains using your week 1-7 notes and rerun targeted practice sets

Recite from memory the key architecture, EAV, layout, and configuration facts you flagged as shaky

Restate each domain's exam weighting and your confidence level against it