Drupal-Site-Builder Training & Certification Get Latest Drupal 10/11 Updated on Sep 04, 2026 [Q16-Q37]

Drupal-Site-Builder Training & Certification Get Latest Drupal 10/11 Updated on Sep 04, 2026

Certification Training for Drupal-Site-Builder Exam Dumps Test Engine

NEW QUESTION # 16
You are building a conference website. All attendees are required to submit an RSVP form. The submissions of the form should be emailed to the attendee and site administrator.
How will you build this functionality?

• A. Create a content type called RSVP with the required fields. Give the permission to create RSVP content to the attendee role.
• B. Create a new contact form type called RSVP and configure email functionality in the form.
• C. Download and enable the RSVP module.
• D. Enable site-wide contact form, rename it to RSVP and configure email functionality in the form.

Answer: B

Explanation:
Drupal 10 and Drupal 11 include the Contact module in core, which allows administrators to create multiple contact form types . Each contact form can have its own configuration, including recipients and email notifications . According to Drupal documentation, you can create custom contact forms (e.g., RSVP) and configure them to send emails to specified recipients when a user submits the form.
Option A is correct because creating a dedicated RSVP contact form allows you to configure email notifications to both the attendee (via auto-reply) and the site administrator. This approach uses Drupal core functionality and is the recommended way to handle simple form submissions with email notifications.
Option B is incorrect because content types are used for structured content, not form submissions with email handling. Option C is not ideal because the site-wide contact form is meant for general communication and does not provide flexibility for RSVP-specific workflows. Option D is unnecessary since Drupal core already provides the required functionality.
Thus, the best and documented solution is to create a custom contact form and configure its email settings, making A correct.

NEW QUESTION # 17
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?

• A. There are no security issues with this form.
• B. Putting a very long text into the message field, may timeout the form submit.
• C. Anonymous users should not have access to forms.
• D. Anonymous users can upload corrupted or virus-infected files to your server.

Answer: D

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

NEW QUESTION # 18
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)

• A. Search for the contributed module for adding image descriptions, as Drupal can't provide this feature out of box.
• B. Create a content type which will have an image and description field, and link this to any content using the entity reference field.
• C. Add description field to the pre-existing image media type. Use the media reference field to link this with content.
• D. Create a media type with an image and the description field. Use the media reference field to link this with the content.

Answer: C,D

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

NEW QUESTION # 19
You have created a new Comment type, but when you try to add a comment field to a Content type, you can't select your new Comment type.

• A. In your new Comment type, you didn't select "Content" as the Target entity type.
• B. "Allow comments" is not checked in the Content type settings.
• C. Custom comment types can only be added to default Content types.
• D. You need to clear the site caches to see the new option.

Answer: A

Explanation:
In Drupal, a comment field can only use comment types that are configured for the same target entity type as the entity you are attaching comments to. When you add a comment field to a Content type (node), Drupal expects a comment type whose Target entity type is Content . If the new comment type was created with another target entity type, such as custom block or user, it will not appear as a selectable option when adding that comment field to a content type. This is consistent with Drupal core's comment architecture and field behavior.
The other choices do not match Drupal's documented behavior. "Allow comments" is not a separate prerequisite checkbox that controls whether a comment type appears; instead, comments are enabled by adding a comment field to the content type. Drupal documentation for administering comment settings confirms that comment capability is added from Manage fields by adding or reusing a comment field. There is also no documented requirement that custom comment types work only on default content types, and cache clearing is not described as the fix for this selection issue.

NEW QUESTION # 20
A "Hotel Review" content type includes an entity reference field, "field_related_hotel," to associate each Hotel Review with a "Hotel" node. You are asked to add a sidebar block to the Hotel node display that shows a list of related reviews.
How can you build this functionality?

• A. Add the "show related content" block to the Hotel nodes display. Set it to include only nodes of type
  "Hotel Review"
• B. Add "field_related_hotel" to the Hotel content type and use css to display the field in the sidebar region.
• C. Create a view of Hotel nodes, with a relationship to field_related_hotel, and add the title field using the relationship. Add the block to the Hotel nodes display.
• D. Create a View of Hotel Review nodes, with a relationship to content referenced from field_related_hotel, and a contextual filter by ID using the relationship, set to use "Content ID from URL". Add the block to the Hotel nodes display.

Answer: D

Explanation:
The correct Drupal site-building approach is to create a View of Hotel Review content and filter it dynamically based on the currently viewed Hotel node . Drupal's Views documentation explains that contextual filters are used when a view should change depending on the current context, such as the URL or current page. It also notes that when the filter is based on related data rather than the base table alone, you may need to add a relationship first.
Here, the base content is Hotel Review nodes, and those reviews point to a Hotel through the entity reference field field_related_hotel . So the View should add the relationship to the referenced Hotel node, then use a Content: ID contextual filter on that relationship, with the default value set to Content ID from URL . This makes the block show only reviews whose referenced hotel matches the Hotel node currently being displayed.
That is exactly what option A describes. The other options either use the wrong base content, rely on CSS instead of Views logic, or refer to a generic block that does not provide this relationship-based filtering behavior.

