AD0-E720: Adobe Commerce Front-End Developer Expert

By Adobe · Browse Mode
About the Exam

Expert-level certification for front-end developers working on Adobe Commerce (Magento) storefronts. It covers themes and layout XML, templates, the front-end build pipeline, JavaScript components and UI components, styling with LESS, and storefront performance. Passing demonstrates practical skill in customising and extending the Adobe Commerce storefront.

Exam Topics

  • Adobe Experience Manager as a Cloud Service33%
  • Adobe Experience Manager Sites33%
  • Adobe Experience Manager Assets34%

How to Use This Practice Exam

  1. Browse — Read each question, select your answer, and reveal the explanation.
  2. Exam Mode — Simulate real exam conditions with a timed session and score report.
  3. Learn Mode — Spaced repetition schedules questions you struggle with for long-term retention.

Download the Full Exam PDF

Get every question and answer in a clean, printable PDF built for offline study. Purchase once, keep permanent access, and re-download the latest version anytime.

Get PDF
Learn More

Last updated November 28, 2025 at 9:43 AM

Topic filter
Retired questions
Question sort
Questions per page

QuestionQ1

Adobe Experience Manager Sites

An Adobe Commerce developer is extending a theme from Magento\blank and needs to override the parent theme’s styles.

Which file must the developer change to override the parent theme styles?

Explanation

In an Adobe Commerce theme that inherits from Magento/blank, web/css/source/_theme.less overrides the parent theme’s _theme.less variables. The _extend.less file is used to add or extend styles rather than replace the parent theme’s variable definitions.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ2

Adobe Experience Manager Sites

An Adobe Commerce developer needs to override the template assigned to a block named existing.product.block. This relationship is defined in the catalog_product_view.xml layout of the Magento_Catalog module. They cannot merely override the file in their theme because the change belongs to a feature being released to the marketplace as a module named Orange_CustomProduct.

The developer has already created the required template at app/code/Orange/CustomProduct/view/frontend/templates/custom-product-block.phtml.

What can they add to app/code/Orange/CustomProduct/view/frontend/layout/catalog_product_view.xml in their module to achieve this?

Explanation

A referenceBlock targets the existing block, and an arguments node containing a string argument named template assigns its template declaratively. The identifier Orange_CustomProduct::custom-product-block.phtml resolves to the module’s view/frontend/templates/custom-product-block.phtml file. Adobe Commerce documents the template argument as a supported way to set a block template and recommends arguments over an <action> call when the block API permits it.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ3

Adobe Experience Manager Sites

In which directory can a custom theme favicon be added?

Explanation

For Magento Open Source, a custom favicon.ico that overrides the default favicon belongs in <your_theme_dir>/Magento_Theme/web/.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ4

Adobe Experience Manager Sites

An Adobe Commerce developer is creating the Vendor/Orange theme and must customize the header used by email templates.

Where in the theme must the developer place the new template for this customization?

Explanation

Theme-based email-template overrides are placed in <theme_dir>/<ModuleVendorName>_<ModuleName>/email. The default header template belongs to Magento_Email and is view/frontend/email/header.html, so its theme override is Magento_Email/email/header.html.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ5

Adobe Experience Manager Sites

Which two actions are necessary to delete a manually installed theme?

Choose two
Explanation

A manually installed, non-Composer theme must have its code removed from app/design/frontend/<VendorName>/<ThemeName> and its corresponding registration removed from the theme database table. The theme:uninstall command is for Composer-packaged themes, while disabling a theme does not remove its code or database record.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

That's the end of the preview

It's free

100% of the questions are free for all users.
No strings attached.

Sign up freeLog in
Topics covered
Adobe Experience Manager as a Cloud ServiceAdobe Experience Manager SitesAdobe Experience Manager Assets
Know a question that should be here? Contribute to this exam
Back home