[Jul-2026 Newly Released] Drupal-Site-Builder Dumps for Drupal 10/11 Certified [Q22-Q44]

[Jul-2026 Newly Released] Drupal-Site-Builder Dumps for Drupal 10/11 Certified

Updated Verified Drupal-Site-Builder dumps Q&As - 100% Pass

NEW QUESTION # 22
You have installed a custom theme for your website, and you notice that the theme displays a Drupal icon as the favicon in the browser. As much as you love Drupal, you would like to remove this favicon and display your company's favicon instead.
How would you do this in the Drupal admin interface?

• A. Use a contributed module to inject CSS to hide the Druplicon and display your logo instead.
• B. Go to Configuration > Basic Site Settings and upload your new favicon.
• C. Go to Appearance > Settings and upload your new favicon.
• D. Place the Site branding block in the appropriate region and enable the favicon under "Toggle branding elements".

Answer: C

Explanation:
In Drupal 10 and Drupal 11, favicon settings are managed at the theme level , not through general site configuration. The official Drupal theming documentation explains that each theme has its own configurable settings, including the ability to upload or replace the site's favicon.
To change the favicon, you navigate to Appearance # Settings (or specifically the active theme's settings page), where you will find an option to upload a custom favicon or use the default. This allows you to replace the default Drupal icon (Druplicon) with your organization's icon.
Option A is incorrect because the Site branding block controls elements like the logo and site name, not the favicon. Option C is incorrect because Basic Site Settings does not manage favicon configuration in modern Drupal versions. Option D is unnecessary and incorrect, as CSS is not used to change favicons.
Therefore, the correct and documented method is to update the favicon through the theme settings in the Appearance section , making option B correct.

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

• A. Create a vocabulary with a list of weapons as terms and check the "Display on user profile" checkbox.
• B. In Account settings, go to Manage fields and add field for "Favorite weapon"
• C. Create a Content Type "Weapons" and create a view. Show this view on /user.
• D. Create a Content Type "Users" which has "Favorite Weapon" field. Use the content type as user profiles.

Answer: B

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

NEW QUESTION # 24
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. Download the Spanish .po files from localize.drupal.org. Import the .po file.
• B. On the Content overview page, select all English content. Check "Import Translations" from the Bulk Actions dropdown.
• C. On Admin > Translate page, enable the Add Google Translations checkbox to import all Spanish translations.
• 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 # 25
What is meant by headless Drupal?
(Select 2 options)

• A. Just another phrase for "decoupled Drupal"
• B. Publishing content automatically in Drupal
• C. Applying security updates automatically to Drupal installation
• D. Exposing Drupal content to other systems such as native applications.

Answer: A,D

Explanation:
In Drupal's official documentation, headless Drupal is described as decoupled Drupal . The documentation explains that decoupled, or headless, Drupal separates the backend content management part of Drupal from the frontend presentation layer . In this architecture, Drupal is used as a content repository and content API, while the frontend can be built with other technologies such as JavaScript frameworks or consumed by other clients. This directly supports option C Drupal documentation also explains that this architecture allows Drupal content to be exposed to other systems and applications through APIs such as JSON:API or REST. That means Drupal can provide content to websites, mobile apps, kiosks, or other digital channels, which matches option B . The purpose of headless Drupal is therefore not automatic updates or automatic publishing, so options A and D are not correct.
So, according to Drupal 10 and Drupal 11 documentation, the correct understanding is that headless Drupal means decoupled Drupal and involves exposing Drupal-managed content to external systems or applications through APIs .

NEW QUESTION # 26
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. Create an Export view, so the content editor can review comments in a spreadsheet.
• C. Edit the Comments View, and update the table settings to make the Entity ID field sortable.
• D. Have the content editor review comments by visiting the node instead of using the Comments page.

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 # 27
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. From the block layout admin page, drag the existing block from the Sidebar region to the Footer region.
• B. From the "Appearance" admin page, reconfigure the site's theme to place the block in the Footer region instead of the Sidebar.
• C. 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.
• D. Using the "Basic page" content type's "Manage display" interface, drag the existing block from the Sidebar region to the Footer region.

Answer: A

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

Answer: B

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 # 29
The development team does monthly releases to the production system. The deployment lasts for an hour.
During the deployment time, the site is put into maintenance mode. You want a certain set of users to be able to access the site during maintenance mode as well.
How do you accomplish this?

• A. Under permissions page, provide permission "Administer site" to required users
• B. Only administrators can access the site during maintenance mode
• C. Create a new role, assign users to the role. Go to Configuration # Development # Maintenance mode and select role to allow access
• D. Create a new role, assign users to the role and provide permission "Use the site in maintenance mode" to new role

Answer: D

