FreeQAs
 Request Exam  Contact
  • Home
  • View All Exams
  • New QA's
  • Upload
PRACTICE EXAMS:
  • Oracle
  • Fortinet
  • Juniper
  • Microsoft
  • Cisco
  • Citrix
  • CompTIA
  • VMware
  • ISC
  • SAP
  • EMC
  • PMI
  • HP
  • Salesforce
  • Other
  • Oracle
    Oracle
  • Fortinet
    Fortinet
  • Juniper
    Juniper
  • Microsoft
    Microsoft
  • Cisco
    Cisco
  • Citrix
    Citrix
  • CompTIA
    CompTIA
  • VMware
    VMware
  • ISC
    ISC
  • SAP
    SAP
  • EMC
    EMC
  • PMI
    PMI
  • HP
    HP
  • Salesforce
    Salesforce
  1. Home
  2. Acquia Certification
  3. Drupal-Site-Builder Exam
  4. Acquia.Drupal-Site-Builder.v2026-07-26.q18 Dumps
  • «
  • 1
  • 2
  • 3
  • 4
  • 5
  • »
Download Now

Question 6

Your tennis club would like to publish details about upcoming competition events. Each event needs a title, description, scheduled date, image, and contact information. This content will need to be searchable, sortable, and displayed in multiple formats on the site.
How do you structure this content to meet the requirements?

Correct Answer: C
Drupal 10 and Drupal 11 documentation recommends planning content structure by identifying each kind of content and then creating an appropriate content type with separate fields for each distinct piece of information. Drupal's User Guide explains that content entities are made up of fields, and that when you add a content type, you can then add fields such as date, image, link, text, and other structured values. This structured approach is what makes content easier to manage, search, sort, reuse in Views, and display in different ways.
For an events use case, the correct model is a single Event content type with discrete fields for title, description, scheduled date, image, and contact information. Storing all event details in one body field or splitting them into unrelated content types would make sorting and display much harder. Drupal's planning guidance also says to choose the content entity type based on how the content will be used and edited, while blocks are better for reusable page-region content, not for primary structured records like event listings.
insert code

Question 7

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?

Correct Answer: B
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.
insert code

Question 8

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?

Correct Answer: A,C
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.
insert code

Question 9

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?

Correct Answer: B,D,E
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 .
insert code

Question 10

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?

Correct Answer: C
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.
insert code
  • «
  • 1
  • 2
  • 3
  • 4
  • 5
  • »
[×]

Download PDF File

Enter your email address to download Acquia.Drupal-Site-Builder.v2026-07-26.q18 Dumps

Email:

FreeQAs

Our website provides the Largest and the most Latest vendors Certification Exam materials around the world.

Using dumps we provide to Pass the Exam, we has the Valid Dumps with passing guranteed just which you need.

  • DMCA
  • About
  • Contact Us
  • Privacy Policy
  • Terms & Conditions
©2026 FreeQAs

www.freeqas.com materials do not contain actual questions and answers from Cisco's certification exams.