Authentic Acquia Certification Exam Drupal-Site-Builder Questions Answers

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.

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.

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.