Explanation:
In Drupal 10 and Drupal 11, access to the site during maintenance mode is controlled through a specific permission rather than a configuration setting tied directly to roles on the maintenance mode page. The correct approach is to create a role and grant it the permission "Use the site in maintenance mode." Users assigned this role will be able to bypass the maintenance mode restriction and access the site while it is offline for regular visitors.
Option C reflects this exact mechanism and aligns with Drupal core's permission-based access control system. Drupal uses roles and permissions extensively to manage access, and maintenance mode is no exception.
Option A is incorrect because access is not limited strictly to administrators; it depends on permissions.
Option B is incorrect because the Maintenance mode configuration page does not provide role selection for access-this is a common misconception. Option D is also incorrect because granting "Administer site" gives excessive privileges and is not required for maintenance mode access; it violates the principle of least privilege.
Therefore, assigning the "Use the site in maintenance mode" permission is the correct, secure, and Drupal- recommended solution.

NEW QUESTION # 30
Your Main navigation menu has two levels of menu items like sections, and child pages within each section.
Your UX team wants to make it easier for a site visitor viewing a child page to see what other pages are in that section. They have asked you to add a submenu to the Sidebar region on child pages.
How can you add a submenu to the child pages that shows all child pages in the section?

• A. In Block layout, place the Main navigation block in the Sidebar region. Set the initial visibility level to
  1.
• B. Add the Main navigation menu to the Sidebar region, and use CSS to hide the top level menu items.
• C. Create a new menu for each main section containing links for each child page, and add each menu's block to the Sidebar region.
• D. In Block layout, place the Main navigation block in the Sidebar region. Set the initial visibility level to
  2.

Answer: D

Explanation:
In Drupal 10 and Drupal 11, menus can be displayed as blocks and configured to show specific levels of the menu hierarchy. The "Main navigation" block includes settings such as "Starting level" (or initial visibility level) and "Maximum number of levels to display." These settings allow site builders to control which part of the menu tree is visible in a given region.
To display only the child pages (submenu items) when a user is on a child page, you need to configure the block to start displaying from level 2 , which corresponds to the submenu under the current top-level section.
This ensures that only relevant sibling pages within the same section are shown in the sidebar, improving usability and navigation.
Option B (level 1) would still show top-level menu items, not just the submenu. Option A is not recommended because using CSS to hide elements does not follow Drupal's configuration best practices.
Option D is unnecessary and inefficient, as Drupal's menu system already supports hierarchical display without creating duplicate menus.
Thus, configuring the menu block with an initial visibility level of 2 is the correct and recommended approach.

NEW QUESTION # 31
You wish to display the "Recent content" block in the sidebar region on all the article pages only. The block should be hidden on all other pages.
How do you accomplish this?

• A. Edit Article Content type and check the "show recent content" option.
• B. Check the "show recent content" option in the site branding block, and set it to be visible only for Article Content type.
• C. In the Block layout settings, add the Recent content block to the Sidebar section and set the block to be visible for the "Article" Content type.
• D. Add the Recent content block to all pages, and hide it from non-Article pages using CSS.

Answer: C

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

NEW QUESTION # 32
A page has been added for a new product, and the marketing team wants you to add it to the main navigation menu, as a child of the "Products" page. During a promotion period, the team also wants you to add a link to the new page as a child of the "What's New" page.
What is the best way to add both links to the main navigation menu?

• A. Edit the new page and create two links in the Menu Settings section, one with "Products" as the parent page and the other with "What's New" as the parent page. When the promotion is over, delete the second menu link.
• B. Edit the new page, add a link in Menu Settings, and select "Products" as the Parent item. In the Main navigation menu, add a new link to the page and select "What's New" as the parent item. When the promotion is over, delete the second link from the menu.
• C. Edit the new page, add a link in Menu Settings, and select "Products" as the Parent item. Clone the new page, and set the menu link parent to the "What's New" page. When the promotion is over, delete the cloned page.
• D. In the Main navigation menu, add two links to the new page, one with "Products" as the parent page and the other with "What's New" as the parent page. Set the second link to expire on the date the promotion ends.

Answer: B

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

NEW QUESTION # 33
You run a site that attracts almost all of its users from France, even though you created the site in Australia. A number of users have started complaining that content publication times do not match their local time.
Which two solutions allow users to view content in their local timezone?

• A. Check the "Users may set their own time zone" option in the Regional settings menu
• B. Alter the default timezone to that of your target audience
• C. Configure the content types to use France's timezone by default
• D. Set the default country to France

Answer: A,B

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

NEW QUESTION # 34
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. 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.
• B. Add the "show related content" block to the Hotel nodes display. Set it to include only nodes of type
  "Hotel Review"
• C. Add "field_related_hotel" to the Hotel content type and use css to display the field in the sidebar region.
• D. 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.

Answer: A

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 # 35
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 Content types and update Media field settings in Manage form display tab.
• B. Edit the Media type Image and update media type settings to disallow .gif files.
• C. Edit the Media type Image and remove gif from "image" field settings in the Manage fields tab.
• D. Edit the Content types and disallow .gif extension in the Media reference field settings.

Answer: C

NEW QUESTION # 36
You have created a new Article node with a title, an image and a body field. Your site is configured to use Drupal's core search. If you search for a phrase which is used in your new article, the article is not returned in the search results. Search is otherwise working correctly.
Why is your article not appearing in the search results?