NEW QUESTION # 21
You installed a new site using the Spanish language. You added new fields to article content type alongside the default fields. The custom fields labels are in Spanish.
Which of the following statements is true when you add the French language to your site?

• A. Drupal will handle translation of content configuration for built-in fields automatically. Custom fields will have to be translated manually.
• B. Drupal will handle translations of both built in and custom field configurations to French automatically.
• C. All content configurations should be translated to French manually.
• D. Drupal will handle translation of content configuration for custom fields automatically. Built-in fields will need to be translated manually.

Answer: A

Explanation:
Drupal distinguishes between interface text and configuration text . The built-in labels and other text that come from Drupal core, modules, and themes are handled by the Interface Translation system, and Drupal can download those translations for added languages. The Drupal User Guide explains that this built-in text is typically translated by downloading available translations rather than translating it yourself.
By contrast, field labels are configuration. Drupal's multilingual documentation says that configuration text includes items such as labels for fields in your content types , and the Configuration Translation module provides the interface to translate that configuration into other languages. It also specifically lists Content fields as translatable configuration elements. That means field labels you created yourself in Spanish are not automatically translated into French just because French is added; they must be translated through configuration translation.
So, when French is added, Drupal can automatically provide translations for built-in field/interface text where translations exist, but custom field configuration labels still require manual translation . Therefore, option C is the correct answer.

NEW QUESTION # 22
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?

• A. Obtain country information from the user profile field while adding comments.
• B. Use the GeoIP module to tag users with their locations.
• C. Create a "Country" vocabulary and add a term reference field to "Places" content type.
• D. Create a new comment type with a new field "Country" and associate it with Places content type.

Answer: D

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

NEW QUESTION # 23
Your website is showing a warning message that a contributed module "Password Policy" has a new security update.
What action will you take?

• A. No action is needed as security updates are not important.
• B. Drupal will update and install security update automatically on the next cron run.
• C. Download the latest version of the module. And visit the update.php page to complete the update.
• D. Uninstall the currently installed module. Download the latest version of the module and configure it again.

Answer: C

Explanation:
In Drupal 10 and Drupal 11, security updates for contributed modules must be applied promptly to protect the site from known vulnerabilities. Drupal core provides a built-in Update Manager module that notifies administrators when updates, especially security releases, are available. However, Drupal does not automatically install updates , including during cron runs, so option C is incorrect.
The correct process, as documented in Drupal's official update procedures, involves downloading the latest recommended release of the module (typically via Composer or manual replacement), and then running database updates using the /update.php script or drush updb . This ensures that any schema changes required by the new version are properly applied.
Option B is incorrect because uninstalling a module is unnecessary and can lead to data loss or configuration issues. Option A is clearly wrong, as ignoring security updates exposes the site to risks.
Therefore, the proper and documented approach is to update the module codebase and run update.php to finalize the update process, making option D the correct answer.

NEW QUESTION # 24
What are the new features built into Drupal 10 core?

• A. Decoupled Menu, Starterkit for theme, Improved Layout Builder, CKEditor5
• B. SEO Tools, Analytics, Social Sharing, Single Sign On (SSO)
• C. User Groups, Taxonomy Access Control, Flags, Social Media Integration
• D. Webforms, Web Tokens, Page Rules, User Profiles

Answer: A

Explanation:
Drupal 10 introduced several important enhancements and modernizations in core, focusing on improving developer experience, site building, and front-end capabilities. One of the most significant updates is the replacement of CKEditor 4 with CKEditor 5 , which provides a modern editing experience and better extensibility.
Drupal 10 also includes the Starterkit theme generator , which replaces older base themes and allows developers to create custom themes more cleanly and maintainably. Additionally, improvements were made to Layout Builder , enhancing usability and flexibility for managing layouts without requiring custom code.
Drupal continues to support decoupled/Headless architectures using built-in APIs like JSON:API, and improvements in this area are reflected in Drupal 10's capabilities.
The other options list features typically provided by contributed modules , not Drupal core. For example, Webforms, SEO tools, social sharing, and flags are not part of Drupal core and must be added separately.
Thus, option A correctly represents features and improvements included in Drupal 10 core.

NEW QUESTION # 25
While building a new site, you are working with the default frontend theme. You have placed custom blocks in available regions. After some time, you decide to install a new contributed theme, and set it as the default for the site.
After switching to the new theme, you notice that many of your blocks have disappeared!
What is the likely reason for this?

