Practice Free Drupal-Site-Builder Acquia Certified Drupal Site Builder Exam for Drupal 10, 11 Exam Questions Answers With Explanation

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 .

The main security risk in this scenario is the unrestricted file upload field exposed to anonymous users. Drupal’s file API documentation explains that file uploads must use validation and a defined list of allowed extensions. Core specifically notes that uploading arbitrary files is dangerous and that validation is necessary. The Drupal file API also states that using a managed file field with defined allowed extensions helps sanitize filenames, validate files, and block insecure extensions by default. Without those restrictions, anonymous visitors could upload unsafe files, including malicious or infected files, to the server.

Option A is too broad, because anonymous users can legitimately access public forms on Drupal sites. The issue is not public access by itself, but public access combined with missing validation and upload restrictions . Option C describes a possible performance problem, not the most important security threat identified by Drupal’s documentation. Option D is clearly incorrect because Drupal’s security guidance stresses protecting public forms and validating uploads carefully, especially on forms exposed to anonymous users.

In Drupal 10 and Drupal 11, each content item (node) can only have one menu link created through its Menu settings . Drupal documentation explains that the Menu settings section allows you to place a node in a menu, but only as a single menu item . Therefore, you cannot create two menu links for the same node directly from the node edit form, which makes option D incorrect.

The correct approach is to create one menu link via the node’s Menu settings (placing it under “Products”), and then manually add an additional menu link in the Menu administration (Structure ? Menus ? Main navigation) that points to the same node but is placed under “What’s New.” This matches option A . After the promotion, the temporary menu link can be removed.

Option B is incorrect because duplicating content creates unnecessary redundancy and breaks content management best practices. Option C is incorrect because Drupal core does not provide a built-in “menu link expiration” feature.

Thus, Drupal’s recommended method is to create one menu link via the node and another manually via the menu UI, making A the correct answer.

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 .

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’s Comment module supports creating different comment types and attaching them to content entities. The official Comment module documentation states that Drupal can create new comment types that can be attached to content entities, and the detailed comment documentation explains that when you create a comment type and choose the target entity type as Content , that comment type becomes available when adding a comment field to a content type.

Drupal’s field documentation also explains that fields on comments are defined at the content-type level , on the Comment fields tab of the content type edit page. When you add a field for comments, each comment on content items of that type gets that field. Drupal even gives an example of adding a field to comments for one content type but not another, which matches this requirement exactly.

So the right solution is to create a new comment type for Places comments, add a Country field to that comment type, and then use that comment type on the Places content type only. The other options either store the data in the wrong place or do not make it specific to comments on Places.

Drupal’s recommended solution for reusable images with their own metadata is to use Media entities , not ordinary image fields on content. Core documentation and issue work around Media in Drupal explain that moving from regular image fields to media image fields is what enables reuse of the same image asset across multiple pieces of content.

That means the description should live on the media item itself , together with the image, and content types should reference that media item through a media reference field . Drupal field documentation also confirms that fields can be attached to entities and reused appropriately through references. So creating a new media type with an image field plus a description field is valid, and adding a description field to an existing Image media type is also valid. Both approaches satisfy the requirement that the image and its description stay together and can be reused elsewhere.

Option B is incorrect because Drupal core already provides Media for this use case. Option C is not the best content model because a content type represents publishable content, while reusable images-with-metadata are better modeled as Media assets.

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 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.

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.