Free Practice Questions for the Acquia Drupal 10/11 Drupal-Site-Builder Exam (2026 Updated)

Drupal’s issue queue guidelines clearly distinguish between different issue types. A Bug Report is used when existing functionality is broken or not working as intended. In this case, the module is functioning correctly—it simply does not provide a UI—so option A is incorrect.

A Feature Request is the correct issue type when asking for new functionality or enhancements to an existing module. Requesting a web-based UI for a module that currently only provides Drush commands is a classic example of a feature enhancement, making option C correct.

Option B (“Plan”) is typically used for outlining larger initiatives or coordinated development efforts, not for requesting a specific feature. Option D is incorrect because Drupal issue queue best practices emphasize clear, descriptive, and professional issue titles , avoiding urgency or misleading wording like “Module Broken!!!” when it is not actually broken.

Drupal.org documentation encourages contributors to categorize issues properly and write clear, concise summaries so maintainers and the community can effectively review and respond. Therefore, submitting a Feature Request with a clear subject line is the correct and recommended approach.

Drupal core provides a specific setting for whether node add/edit forms should use the administration theme. On the Appearance page, this is the checkbox labeled “Use the administration theme when editing or creating content” . When that setting is enabled, content creation and editing routes are treated as admin-theme routes; when it is disabled, those forms use the site’s default front-end theme instead, while the rest of the administration area can still use the admin theme such as Claro. This behavior is implemented in core through the node.settings configuration value use_admin_theme and the node route subscriber that marks node operation routes as admin routes only when that setting is turned on.

That makes option A correct. Option B would not solve the requirement, because setting the admin theme as the default theme would affect the whole site’s front-end presentation. Options C and D are incorrect because Drupal does not use a role permission like “View Admin Theme” to control this behavior for node edit pages. The documented control for this requirement is the Appearance-page checkbox tied to node.settings.use_admin_theme .

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’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 10 and Drupal 11 recommend using entity references and view modes to display structured entity data (like users) within other entities such as blocks. The requirement is to display a selected user (employee) with their name and picture and allow editors to choose which user appears in the block through the block editing UI.

Option D follows Drupal best practices. First, you create a custom view mode for users (e.g., “Star Performer”) and configure it to display only the necessary fields such as user name and profile picture. Then, you create a custom block type with a user reference field , allowing editors to select a specific user. The display of that referenced user can be configured to use the custom view mode, ensuring consistent formatting.

Option B is less suitable because it relies on Views filtering rather than allowing editors to directly select a specific user. Option A depends on a contributed module unnecessarily. Option C is incorrect because Drupal does not provide a default block type for selecting arbitrary user entities in that way.

Thus, using a user reference field with a dedicated view mode is the correct and scalable Drupal solution.

In Drupal 10 and Drupal 11, blocks are placed and managed through the Block Layout system available at Structure → Block layout . Each theme defines regions such as Sidebar, Footer, Header, etc., and administrators can assign blocks to these regions.

Since the “Social share” buttons are implemented as a custom block , the correct approach is to reposition the block using the Block Layout admin interface . This interface allows site builders to move blocks between regions either by dragging or by editing the block’s region setting. This matches Drupal’s documented site-building practice for managing block placement.

Option A is incorrect because Manage display is used for configuring how fields are displayed on entities, not for block placement. Option C is incorrect because the Appearance page controls themes, not individual block placement. Option D is unnecessary because Layout Builder is used for per-content or per-entity layouts, not for globally placed blocks like a social share block.

Therefore, the simplest and correct solution is to move the block via the Block Layout page, making option B correct.

Drupal 10 and Drupal 11 let you control block display through visibility conditions on the block configuration form. Drupal’s block management documentation explains that a block’s visibility can depend on page-specific visibility settings and also on user role conditions. For page visibility, Drupal specifically notes that the front page is an exception and must be entered as <</b> front > . To show a block only on the homepage, you add < front > in the Pages visibility settings and choose “Show for the listed pages.”

To limit the block to a specific audience, you use the Roles visibility condition and select the exact role that should see the block. In this case, that is Premium customer , not the broader Authenticated user role, because selecting Authenticated user would show the block to all logged-in users who have that role, not just premium customers. Drupal core’s block form API also confirms that block visibility is built through configurable visibility conditions in the block UI.

So the correct combination is:

A for the role restriction, and B for the front-page-only restriction.