• A. The blocks have not yet been registered with the new theme.
• B. The new theme only allows system blocks, not custom blocks.
• C. The blocks were built in such a way that they are not compatible with the new theme. They need to be re-created.
• D. The new theme's regions have different names from the regions in the old theme. Those blocks have been disabled.

Answer: D

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

NEW QUESTION # 26
Your site is experiencing high page load times. When looking at recent log messages, you noticed a high frequency of "page not found" messages from a single IP address. On further investigation, the IP address was tracked to a suspicious crawler.
Which step will you take to improve site performance?

• A. No action needed, Drupal automatically blocks any such suspicious visitors.
• B. Visit the Performance administration page, select "enable fast 404s".
• C. Visit the Search administration page, select redirect 404s to the search page.
• D. Enable "Ban" module and configure it to ban the IP address found in the logs.

Answer: B

Explanation:
The best answer is B because the problem described is a large volume of 404 Page Not Found requests generated by a crawler, and Drupal core includes Fast 404 handling specifically to reduce the performance cost of such requests. In Drupal 10 and Drupal 11, core contains a Fast404ExceptionHtmlSubscriber and configuration under system.performance:fast_404 . Drupal's API documentation explains that Fast 404 returns a minimalist 404 response for matching requests instead of going through the full themed page handling, which lowers processing overhead for repeated invalid URL requests.
Option A may help block a bad actor, but banning one IP address is not the Drupal-documented performance feature aimed at reducing the cost of many 404s. Option C would worsen the situation because redirecting missing pages to search adds extra processing rather than reducing it. Option D is incorrect because Drupal does not automatically block suspicious visitors just because they generate many 404 log entries. Also, Drupal
10 release notes explicitly note that Fast 404 is a core capability and that separate legacy settings.php-based handling is no longer the recommended approach.

NEW QUESTION # 27
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?

• A. On Admin > Translate page, enable the Add Google Translations checkbox to import all Spanish translations.
• B. Download the Spanish .po files from localize.drupal.org. Import the .po file.
• C. On the Content overview page, select all English content. Check "Import Translations" from the Bulk Actions dropdown.
• D. On the Translate tab of each node, add Spanish translations manually.

Answer: D

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

NEW QUESTION # 28
The UX team has suggested that "Social share" buttons currently visible in the sidebar region should be moved to the footer. The Social share buttons are implemented in a custom block.
How should you make the requested changes?

• A. For each content type, use the Layout Builder module's "manage layout" feature to reassign the block from the Sidebar region to the Footer region.
• B. Using the "Basic page" content type's "Manage display" interface, drag the existing block from the Sidebar region to the Footer region.
• C. From the block layout admin page, drag the existing block from the Sidebar region to the Footer region.
• D. From the "Appearance" admin page, reconfigure the site's theme to place the block in the Footer region instead of the Sidebar.

Answer: C

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

NEW QUESTION # 29
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)

• A. Reconfigure the "Basic HTML" text format to allow the use of < div > tags.
• B. Reconfigure the site's permissions; grant content editors the "Use advanced HTML" permission.
• C. Reconfigure the page's body field to use the "Full HTML" text format.
• D. Enable the site theme's "structural HTML" setting.

Answer: A,C

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

NEW QUESTION # 30
Recent log entries of your site show that there are too many failed login attempts for the site super admin user (user 1).
How can you better secure the Drupal super admin user (user 1) from outside attacks?

• A. Remove the "Administrator" role from user 1, which makes them an anonymous user.
• B. Do not give this user an obvious name like "admin" or "administrator" which are too easy to guess.
• C. Cancel the user account for user 1.
• D. Only allow members of the Drupal community in good standing to be user 1.

Answer: B

Explanation:
Drupal's official security guidance for the super user account ( user 1 ) specifically recommends that administrators do not name the first account "admin" or something obvious . The reason is straightforward: obvious usernames make brute-force and credential-guessing attacks easier, because attackers already know half of the login credentials they need to target. Drupal's administration and security documentation also recommends limiting direct use of user 1 and protecting it carefully because it is a uniquely powerful account.
That makes option D the correct answer. The other options do not match Drupal's documented best practices.
There is no Drupal security rule about "members of the Drupal community in good standing" being allowed to use user 1. Canceling the user 1 account is not the recommended solution for this situation, and removing the Administrator role from user 1 would not make the account anonymous; in Drupal, user 1 is a special account with superuser behavior that is handled separately from ordinary role assignment. Drupal's own guidance emphasizes safer naming and tighter handling of the account, not these alternative actions.

NEW QUESTION # 31
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?

