P.S. Free 2026 Acquia Drupal-Site-Builder dumps are available on Google Drive shared by Dumpexams: https://drive.google.com/open?id=1M9CmbqnTbZltrTmtlHa_6ccv9O07HPac
Dumpexams Drupal-Site-Builder product in above-mentioned three formats carries most probable real exam questions. Every person who attempts the exam has different preparation style. Some want to do in-depth study while some prefer quick Acquia Certified Drupal Site Builder Exam for Drupal 10, 11 test preparation. Dumpexams has introduced these three formats so every applicant of the test can prepare as per unique learning styles. In addition, we offer up to 1 year of free questions updates, free demos, discounts, and a 24/7 customer support. Don’t miss these incredible offers. Purchase real exam questions today.
| Section | Weight | Objectives |
|---|---|---|
| Topic 1: Understanding Drupal and working with a Drupal Site | 12% | - Drupal features and terminology - Content vs block differentiation - Troubleshooting content, configuration and maintenance issues |
| Topic 2: Security and Performance | 8% | - Performance impacts from configuration - Security risks from configuration |
| Topic 3: Contributed Module and Theme Management | 12% | - Add, update, remove contributed modules - Community participation and issue reporting - Add, update, remove contributed themes |
| Topic 4: Site Configuration | 20% | - Core site settings: accounts, content, search, media etc. - User accounts and permissions setup - Configuration import, export, synchronization |
| Topic 5: Content Modeling | 28% | - Comment types and comments management - Rich media usage via Media module - Menus, menu items and menu blocks - Contact forms setup and management - Multilingual content and interface configuration - Block types and blocks configuration - Content types and vocabularies |
| Topic 6: Site Display | 20% | - Layout building with Layout Builder - Content display control using block system - Entity presentation customization - Content lists creation and management with Views |
>> Drupal-Site-Builder Free Download <<
The pass rate is 98.65% for Drupal-Site-Builder study guide, and you can pass the exam just one time. In order to build up your confidence for the exam, we are pass guarantee and money back guarantee. If you fail to pass the exam by using Drupal-Site-Builder exam braindumps of us, we will give you full refund. Besides, Drupal-Site-Builder learning materials are edited and verified by professional specialists, and therefore the quality can be guaranteed, and you can use them at ease. We have online and offline service. If you have any questions for Drupal-Site-Builder Exam Materials, you can consult us, and we will give you reply as quick as possible.
NEW QUESTION # 25
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)
Answer: A,B
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 # 26
Your website has a content type named Hotel with a Taxonomy reference field for Landmarks vocabulary.
You want to create a view to list all the hotels filtered by landmarks as a contextual filter.
How will you pass the term name in the URL for the contextual filter?
Answer: A
Explanation:
In Drupal 10 and Drupal 11, Views contextual filters are used to dynamically filter content based on values passed through the URL. When filtering content by taxonomy (such as Landmarks), you configure a contextual filter using the taxonomy term field associated with the content type.
To pass a value like a term name in the URL , you must configure the contextual filter to accept term identifiers such as term ID or term name . Drupal Views allows validation and transformation of contextual input, including using the taxonomy term name via settings like "Provide default value" or "Specify validation criteria." This matches option B.
Option A is incorrect because exposed filters rely on user input via UI forms, not URL path arguments.
Option C is unnecessary duplication and not aligned with best practices. Option D is not required because taxonomy reference fields already provide the necessary relationship internally for filtering; explicitly adding a relationship is only needed in more complex multi-entity scenarios.
Therefore, the correct approach is to use a contextual filter configured to accept the taxonomy term (including term name) via the URL, making option B correct.
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?
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 # 28
You have a content type named "Job opening" used by your HR department. The content type has several fields. The HR department wants to rearrange how the fields are displayed on the job opening nodes. They also want to have a different arrangement of fields on different job opening posts. All the core modules are enabled on your site.
How will you build this feature?
Answer: D
Explanation:
Drupal 10 and Drupal 11 provide the Layout Builder module in core, which allows site builders and content editors to control how fields are displayed. There are two levels of control: content type-level layouts and per- content (per-node) layout overrides .
Option A only allows rearranging fields globally for all nodes of that content type, which does not meet the requirement of having different layouts per job posting. Option B involves theming and template overrides, which require developer intervention and are not intended for content editors or HR staff.
Option C enables Layout Builder but only at the content type level, meaning all job openings would share the same layout. This still does not satisfy the requirement for different arrangements per node.
Option D is correct because enabling Layout Builder and allowing each content item to have its layout customized activates the "Allow each content item to have its layout customized" setting. Drupal documentation explains that this allows individual nodes to override the default layout, giving flexibility to rearrange fields differently for each job opening while still using a structured, UI-based approach.
Thus, Layout Builder with per-node customization is the correct solution.
NEW QUESTION # 29
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?
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 # 30
......
The quality of our Acquia Drupal-Site-Builder training material is excellent. After all, we have undergone about ten years' development. Never has our practice test let customers down. Although we also face many challenges and troubles, our company get over them successfully. If you are determined to learn some useful skills, our Acquia Drupal-Site-Builder Real Dumps will be your good assistant. Then you will seize the good chance rather than others.
Drupal-Site-Builder Exam Vce: https://www.dumpexams.com/Drupal-Site-Builder-real-answers.html
P.S. Free 2026 Acquia Drupal-Site-Builder dumps are available on Google Drive shared by Dumpexams: https://drive.google.com/open?id=1M9CmbqnTbZltrTmtlHa_6ccv9O07HPac