Drupal Site Builder Exam Preparation Material | Acquia Certified Drupal Site Builder Exam for Drupal 10, 11

Explanation:
Drupal’s configuration management system is specifically designed to move site configuration ―such as content types, fields, vocabularies, and Views―between environments by exporting configuration to files and then importing it elsewhere. Drupal documentation explicitly describes configuration as the administrative settings that determine how the site functions, and it lists fields and views as examples of configuration.
That makes option D the correct workflow: build the new fields and View on a development copy of the site, export the configuration to code, deploy that code to staging, import it for QA review, and then repeat the import in production after approval. This preserves live editorial activity such as comments , because comments are site content , not configuration, and configuration deployment avoids overwriting production content with a copied database.
Option A is risky because copying the staging database back to production could overwrite live comments and other newly created production content.
Option B is false because staging and production do not automatically share configuration through one database in a normal deployment workflow.
Option C is inferior because configuration should be created from a development copy of the actual site, where the existing modules, schema, and site setup already match the target environments.

Explanation:
Drupal handles date and time display through regional settings and user account timezone preferences , not through content type configuration. The correct solutions are therefore A and C. Enabling “Users may set their own time zone” allows authenticated users to choose their own timezone in their user account settings, so dates such as content publication times are displayed according to each user’s local timezone. This is the most accurate solution when users may come from different regions.
Changing the default timezone to that of your primary audience, in this case France, is also correct. Drupal uses the site default timezone for users who have not set a personal timezone, and for anonymous visitors. This makes displayed times more appropriate for the majority of site visitors.
Option B is incorrect because Drupal does not provide timezone handling at the content type level. Timezone behavior is managed globally and per user, not per content type.
Option D is also incorrect because setting the default country affects address-related defaults and locale-related behavior, but it does not control how Drupal displays timestamps. Therefore, the verified answers are A and C.

Explanation:
Drupal uses text formats and filters to control how HTML input is processed before being displayed. One of the available filters is “Correct faulty and chopped off HTML” , which is specifically designed to fix improperly formatted or broken HTML markup.
According to Drupal documentation, this filter ensures that HTML pasted into editors (like CKEditor) is automatically cleaned and corrected , such as closing unclosed tags, fixing malformed markup, and preventing rendering issues. This is particularly useful when users paste HTML from external sources, which often includes inconsistent or invalid markup.
Option D is correct because it directly addresses the issue at the text format level without restricting allowed tags, maintaining the requirement to allow all HTML elements.
Option C is incorrect because enabling “Limit allowed HTML tags” would restrict HTML usage, which contradicts the requirement to allow all elements.
Options A and B are not standard Drupal solutions and do not align with Drupal’s built-in filtering system.
Therefore, enabling the Correct faulty and chopped off HTML filter is the correct and recommended approach in Drupal 10 and Drupal 11.

Explanation:
The correct answer is D. Drupal core’s Layout Builder is specifically designed to let site builders create different display layouts for different bundles, including content types such as Page and Article. The official Layout Builder documentation explains that it can be used to create layouts for content types and other entity types, and that layout defaults apply to all items of a given bundle. That matches this scenario exactly: one content type needs a default three-column layout and another needs a default two-column layout.
Option B is not the best answer because the extra setting “Allow each content item to have its layout customized” enables layout overrides for individual nodes. The question asks for different layouts by content type , not per individual content item, so overrides are unnecessary. Drupal documentation states that layout overrides are optional and are only needed when each entity may differ from the bundle default.
Option A is incorrect because field grouping and theme styling are not the Drupal core mechanism for bundle-level visual page layouts.
Option C is also incorrect because content types are not assigned page layouts during field creation. In Drupal core, this is handled later through Manage display with Layout Builder enabled for each content type.

Explanation:
Drupal core search does not index newly created or updated content immediately in the default workflow. According to the official Drupal core Search module overview , content actions such as creating, editing, or deleting content automatically mark the affected content items for indexing or reindexing at the next cron run. Until cron runs, the new or changed content is not updated in the search index, so a newly created article may not appear in search results even though search is otherwise functioning correctly.
This makes option C the correct answer. The other options do not match Drupal core behavior. There is no normal site-building step where you configure core search to “recognize” a specific term, and Drupal does not provide an “Add to search index” checkbox when creating an article in core search. Also, while contributed search solutions exist, the question states that Drupal core search is already working correctly, so the missing result is best explained by indexing timing, not by a flaw requiring another module. Drupal’s search documentation is explicit that cron is responsible for updating the index after content changes.