Drupal-Site-Builder Exam Dumps - Acquia Drupal 10/11 Questions and Answers

In Drupal 10 and Drupal 11, content translation is handled through the Content Translation module , which allows you to translate individual content entities (such as nodes). Once multilingual support is enabled and a new language (Spanish) is added, each piece of content provides a Translate tab where translations can be created and managed.

Drupal’s User Guide explains that to translate existing content, you navigate to the content item and use the Translate tab to add a translation in the desired language. This process allows editors to manually enter translated content for each field, ensuring accuracy and proper localization.

Option B is incorrect because Drupal core does not provide automatic Google translation import functionality. Option C refers to interface translation (.po files), which is used for translating the Drupal UI, not site content. Option D is incorrect because Drupal does not provide a bulk “Import Translations” action for node content in this manner.

Therefore, the correct and documented approach is to manually add translations via the Translate tab for each content item, making A the correct answer.

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 are flexible because they provide major site-building capabilities through configuration and core modules, instead of requiring everything to be custom-coded. Drupal supports headless/decoupled use cases out of the box through core web services such as JSON:API , which Drupal documentation describes as a standard way to expose site content for decoupled applications. That makes A correct.

Drupal also provides strong content modeling through entity types and fields, and it supports listing and displaying content through the Views UI . The User Guide and core documentation explain that site builders can define structured content types and then create listings, pages, blocks, sorting, and filtering through Views without writing custom code. That makes B correct.

Drupal additionally ships with a rich administrative interface for installing modules, managing themes, creating content types, editing fields, configuring permissions, and administering content. This is one of the platform’s core strengths compared with a purely custom-built system, so E is correct.

Options C and D are not correct. Drupal.org provides contributed projects, but not an online store for buying modules and themes, and Drupal does not present direct database-column renaming as a normal UI-based site-building feature.

In Drupal 10 (Standard installation profile), several roles are created automatically to support common editorial workflows. These include Authenticated user , Content editor , and Administrator .

Authenticated user is a core default role in all Drupal installations. It represents any logged-in user and is always present.

Content editor is provided by the Standard installation profile as part of Drupal’s out-of-the-box editorial workflow, allowing users to create and manage content.

Administrator is also included and has full permissions to manage the entire site.

Options A (Site builder) and C (Publisher) are not default roles created by Drupal core or the Standard profile. While such roles can be created manually or may appear in specific distributions, they are not included by default.

Drupal’s documentation for installation profiles confirms that the Standard profile provides a pre-configured editorial setup, including roles like Content editor, in addition to the core Authenticated user and Administrator roles.

Therefore, the correct answers are B, D, and E .

In Drupal 10 and Drupal 11, user accounts are fieldable entities , which means you can add custom fields directly to user accounts through the administrative UI. Drupal’s field documentation explains that fields can be added to various entity types, including users , not just content types. So if you want each user to choose a favorite weapon, the correct site-building approach is to add a field such as Favorite weapon to the User entity using the Manage fields interface for user accounts. This makes option A correct.

This approach is also flexible. The field could be a plain list, an entity reference, or a taxonomy term reference if the site needs a controlled list of weapons. The important point is that the selection belongs to the user profile/account , because the requirement is about storing a preference for each user.

The other options are not the correct primary solution. Option B creates taxonomy terms but does not by itself provide the user-selection field. Option C uses content and Views instead of storing a value on user accounts. Option D is incorrect because Drupal users are not modeled as a content type. Therefore, adding a field to user accounts is the proper Drupal-native solution.