[Aug-2026] Free Drupal-Site-Builder Exam Questions Drupal-Site-Builder Actual Free Exam Questions [Q19-Q34]

Rate this post

[Aug-2026] Free Drupal-Site-Builder Exam Questions Drupal-Site-Builder Actual Free Exam Questions

Verified Drupal-Site-Builder dumps and 52 unique questions

Acquia Drupal-Site-Builder Exam Syllabus Topics:

Section	Weight	Objectives
Topic 1: Multilingual and Internationalization	10%	– Interface Translation – Content Translation – Language Configuration – Configuration Translation
Topic 2: Drupal 10/11 Specific Features	15%	– CKEditor 5 Configuration – Olivero and Claro Themes – Modern Module Usage – JSON:API and REST Configuration
Topic 3: Site Building Fundamentals	20%	– Content Types and Fields – Entity Reference Relationships – Taxonomy Architecture – Content Workflow and States
Topic 4: Site Configuration	15%	– Module Configuration – Configuration Management – User Role and Permission Management – Search Configuration
Topic 5: Layout and User Interface	20%	– Theme Configuration – Layout Builder – Block System and Placement – View Modes and Display Settings
Topic 6: Site Display and Presentation	20%	– Webform Integration – Views Module Fundamentals – Views Displays and Filters – Media Management

Q19. You manage an online store which sells digital photos. The site hosts thousands of photos from multiple categories. Each photo has a unique description. Your client has specified that the photo description should be stored along with the image file while adding images to the photo content type. The images can be reused on other pieces of content like landing pages, blog posts etc.
How will you build the functionality to store image descriptions along with images? (Select 2 options)

Create a media type with an image and the description field. Use the media reference field to link this with the content.

Search for the contributed module for adding image descriptions, as Drupal can’t provide this feature out of box.

Create a content type which will have an image and description field, and link this to any content using the entity reference field.

Add description field to the pre-existing image media type. Use the media reference field to link this with content.

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.

Q20. You are building a bi-lingual site which is in English and Spanish. You have created all the English content.
How will you add Spanish translation to existing content?

On the Translate tab of each node, add Spanish translations manually.

On Admin > Translate page, enable the Add Google Translations checkbox to import all Spanish translations.

Download the Spanish .po files from localize.drupal.org. Import the .po file.

On the Content overview page, select all English content. Check “Import Translations” from the Bulk Actions dropdown.

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.

Q21. Your client wishes to retain past versions of the site content by default.
How do you accomplish this?

Install the Content Moderation module, enable the option “Turn on content revisions”

Install the Content Revisions module and enable revisions for each Content type.

When creating a node, choose the “Enable content history” option

In each Content type configuration, enable the option “Create new revisions”

The correct answer is D . In Drupal 10 and Drupal 11, retaining past versions of content is handled through node revisions . Drupal’s official documentation explains that revisions are controlled at the content type level, and the relevant setting is the “Create new revision” checkbox in the content type configuration. When this option is enabled, Drupal creates a new revision by default whenever content of that type is updated, allowing editors and administrators to retain and review previous versions of the content.
The other options are not correct according to Drupal core documentation. Content Moderation is related to editorial workflows and depends on revisions, but it is not required just to keep past versions of content. There is also no core module called Content Revisions for enabling this basic feature, and “Enable content history” is not the Drupal node setting used for revision retention. Drupal’s API documentation for NodeType::$new_revision and setNewRevision() confirms that the content type stores whether new revisions should be created by default. The Drupal site-building documentation also notes that new content types, as well as standard Article and Page types, use the Create new revision setting for revision behavior.
I understand you want the next one in the same exact format, verified against Drupal 10/11 site-building documentation. Here it is.

Q22. You are building a gaming site where users are teamed based on their favorite weapon.
How will you provide the ability for users to select their favorite weapon?

In Account settings, go to Manage fields and add field for “Favorite weapon”

Create a vocabulary with a list of weapons as terms and check the “Display on user profile” checkbox.

Create a Content Type “Weapons” and create a view. Show this view on /user.

Create a Content Type “Users” which has “Favorite Weapon” field. Use the content type as user profiles.

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.

Q23. Users are complaining that listing pages with a large number of images are loading very slowly. On reviewing this you found that full-sized images are loaded while displaying thumbnails.
How will you ensure that smaller sized images are used as thumbnails?

Enable the “Optimize images” option on the Performance administration page.

