Pass the Acquia Drupal 10/11 Drupal-Site-Builder Questions and answers with ExamsMirror

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.

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.

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.

Because all three content types use a Media reference field that allows the Image media type , the actual uploaded file restrictions are controlled by the source field on the Media type , not by each content type’s reference field. In Drupal, the Image media type contains an image field as its source field, and image/file fields have settings such as allowed file extensions . Drupal’s Image module documentation states that image fields can be configured with settings including allowed extensions .

Therefore, to block GIF uploads everywhere this Image media type is used, you edit the Image media type , go to Manage fields , edit its image source field , and remove gif from the allowed extensions. Since all three content types reference that same media type, the restriction applies consistently across all of them. This is the most efficient and Drupal-native solution.

Option A is incorrect because the media reference field on a content type controls which media types may be referenced, not which file extensions the media type’s source field accepts. Option C concerns form widget display, not file validation. Option D is too general; the actual extension restriction lives on the image field settings within the media type.

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.

In Drupal 10 and Drupal 11 Views, the correct place to add a CSS class to each rendered row is the Format → Settings → Row class option. Drupal core’s Views API shows that style plugins can provide a Row class text field, and when the display uses fields, this option explicitly supports field tokens . The documentation in core states: “You may use field tokens … for all fields.” That means you can add the Manufacturer field to the View and use its token in the Row class setting so each row gets a class derived from that field’s value. Drupal then token-replaces the value for each row and sanitizes it into a valid CSS identifier.

The other options do not match how Drupal Views handles per-row CSS classes. Attachments do not assign row classes to the main display, a separate custom field is not required for this built-in capability, and group-by options are for grouping results rather than applying row-level CSS classes. So the Drupal-native, documented method is to put the Manufacturer field token directly into the Row class setting in the display’s Format settings .

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.

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.

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.

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.