Why Study with PlanetCert?
The Latest Questions
Practice questions and exam topics aligned with the current exam objectives.
Detailed Explanations
Go beyond the answer. Master the material with comprehensive learning and professional explanations for every concept.
AI-Powered Insights
Personalized preparation guidance that adapts to your performance and identifies weak spots automatically.
Exam Information
Official specifications published by Magento
Exam Format
Registration
Validity
Skills this practice test covers
- Build a custom module with registration.php and module.xml, and configure its classes in di.xml.
- Change a public method's behavior with a before, after or around plugin.
- Alter tables with declarative schema and seed records with data patches.
- Place blocks and templates on a page through layout XML and layout handles.
- Add a custom checkout step and customize payment and shipping methods.
- Branch and manage Commerce Cloud environments with the magento-cloud CLI.
Explore related topics
AD0-E717 exam content
9 domains · 28 topics · 41 of 280 questions are written for AD0-E717
Working with Admin
This domain looks at the Admin panel from the developer's side. Candidates explain how the ACL ties roles to resources, and they identify the files and components behind Admin grids, forms, configuration fields and menu items.
Skills tested
- Explain how the ACL links roles to resources, and restrict an Admin page to one role.
- Identify the components used to create or change an Admin grid or form.
- Identify the files that add store configuration fields and Admin menu items.
Official topics
- Access Control and Security
- Admin Configuration
Architecture41 questions
This is the broadest domain: it covers how a module plugs into the platform. It spans di.xml, plugins and observers, controllers and URL rewrites, CLI commands and cron jobs, caching, indexing, translations and the store structure.
Skills tested
- Create a module with the expected file structure, registration.php and module.xml.
- Choose between a plugin, a preference and an event observer for a given change.
- Create a controller, configure its route, and add a custom URL rewrite.
- Add a console command and a cron job, and pick the cache types to clean after a change.
- Set up translations, and describe how websites, stores and store views relate.
Questions by topic
- Performance Optimization7
- Core Concepts3
- Database Schema5
- Asynchronous Operations4
- Indexing2
- Content Management1
- Module Development4
- Dependency Injection7
- Caching4
- Plugins2
- Cloud Services Configuration1
- Web API Development1
EAV/Database
Products and categories keep their attributes in the EAV model, so this domain asks how attributes, attribute sets and entity types work. It also covers changing tables through the database schema and reading data with models, resource models and collections.
Skills tested
- Describe the attribute types and when each one fits.
- Create an attribute and add it to an attribute set and an attribute group.
- Change a table with declarative schema, and add data with a data patch.
- Load and filter records with collections, and save them through resource models.
Official topics
- Entity-Attribute-Value Model
- Database Operations
Layout/UI
This domain is about what shoppers and Admin users see. Candidates edit layout XML, follow how a page renders from its layout handles, build blocks with templates, and configure UI components.
Skills tested
- Add, move or remove a block in a layout XML file.
- Explain the difference between a container and a block.
- Create a block class with its template, and pass data from one to the other.
- Configure a UI component and follow how it renders.
Official topics
- Layout XML Configuration
- Templates and Blocks
- UI Components
Checkout and Sales
This domain follows a purchase from checkout to the finished order. Candidates customize the checkout process, add checkout steps, change payment and shipping methods, and work with orders and other sales entities.
Skills tested
- Add a custom step to the checkout, or change an existing step.
- Customize a payment method or a shipping method.
- Follow an order through its states and statuses.
Official topics
- Checkout Process
- Sales Operations
Catalog
The catalog domain covers product types, categories, prices and stock. Candidates change an existing product type or create a new one, work with the category tree, and implement pricing and inventory logic.
Skills tested
- Change an existing product type, or create a custom product type.
- Work with the category tree and category attributes.
- Implement pricing logic, including special prices.
- Manage stock with multi-source inventory and reservations.
Official topics
- Product Types
- Category Management
- Price and Inventory
Adobe Commerce Cloud Architecture
Adobe Commerce Cloud runs a store as a project with Git branches, environments and services. This domain covers the project's files, permissions and structure, the ways to connect to cloud services, and environment and user management in the web interface.
Skills tested
- Describe what each project file controls, such as .magento.app.yaml, routes.yaml and services.yaml.
- Identify the ways to connect to cloud services such as MySQL, Redis and RabbitMQ.
- Manage environments and cloud users through the web interface.
Official topics
- Cloud Project Structure
- Environment Management
Setup/Configuring Adobe Commerce Cloud
This short domain covers the first setup of a Cloud project. Candidates configure a new project and a local environment so that code builds and deploys as expected.
Skills tested
- Set up and configure a new Adobe Commerce Cloud project.
- Prepare a local environment for work on the cloud project.
- Set deployment configuration with environment variables in .magento.env.yaml.
Official topics
- Initial Setup
Commerce Cloud CLI tool (Managing part)
The last domain covers the magento-cloud CLI. Candidates use it to manage environments and branches, and they know which tasks only the CLI can do.
Skills tested
- Create, branch and rebase environments with the magento-cloud CLI.
- Export the database or take a snapshot from the command line.
- Name the management tasks that need the CLI instead of the web interface.
Official topics
- CLI Operations
Requirements
- No formal prerequisites: anyone can book the exam.
- Recommended: zero to twelve months of hands-on development work on Adobe Commerce.
- Recommended: comfort with the Admin and a basic grasp of Admin development.
- Recommended: working knowledge of the architecture, the EAV model, layout and UI, and checkout and sales.
About the AD0-E717 exam
For developers who extend Adobe Commerce, AD0-E717 checks how the platform is built and where custom code belongs. Its domains cover the Admin, the module architecture, the entity-attribute-value (EAV) database model, layout and UI, checkout and sales, and the catalog. Three more domains deal with Adobe Commerce Cloud: project structure, setup and the CLI tool. Passing earns the Adobe Certified Professional - Adobe Commerce Developer with Cloud Add-on certification.
Commerce Cloud work takes a large share of the PlanetCert practice test, from deploy hooks and environment variables to service errors. Architecture questions come next. The explanations matter most where two answers look close, such as a plugin versus a preference, or the build phase versus the deploy phase. Study Mode suits the Architecture questions, where plugin order and di.xml rules need a slow read. Brainy AI Assistant can trace how a request reaches a controller, or explain why a deployment failed during the build phase.
How to earn the certification
- Earns
- Adobe Certified Professional - Adobe Commerce Developer with Cloud Add-onProfessional
The certification stays valid for two years.
How to prepare for AD0-E717
- 1
Run a local Commerce install
Install Adobe Commerce on a local machine so every objective can be tried by hand. Start with one small module that has a controller, a route and a layout file.
- 2
Follow one request end to end
Trace a storefront request from the front controller through routing and the action class to the layout handles and blocks that render the page. Both the Architecture and Layout/UI domains rest on this flow.
- 3
Try each extension point
Change the same behavior three times: with a plugin, with a preference and with an observer. Note where each one is declared and when it runs, since the Architecture domain asks when each one fits.
- 4
Learn the Cloud project files
Read .magento.app.yaml, .magento.env.yaml, routes.yaml and services.yaml line by line, and learn what the build, deploy and post-deploy stages do. Then practise branching, rebasing and database exports with the magento-cloud CLI.
- 5
Close with a timed run
Take the AD0-E717 practice test in Timed Mode once each domain feels solid. For each missed Cloud or plugin question, ask Brainy AI Assistant which file or setting would have changed the answer.
Start a timed AD0-E717run
Who AD0-E717 is for
- Developers with up to a year on Adobe Commerce who build custom modules for a store.
- Agency and in-house developers who support stores on Adobe Commerce Cloud.
- Back-end developers who change checkout, catalog or Admin behavior for a business.
Typical job titles: Adobe Commerce developer · Magento developer · Back-end developer · E-commerce developer
AD0-E717 glossary
19 terms from the exam objectives and the vendor's official material, each defined in a sentence.
- .magento.app.yaml
- The Commerce Cloud file that sets how the application is built and deployed, including hooks, PHP extensions and cron jobs.
- .magento.env.yaml
- The Commerce Cloud file that sets environment variables for the build, deploy and post-deploy stages.
- ACL (Access Control Lists)
- The tree of Admin resources that each role is allowed or denied, which decides what an Admin user can see and do.
- Attribute sets
- Named groups of attributes that decide which fields a product of that set shows in the Admin.
- Data patches
- Classes that add or change data once, such as creating an attribute, and that the platform records so they do not run twice.
- Declarative schema
- A way to describe a module's database tables in XML, so that the platform creates or changes the tables to match.
- di.xml
- The module file that sets dependency injection rules, such as preferences, plugins and constructor arguments.
- Entity-Attribute-Value Model
- A storage design that keeps each attribute value of an entity, such as a product, in separate value tables, so attributes can be added without new columns.
- Event observers
- Classes that run when a named event is dispatched, so code can react without changing the code that fired the event.
- Interceptors
- Classes that Adobe Commerce generates around a class with plugins, so that the plugin code runs when its methods are called.
- Layout handles
- Names for a page or page type, each tied to a layout XML file of the same name that changes that page.
- magento-cloud CLI
- The command-line tool for Commerce Cloud projects, used for tasks such as branching environments and exporting databases.
- Multi-source inventory
- The inventory system that tracks one product's stock across several sources, such as warehouses or shops.
- Plugins
- Classes that run code before, after or around a public method of another class, without changing that class.
- Preferences
- di.xml entries that tell Adobe Commerce to use one class in place of another, often as the implementation of an interface.
- Reservations
- Records that lower a product's salable quantity when an order is placed, before stock is deducted from a source at shipment.
- Resource models
- Classes that read a model's data from its database table and write it back.
- Scope hierarchy
- The global, website and store view levels at which a setting can be saved, where a lower level overrides a higher one.
- UI Components
- Reusable interface parts, such as Admin grids and forms, that are declared in XML and rendered with JavaScript.