Use an image style to resize the images.

Use JavaScript to resize the images.

Use CSS to resize the images.

In Drupal 10 and Drupal 11, the correct way to display resized images (such as thumbnails) is by using Image Styles . Image styles allow Drupal to generate derivative images with specific dimensions (e.g., thumbnail size) and serve those instead of the original full-sized image. This significantly improves performance because smaller image files are loaded, reducing page load time and bandwidth usage.
Drupal’s Image module documentation explains that image styles can apply effects such as scaling, cropping, and resizing, and are typically used in Views or field display settings to ensure appropriately sized images are rendered.
Options C and D (JavaScript and CSS resizing) only change how images appear visually but still load the full- size image , which does not improve performance. Option A refers to performance settings but does not specifically handle image resizing.
Therefore, using an image style is the correct, recommended, and documented approach for optimizing image display and improving site performance.

Q24. You are using a contributed module named Lotus. You have read the module’s documentation and ensured it is configured correctly. However, certain functionality of the module is not working as intended.
How should you find help?
(Select 2 options)

Search for answers and ask questions in the module’s issue queue on drupal.org.

Ask questions in the drupal-support channel on IRC or in the support channel on Drupal Slack group.

Create a comment of type “support request” on the module’s project page.

Email the module’s maintainer and ask for help.