• A. Edit the Media type Image and update media type settings to disallow .gif files.
• B. Edit the Media type Image and remove gif from "image" field settings in the Manage fields tab.
• C. Edit the Content types and disallow .gif extension in the Media reference field settings.
• D. Edit the Content types and update Media field settings in Manage form display tab.

Answer: B

NEW QUESTION # 32
The site you are managing has a "Comments approval" process. You have moderators with appropriate permissions to review and approve comments. The moderators want to see all the unapproved comments sorted by the node on which they are posted, but they can't do this on the Comments approval page.
What is the simplest way to solve this problem?

• A. Create a View of unapproved comments and set the sort order to "Entity ID."
• B. Have the content editor review comments by visiting the node instead of using the Comments page.
• C. Edit the Comments View, and update the table settings to make the Entity ID field sortable.
• D. Create an Export view, so the content editor can review comments in a spreadsheet.

Answer: C

Explanation:
In Drupal 10 and Drupal 11, the administrative Comments listing is provided by the core comment View. In core's default views.view.comment configuration, the comments administration display uses the table style, includes the entity_id field labeled "Posted in" , and that column is present in the table configuration.
However, core sets that column's table option to sortable: false , while other columns such as Subject, Author, and Updated are sortable. That is why moderators cannot sort the approval page by the content item the comment belongs to, even though the field is already there.
Because the existing approval page already uses a View, the simplest solution is to edit that View and enable sorting for the Entity ID / Posted in column in the table settings. Creating a brand-new View would work, but it is not the simplest option because it duplicates an existing administrative display. The other options do not address the actual issue with the current moderation screen. Drupal's content administration documentation also confirms that comments are managed from the Comments administration page, making improvement of that interface the most appropriate site-building solution.

NEW QUESTION # 33
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?

• A. Site builder
• B. Content editor
• C. Authenticated user
• D. Publisher
• E. Administrator

Answer: B,C,E

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 .

NEW QUESTION # 34
You manage a local restaurants guide website. You are creating a page listing all the restaurants registered on your site. You've been asked to make sure that each restaurant in the list includes an image, a title, and cuisine style. When the user clicks the title or picture, the user will be taken to a detail page showing a full description of the restaurant.
Which 2 options will ensure that the listing page only contains the fields noted, without removing the description field from the detail page?

• A. Use custom display settings for the "Teaser" view mode and configure it to display only the image, title, and cuisine fields. Use the Views module to create a list of all restaurants, displaying each row as content using the "Teaser" view mode.
• B. Create a second content type called "Restaurant Overview," which only contains the image, title, and cuisine fields. Use the Views module to create a list of all of these Restaurant Overview nodes, but link their titles to their corresponding Restaurant nodes.
• C. Use the Views module to create a list of all restaurants, and make sure it displays each restaurant row as fields. Add the image, title, and cuisine fields to the view's field list.
• D. Use the Views module to create a list of all restaurants. Configure the view to hide the description field by adding a custom CSS class to its wrapper.

Answer: A,C

Explanation:
Drupal 10 and Drupal 11 provide multiple ways to control how content is displayed without altering the underlying data. The requirement here is to show only selected fields (image, title, cuisine) in a listing, while keeping the full description available on the detail page.
Option A is correct because Views allows you to display content as fields , meaning you can explicitly choose which fields to show. This is a core feature of the Views module and is commonly used for listing pages.
Option C is also correct because Drupal supports view modes (like Teaser and Full). The documentation explains that you can configure the Teaser view mode to show only selected fields. Then, in Views, you can display content using that view mode. This approach is reusable and aligns with Drupal's display system.
Option B is incorrect because creating a duplicate content type is unnecessary and violates content modeling best practices. Option D is incorrect because hiding fields with CSS does not remove them from the rendered output and is not a proper Drupal solution.
Thus, using Views fields or Teaser view mode are the correct, documented approaches.

NEW QUESTION # 35
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?

• A. Add the desired destination page to the "Redirect path" field in contact form settings.
• B. Set "Redirect URL" on Site information page under configuration.
• C. Use an add-on module like Webform, since Core doesn't offer this feature.
• D. Allow users to add their own Redirect URL in user profile pages.

Answer: A

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

NEW QUESTION # 36
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?

• A. Drupal has a comprehensive and feature rich administrative UI out of the box.
• B. Drupal allows you to directly rename database columns from the UI.
• C. Drupal can be used as a headless CMS out of the box.
• D. Drupal.org has an online store where you can purchase modules and themes.
• E. Drupal provides comprehensive content modeling and listing of content using UI.

Answer: A,C,E

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

NEW QUESTION # 37
......

Step by Step Guide to Prepare for Drupal-Site-Builder Exam: https://torrentpdf.validvce.com/Drupal-Site-Builder-exam-collection.html