Acquia Acquia Certified Drupal Site Builder Exam for Drupal 10, 11 Drupal-Site-Builder Exam Dumps: Updated Questions & Answers (April 2026)

In Drupal 10 and Drupal 11, block placement is defined per theme . The Block Layout documentation explains that when placing a block, you are assigning it to a region in a specific theme , not globally for all themes. So when you switch the site’s default theme, the new theme may have a different set of regions or different region names, and block placements from the previous theme may no longer map correctly.

Drupal’s theming documentation is even more explicit: if a theme does not define a region that blocks were assigned to, those blocks are treated as assigned to an invalid region and are disabled . The Block module documentation also states that disabled blocks (blocks not assigned to any region in your theme) are never shown . This is exactly why blocks can appear to “disappear” after changing themes.

The other options do not match Drupal’s documented behavior. Blocks do not need to be “registered” with a theme in this sense, contributed themes are not limited to system blocks, and custom blocks generally do not need to be recreated just because the theme changed. The issue is the theme-specific region mapping , which makes D the correct answer.

In Drupal 10 and Drupal 11, favicon settings are managed at the theme level , not through general site configuration. The official Drupal theming documentation explains that each theme has its own configurable settings, including the ability to upload or replace the site’s favicon.

To change the favicon, you navigate to Appearance → Settings (or specifically the active theme’s settings page), where you will find an option to upload a custom favicon or use the default. This allows you to replace the default Drupal icon (Druplicon) with your organization’s icon.

Option A is incorrect because the Site branding block controls elements like the logo and site name, not the favicon. Option C is incorrect because Basic Site Settings does not manage favicon configuration in modern Drupal versions. Option D is unnecessary and incorrect, as CSS is not used to change favicons.

Therefore, the correct and documented method is to update the favicon through the theme settings in the Appearance section , making option B correct.

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 .

Drupal 10 and Drupal 11 provide block visibility conditions that allow administrators to control where blocks appear. According to Drupal’s block system documentation, when placing a block through Structure → Block layout , you can configure visibility based on content types, pages, roles, or request paths .

To meet the requirement of showing the "Recent content" block only on Article pages, the correct approach is to place the block in the Sidebar region and configure its visibility condition to Content types → Article . This ensures the block is displayed only when viewing nodes of the Article content type and hidden elsewhere.

Option A is incorrect because using CSS to hide blocks is not a proper Drupal configuration and still renders the block unnecessarily. Options B and C are invalid because Drupal does not provide such settings in content type or site branding configurations.

Thus, using block visibility settings tied to the Article content type is the correct and recommended method in Drupal site building.

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.

In Drupal 10 and Drupal 11, a module can appear on the Extend page but still have its checkbox unavailable when Drupal determines that its requirements are not met. One of the most common and documented reasons is missing dependencies . Drupal modules declare dependencies in their .info.yml file, and if one or more required modules are not present or enabled, Drupal prevents installation until those dependencies are satisfied. Drupal’s module documentation specifically notes that when a module is listed on admin/modules but its checkbox is disabled, you should verify compatibility and requirements declared in the module metadata.

Option D fits Drupal’s standard dependency behavior. This is also consistent with Drupal community documentation explaining that if you cannot check a module or feature on the module listing page, it is most likely because required dependent modules are missing, and unmet dependencies should be checked first.

The other options are not the correct explanation here. modules/contrib is a valid and standard location for contributed modules, and downloading a module outside the Drupal UI does not itself disable installation. A missing permission would typically affect access to the page or action availability, but the classic reason for a disabled module checkbox on the Extend page is unmet dependencies.

Drupal 10 and Drupal 11 provide the Layout Builder module in core, which allows site builders and content editors to control how fields are displayed. There are two levels of control: content type–level layouts and per-content (per-node) layout overrides .

Option A only allows rearranging fields globally for all nodes of that content type, which does not meet the requirement of having different layouts per job posting. Option B involves theming and template overrides, which require developer intervention and are not intended for content editors or HR staff.

Option C enables Layout Builder but only at the content type level, meaning all job openings would share the same layout. This still does not satisfy the requirement for different arrangements per node.

Option D is correct because enabling Layout Builder and allowing each content item to have its layout customized activates the “Allow each content item to have its layout customized” setting. Drupal documentation explains that this allows individual nodes to override the default layout, giving flexibility to rearrange fields differently for each job opening while still using a structured, UI-based approach.

Thus, Layout Builder with per-node customization is the correct solution.

Drupal’s recommended way to let visitors narrow a Views listing by a field value is to add that field as a filter criterion and then expose the filter to site visitors . The core Views documentation explains that filters can be exposed so users can interact with the data shown in the view, instead of hard-coding separate displays or relying on free-text searching.

This question specifically says the recipes are tagged with a curated taxonomy vocabulary of ingredients. Drupal’s User Guide uses Ingredients as an example of a field that should be a taxonomy term reference , because the allowed values come from a managed list that can grow over time. That means the correct filter is the Recipe content type’s Ingredients taxonomy-reference field in the View. Since visitors should be able to choose the ingredients they have on hand, the exposed filter should allow multiple selections .

The other options are not the standard Drupal site-building solution. Separate displays per ingredient do not scale, a combined-text search is not a structured taxonomy filter, and a menu block is navigation rather than a proper Views filter.

Drupal core’s Contact module allows administrators to configure multiple contact forms, each with its own settings. One of the configurable options is the ability to define a redirect path after form submission. This is done within the specific contact form’s configuration, where you can specify the destination page users should be taken to after submitting the form.

Option D is correct because Drupal provides a “Redirect path” setting directly in the contact form configuration , making it possible to send users to a custom page such as a thank-you or confirmation page after submission.

Option A is incorrect because Drupal core already supports this functionality without needing a contributed module like Webform. Option B is incorrect because Site information settings do not control form submission redirects. Option C is not relevant, as redirect behavior is not controlled through user profiles.

Thus, the correct Drupal-native solution is to configure the redirect path within the contact form settings, making D the correct answer.

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.