Drupal 10 and Drupal 11 documentation strongly recommend using community-supported channels for troubleshooting contributed modules. The primary and most appropriate place to seek help is the module’s issue queue on drupal.org , where users can search for existing issues, report bugs, and ask questions. This ensures transparency, allows maintainers and contributors to track problems, and benefits the wider community. Therefore, option A is correct.
Additionally, Drupal has active community communication platforms such as Drupal Slack and IRC channels (like #drupal-support), where developers and site builders collaborate and provide real-time assistance. These are officially recognized community support channels, making option B correct.
Option C is incorrect because Drupal project pages do not use general comments for support; instead, all discussions should happen in the issue queue. Option D is discouraged because directly emailing maintainers bypasses the public support process and is not aligned with Drupal community best practices.
Thus, the correct and recommended ways to find help are using the issue queue and community support channels.

Q25. You have enabled website feedback contact form to allow users to submit feedback. You would like to redirect users to a different page after submission.
How will you accomplish this?

Use an add-on module like Webform, since Core doesn’t offer this feature.

Set “Redirect URL” on Site information page under configuration.

Allow users to add their own Redirect URL in user profile pages.

Add the desired destination page to the “Redirect path” field in contact form settings.

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.

Q26. Your content team needs to use < div > tags in the content of some articles. The default configuration does not allow for this.
How can you reconfigure the site to support this request? (Select 2 options)

Reconfigure the page’s body field to use the “Full HTML” text format.

Reconfigure the site’s permissions; grant content editors the “Use advanced HTML” permission.

Reconfigure the “Basic HTML” text format to allow the use of < div > tags.

Enable the site theme’s “structural HTML” setting.

Drupal controls HTML markup through text formats and filters . The official User Guide explains that text formats such as Basic HTML and Full HTML determine which tags are allowed, and these formats exist specifically to protect the site from unsafe markup such as XSS. Because of that, if editors need to use < div > tags, one valid solution is to configure the content so it can use the Full HTML text format, which is the most permissive core format. Drupal also supports restricting or allowing which text formats are available on a formatted text field, including the Body field.
Another valid solution is to edit the Basic HTML text format and add < div > to the list of allowed HTML tags. Drupal’s text format configuration page explicitly allows administrators to change the Allowed HTML tags for Basic HTML. That makes option C correct as well. Option B is incorrect because Drupal does not use a permission named “Use advanced HTML”; permissions are tied to specific text formats. Option D is incorrect because theme settings do not control which tags are allowed in editor input.

Q27. You are building a Drupal site for a company which has two content types, Page and Article. The layout of the content region on both the content types needs to be different. Page content type needs to have a three- column layout for the content section whereas the Article content type needs to use a two-column layout.
How will you build this functionality assuming all the core modules on the site are enabled?

Add field groups named two-column and three-column in respective content types and organize fields in the field groups. Add appropriate layout styles in your theme.

For each content type, enable “Use Layout Builder” in layout options on the Manage display tab and also check the “Allow each content item to have its layout customized” option.

While defining the content types, select the two-column layout or three-column layout as appropriate while adding the fields.

For each content type, enable “Use Layout Builder” in layout options on the Manage display tab and select appropriate two-column / three-column layouts for the content types.

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.

Q28. You have a Corporate site where all traffic is anonymous. On the site, you have been getting thousands of user registrations every day. You notice that most of the registrations are spam.
What will you do to prevent this?

Add user/password in your .htaccess, so that only people who know the credentials can access your site and create an account.

Set “Who can register accounts” to “Visitors,” and check “Enable password strength indicator.”

Set “Who can register accounts” to “Administrators only,” and assign the task of new account creation to site admins.

Set the personal contact form for new users to disabled, and set email verification to use the personal contact form method.

For a corporate site where public visitors do not need self-service accounts, the correct Drupal site-building solution is to disable visitor registration. Drupal’s official User Guide for Configuring User Account Settings says to go to Configuration > People > Account settings and, under Registration and cancellation , select
“Administrators only” as the people with permission to register user accounts. This turns off public account creation and is the standard Drupal method for stopping spam registrations on sites that do not need open sign- up.
The other choices do not match Drupal’s documented account-management approach. Option B still allows visitors to create accounts, so it does not prevent spam registrations; a password strength indicator is unrelated to blocking bot sign-ups. Option A would protect the entire site at the web-server level, which is not the intended Drupal account-registration setting and would block all anonymous access, contradicting the site’s normal public use. Option D refers to unrelated contact-form behavior and does not control account creation.
Drupal’s account settings documentation specifically identifies “Administrators only” as the way to stop visitor registration, making C the verified answer.

Q29. You are building a recipe site in which users submit their favorite recipes as nodes, tagged with common ingredients from a carefully curated taxonomy vocabulary. You’ve been asked to create a page on which site visitors can select the ingredients they have on hand and view all the site’s recipes that use those ingredients.
You’ve already created a view listing all Recipe nodes.
How can you modify the view to support filtering by ingredient?

For each ingredient, create a separate view display with a contextual filter to limit results by that ingredient.

Include a “Combine fields” filter that searches all fields for the ingredient name(s) the user enters.

Create a filter using the Recipe content type’s “Ingredients” field. Expose the filter to users, making sure it allows multiple selections.

Add a menu block listing all ingredients. Each item in the menu block should link to a subdirectory URL associated with the listed ingredient.

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.

Q30. Your site has three Content types with a Media reference field. The field is configured to Media type as Image. You noticed that some users are adding animated GIF files while adding the content, which are very distracting.
How can you disallow adding files with .gif extension on all the Content types which use the Media reference field?

Edit the Media type Image and update media type settings to disallow .gif files.

Edit the Content types and update Media field settings in Manage form display tab.

Edit the Content types and disallow .gif extension in the Media reference field settings.

Edit the Media type Image and remove gif from “image” field settings in the Manage fields tab.

Q31. Your customer support department has asked to build a form on your Drupal website. The form should have the following fields: Subject (text plain), Name (text plain), Email (Email), Message (text long), Attachment (file).
A developer built the form without any validations or restrictions. The form is accessible to Anonymous users of the site.
What is the potential security threat with this form?

Anonymous users should not have access to forms.

Anonymous users can upload corrupted or virus-infected files to your server.

Putting a very long text into the message field, may timeout the form submit.

There are no security issues with this form.

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.

Q32. You just installed Drupal 10 with a standard installation profile.
When you visit the User roles list, which three user roles are already available by default?

Site builder

Authenticated user

Publisher

Content editor

Administrator

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 .

Q33. A new customer has asked, why a Drupal-based website will be more flexible over a custom developed website.
Which THREE Drupal features would you explain to the customer?

Drupal can be used as a headless CMS out of the box.

Drupal provides comprehensive content modeling and listing of content using UI.

Drupal.org has an online store where you can purchase modules and themes.

Drupal allows you to directly rename database columns from the UI.

Drupal has a comprehensive and feature rich administrative UI out of the box.

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.

Q34. You have a content type “Places” which lists tourist destinations of different countries. You would like the visitors to be able to mark their country while commenting on “Places”. This does not apply to other content types.
How will you build this functionality?

Obtain country information from the user profile field while adding comments.

Create a new comment type with a new field “Country” and associate it with Places content type.

Create a “Country” vocabulary and add a term reference field to “Places” content type.

Use the GeoIP module to tag users with their locations.

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.

Loading …