Acquia Site Builder D10 study guide
Acquia Site Builder D10 · Work through your exam, one topic at a time.
The Acquia Certified Site Builder is one of the Drupal-track credentials in Acquia's certification program, which Acquia describes as validating and promoting expertise in Drupal and Acquia products for developers, agencies, and customers. It sits alongside the Acquia Certified Developer, Front End Specialist, and Back End Specialist exams, and Acquia lists it as available in English, Japanese, French, and Spanish. The credential is aimed at people who assemble and configure Drupal sites rather than write custom modules: building content types and fields, arranging displays and layouts, configuring site settings, and moving configuration and content between environments. Exams are delivered with online proctors on Acquia Academy through Acquia's testing partner, ProctorU, and passing candidates see their score on screen and can download a certificate from Acquia Academy, with a badge and profile available through the Certification Registry. Topics on this exam: Drupal 10 site building (content structures, configuration, and layout) and Content and configuration management. The Acquia Site Builder D10 study guide has 2 sections and about 598 words.
01Drupal 10 Site Building: Content Structures, Configuration, and Layout
Site building in Drupal 10 rests on entities. Content types, vocabularies, and users are bundles of base entities (node, taxonomy term, user). Fields are attached to bundles through the Field UI and stored as field storage plus field instance configuration. Understand the distinction: field storage (shared across bundles) versus field instance (per-bundle widget and display settings).
317 words, about 2 min02Content and Configuration Management
Drupal separates content (nodes, terms, users, files) from configuration (YAML objects such as content types, views, and fields). Configuration management moves config between environments using export/import, typically with drush config:export and drush config:import , backed by a sync directory. Content is migrated separately with modules or Drush, not by config sync. Make changes in a development environment, export config to the sync directory, commit it, then import in staging and production.
281 words, about 1 min