Acquia Back End Specialist (D10) study guide
Acquia Back End Specialist (D10) · Work through your exam, one topic at a time.
The Acquia Certified Drupal 10 Back End Specialist credential is a vendor certification aimed at developers who build and run Drupal 10 sites, covering back end development, site building, theming fundamentals, performance, security, and the Acquia hosting platform with its deployment and environment tooling. This page is an independent study resource, not an official Acquia publication, and it is not affiliated with or endorsed by Acquia. It exists to help you organise preparation and practise the reasoning the exam rewards. Important caveat: the official certification page was unavailable when this page was compiled, so the exam's item count, time limit, passing score, fee, format, retake rules, and validity period are all unconfirmed here and are shown as unknown rather than estimated. Topics on this exam: Drupal 10 back end development (site building, module development, theming, performance, security) and Acquia platform and hosting (Acquia Cloud, deployments, environments, tooling). The Acquia Back End Specialist (D10) study guide has 2 sections and about 806 words.
01Drupal 10 Back End Development: Site Building, Module Development, Theming, Performance, and Security
Back-end questions on Drupal 10 reward precise knowledge of the services and patterns that core itself uses. You should be fluent in the plugin system (annotations replaced by PHP attributes in D10 for many plugin types, with #[Attribute] -based discovery), the entity/field API, dependency injection via .services.yml , and the routing/controller/access stack. Know the difference between a service definition, a service collector, and a tagged service. Understand config vs.
416 words, about 2 min02Acquia Platform and Hosting: Acquia Cloud, Environments, Deployments, and Tooling
Acquia Cloud questions test your mental model of the platform rather than Drupal internals. Know the environment tiers: a Dev environment, one or more Stage environments, and a Prod environment, each with its own database, code branch, and domains. Code moves through a Git-based artifact flow: you push to a branch, and a deployment builds that branch onto the environment's servers. Understand that the codebase is a Composer-managed Drupal project, and that the document root is typically docroot .
390 words, about 2 min