Online Questions - Valid Practice Drupal-Site-Builder Exam Dumps Test Questions
100% Real Drupal-Site-Builder dumps - Brilliant Drupal-Site-Builder Exam Questions PDF
NEW QUESTION # 31
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, 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.
- B. 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.
- 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: A
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 # 32
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. Create a new role, assign users to the role and provide permission "Use the site in maintenance mode" to new role
- C. Only administrators can access the site during maintenance mode
- D. Create a new role, assign users to the role. Go to Configuration # Development # Maintenance mode and select role to allow access
Answer: B
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 # 33
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 # 34
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?
- A. Use an image style to resize the images.
- B. Use JavaScript to resize the images.
- C. Enable the "Optimize images" option on the Performance administration page.
- D. Use CSS to resize the images.
Answer: A
Explanation:
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.
NEW QUESTION # 35
You have created a new View on the development environment.
How will you export the View to the production environment?
- A. Make the required changes to the development site. Partial export using single export option and import on the live site
- B. Select synchronize configurations option on production environment
- C. This requires development effort and cannot be done by Drupal admin interface
- D. Use backup and migrate module to export the view
Answer: A
Explanation:
In Drupal 10 and Drupal 11, a View is stored as configuration , and Drupal provides a built-in Configuration Management system to move configuration between environments. According to the official Drupal User Guide, when you want to move a single configuration item (such as a View), the recommended approach is to use the Single Export and Single Import functionality available in the admin interface.
On the development site, you navigate to Configuration # Development # Configuration synchronization # Export # Single item , select View , and copy the YAML configuration. Then, on the production site, you go to Import # Single item and paste the configuration to import it.
Option A refers to full configuration synchronization, which is typically used for complete site configuration deployment, not for a single View. Option B is incorrect because Backup and Migrate is meant for database backups, not configuration transfer. Option C is incorrect because Drupal provides a UI-based method for this task.
Thus, the correct and documented approach is partial export/import using the single configuration option, making D the correct answer.
NEW QUESTION # 36
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?
- A. Create a filter using the Recipe content type's "Ingredients" field. Expose the filter to users, making sure it allows multiple selections.
- B. Include a "Combine fields" filter that searches all fields for the ingredient name(s) the user enters.
- C. Add a menu block listing all ingredients. Each item in the menu block should link to a subdirectory URL associated with the listed ingredient.
- D. For each ingredient, create a separate view display with a contextual filter to limit results by that ingredient.
Answer: A
Explanation:
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.
NEW QUESTION # 37
Your client copies HTML from an external source and pastes into the default WYSIWYG Editor on your site (CKEditor). The client has come to you complaining of broken HTML being displayed on the site. The CKEditor is configured to use Full HTML text format allowing all HTML elements and should continue to allow all elements.
How would you fix the issue of broken HTML?
- A. Enable "Correct faulty and chopped off HTML" filter on Full HTML text format
- B. Enable "Limit allowed HTML tags and correct faulty HTML" option on Full HTML
- C. Suggest using an online HTML validator before pasting into CKEditor
- D. Use JavaScript HTML corrector plugin in your CKEditor
Answer: A
Explanation:
Drupal uses text formats and filters to control how HTML input is processed before being displayed. One of the available filters is "Correct faulty and chopped off HTML" , which is specifically designed to fix improperly formatted or broken HTML markup.
According to Drupal documentation, this filter ensures that HTML pasted into editors (like CKEditor) is automatically cleaned and corrected , such as closing unclosed tags, fixing malformed markup, and preventing rendering issues. This is particularly useful when users paste HTML from external sources, which often includes inconsistent or invalid markup.
Option D is correct because it directly addresses the issue at the text format level without restricting allowed tags, maintaining the requirement to allow all HTML elements.
Option C is incorrect because enabling "Limit allowed HTML tags" would restrict HTML usage, which contradicts the requirement to allow all elements. Options A and B are not standard Drupal solutions and do not align with Drupal's built-in filtering system.
Therefore, enabling the Correct faulty and chopped off HTML filter is the correct and recommended approach in Drupal 10 and Drupal 11.
NEW QUESTION # 38
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 Appearance > Settings and upload your new favicon.
- C. Go to Configuration > Basic Site 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: B
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 # 39
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. Create a new comment type with a new field "Country" and associate it with Places content type.
- B. Obtain country information from the user profile field while adding comments.
- C. Use the GeoIP module to tag users with their locations.
- D. Create a "Country" vocabulary and add a term reference field to "Places" content type.
Answer: A
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 # 40
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. Enable site-wide contact form, rename it to RSVP and configure email functionality in the form.
- B. Download and enable the RSVP module.
- C. Create a content type called RSVP with the required fields. Give the permission to create RSVP content to the attendee role.
- D. Create a new contact form type called RSVP and configure email functionality in the form.
Answer: D
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 # 41
You have a website which is using a custom theme made specifically for that website. The client complains that content creators see an admin theme called "Claro" while creating or editing content. They want to see the content edit page in their own custom theme, but keep the other admin section in the Claro theme.
How can you achieve this?
- A. Give the Content Creator role permission to "View Admin Theme"
- B. On the Appearance page set admin theme as default theme
- C. On Appearance page, unselect the checkbox "See the administration theme when editing or creating content"
- D. Revoke the permission of viewing the custom theme for content creator role.
Answer: C
Explanation:
Drupal core provides a specific setting for whether node add/edit forms should use the administration theme.
On the Appearance page, this is the checkbox labeled "Use the administration theme when editing or creating content" . When that setting is enabled, content creation and editing routes are treated as admin-theme routes; when it is disabled, those forms use the site's default front-end theme instead, while the rest of the administration area can still use the admin theme such as Claro. This behavior is implemented in core through the node.settings configuration value use_admin_theme and the node route subscriber that marks node operation routes as admin routes only when that setting is turned on.
That makes option A correct. Option B would not solve the requirement, because setting the admin theme as the default theme would affect the whole site's front-end presentation. Options C and D are incorrect because Drupal does not use a role permission like "View Admin Theme" to control this behavior for node edit pages.
The documented control for this requirement is the Appearance-page checkbox tied to node.settings.
use_admin_theme .
NEW QUESTION # 42
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
2. - B. Create a new menu for each main section containing links for each child page, and add each menu's block to the Sidebar region.
- C. In Block layout, place the Main navigation block in the Sidebar region. Set the initial visibility level to
1. - D. Add the Main navigation menu to the Sidebar region, and use CSS to hide the top level menu items.
Answer: A
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 # 43
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 media type with an image and the description field. Use the media reference field to link this with the content.
- C. Add description field to the pre-existing image media type. Use the media reference field to link this with content.
- D. Create a content type which will have an image and description field, and link this to any content using the entity reference field.
Answer: B,C
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 # 44
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. 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.
- B. 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.
- C. 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.
- D. Click the "Manage layout" link of the home page, find the field containing the inaccurate information, and make changes there.
Answer: A,C
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 # 45
Your client wishes to retain past versions of the site content by default.
How do you accomplish this?
- A. In each Content type configuration, enable the option "Create new revisions"
- B. When creating a node, choose the "Enable content history" option
- C. Install the Content Revisions module and enable revisions for each Content type.
- D. Install the Content Moderation module, enable the option "Turn on content revisions"
Answer: A
Explanation:
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.
NEW QUESTION # 46
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 the Content overview page, select all English content. Check "Import Translations" from the Bulk Actions dropdown.
- B. On the Translate tab of each node, add Spanish translations manually.
- C. On Admin > Translate page, enable the Add Google Translations checkbox to import all Spanish translations.
- D. Download the Spanish .po files from localize.drupal.org. Import the .po file.
Answer: B
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 # 47
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. Configure new user accounts to "require email verification when a visitor creates an account."
- B. Hide user login by disabling the login block and/or move the login page.
- C. Change who can register accounts to "Administrators only."
- D. Enable the Drupal core captcha field on the user registration form.
Answer: D
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 # 48
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 "field_related_hotel" to the Hotel content type and use css to display the field in the sidebar region.
- B. 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.
- C. Add the "show related content" block to the Hotel nodes display. Set it to include only nodes of type
"Hotel Review" - 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: B
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 # 49
You need to add a "Star performer" block into your company's website. The block should show the name and picture of a selected star performer employee and should be editable in the normal block layout interface. All the employees are users of the website.
How do you implement the block?
- A. Create a user view mode with user name and picture. Add a user reference field to one of your block types and let the user reference field use the new user view mode.
- B. Add a custom block and select the type "user account information", activate the user name and picture fields.
- C. Create a new Users View with user name field and user picture and an exposed filter on uid. Add a block display to the view and place the block in the block layout.
- D. Install the user_blocks module from Drupal.org, select the fields you need and place block via block layout.
Answer: A
Explanation:
Drupal 10 and Drupal 11 recommend using entity references and view modes to display structured entity data (like users) within other entities such as blocks. The requirement is to display a selected user (employee) with their name and picture and allow editors to choose which user appears in the block through the block editing UI.
Option D follows Drupal best practices. First, you create a custom view mode for users (e.g., "Star Performer") and configure it to display only the necessary fields such as user name and profile picture. Then, you create a custom block type with a user reference field , allowing editors to select a specific user. The display of that referenced user can be configured to use the custom view mode, ensuring consistent formatting.
Option B is less suitable because it relies on Views filtering rather than allowing editors to directly select a specific user. Option A depends on a contributed module unnecessarily. Option C is incorrect because Drupal does not provide a default block type for selecting arbitrary user entities in that way.
Thus, using a user reference field with a dedicated view mode is the correct and scalable Drupal solution.
NEW QUESTION # 50
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 provides comprehensive content modeling and listing of content using UI.
- B. Drupal has a comprehensive and feature rich administrative UI out of the box.
- C. Drupal.org has an online store where you can purchase modules and themes.
- D. Drupal allows you to directly rename database columns from the UI.
- E. Drupal can be used as a headless CMS out of the box.
Answer: A,B,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 # 51
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. Cancel the user account for user 1.
- B. Remove the "Administrator" role from user 1, which makes them an anonymous user.
- C. Do not give this user an obvious name like "admin" or "administrator" which are too easy to guess.
- D. Only allow members of the Drupal community in good standing to be user 1.
Answer: C
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 # 52
......
Drupal-Site-Builder Exam PDF [2026] Tests Free Updated Today with Correct 52 Questions: https://www.itexamdownload.com/Drupal-Site-Builder-valid-questions.html
Acquia Drupal-Site-Builder Exam Preparation Guide and PDF Download: https://drive.google.com/open?id=1KIX7eUA-hvkAjCygL4D9z6uOOvACzvfx