• A. Drupal core search does not work very well, and you should use a contributed module for search instead.
• B. The core search module must be configured to recognize the search term.
• C. Cron has not run since you added the article, so Drupal has not indexed the new article yet.
• D. You did not check the "Add to search index" checkbox when creating your article.

Answer: C

Explanation:
Drupal core search does not index newly created or updated content immediately in the default workflow.
According to the official Drupal core Search module overview , content actions such as creating, editing, or deleting content automatically mark the affected content items for indexing or reindexing at the next cron run
. Until cron runs, the new or changed content is not updated in the search index, so a newly created article may not appear in search results even though search is otherwise functioning correctly.
This makes option C the correct answer. The other options do not match Drupal core behavior. There is no normal site-building step where you configure core search to "recognize" a specific term, and Drupal does not provide an "Add to search index" checkbox when creating an article in core search. Also, while contributed search solutions exist, the question states that Drupal core search is already working correctly, so the missing result is best explained by indexing timing, not by a flaw requiring another module. Drupal's search documentation is explicit that cron is responsible for updating the index after content changes.

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

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

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 # 38
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 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.
• B. 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.
• C. 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.
• D. 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.

Answer: B,D

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 # 39
An audit of a corporate Drupal website revealed that a lot of user accounts are being created on the site, with the status "blocked". The site was initially set up to allow editors to self-register with additional administrator approval. However, the audit revealed that robots are creating a lot of user accounts and administrators are not able to keep up with the approval process.
How can we eliminate fake user registration?

• A. Hide user login by disabling the login block and/or move the login page.
• B. Change who can register accounts to "Administrators only."
• C. Enable the Drupal core captcha field on the user registration form.
• D. Configure new user accounts to "require email verification when a visitor creates an account."

Answer: C

Explanation:
The most effective and Drupal-recommended way to prevent automated (bot-driven) user registrations is to implement a challenge-response mechanism such as CAPTCHA. In Drupal 10 and Drupal 11, this is achieved using the CAPTCHA module (often paired with reCAPTCHA), which integrates directly into forms like user registration. By enabling a CAPTCHA field on the registration form, bots are prevented from submitting automated requests because they cannot solve the challenge, while legitimate users can proceed normally.
Drupal's security best practices emphasize mitigating automated abuse at the form level rather than relying solely on post-registration controls. Option A (email verification) still allows bots to create accounts and flood the system, even if they cannot activate them. Option C (hiding login) does not affect registration endpoints and provides no real protection. Option D (restricting registration to administrators only) eliminates self- registration entirely, which may not meet business requirements and is not a balanced solution.
Therefore, enabling CAPTCHA directly addresses the root cause-automated submissions-making it the most appropriate and scalable solution according to Drupal security guidelines.

NEW QUESTION # 40
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. Visit the Search administration page, select redirect 404s to the search page.
• B. Enable "Ban" module and configure it to ban the IP address found in the logs.
• C. No action needed, Drupal automatically blocks any such suspicious visitors.
• D. Visit the Performance administration page, select "enable fast 404s".

Answer: D

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

Answer: C

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 # 42
Your Marketing Department notified you that the company has recently obtained a new Toll-free phone number for customer care. They have asked you to update the "Customer care contact information" posted on your website with the new number. The contact information appears in the sidebar of every page on the site.
How should you make your updates? (Select 2 options)

• A. Click the "Edit" link on any page and make changes to the content in the editor form; repeat this process for all pages on the site.
• B. Navigate to the Block Layout admin page's custom block library, find the custom block that contains the information in question, and make changes to the content in the block editor.
• C. Click the "Manage layout" link of the home page, find the field containing the inaccurate information, and make changes there.
• D. Hover over the content until a pencil icon appears, click the icon, and choose "Edit" so that you can modify the content in Custom block edit interface.

Answer: B,D

Explanation:
In Drupal 10 and Drupal 11, content that appears in the sidebar across all pages is typically implemented as a custom block placed in a theme region via the Block Layout system. Drupal documentation explains that reusable content like contact information is best managed through custom blocks , which can be edited centrally and automatically update everywhere they are placed.
Option A is correct because the proper way to update such content is to go to Structure # Block layout # Custom block library , locate the block, and edit it. This ensures the change is reflected globally wherever the block is used.
Option C is also correct because Drupal provides contextual links (the pencil icon) that allow administrators to directly edit blocks from the front end. This is a standard and documented shortcut for editing block content.
Option B is incorrect because Layout Builder is not mentioned and is not required here. Option D is incorrect because editing individual pages would not update a shared sidebar block and would be inefficient and incorrect.
Thus, the correct Drupal site-building approaches are editing the custom block via the block library or using contextual links, making A and C correct.

NEW QUESTION # 43
......

Latest Drupal-Site-Builder Exam Dumps Acquia Exam from Training: https://actualtorrent.realvce.com/Drupal-Site-Builder-VCE-file.html