Score Higher on Verified Drupal-Site-Builder | Acquia Certified Drupal Site Builder Exam for Drupal 10, 11 Exam Questions with Answers

The correct answer is D . Drupal core’s Layout Builder is specifically designed to let site builders create different display layouts for different bundles, including content types such as Page and Article . The official Layout Builder documentation explains that it can be used to create layouts for content types and other entity types, and that layout defaults apply to all items of a given bundle. That matches this scenario exactly: one content type needs a default three-column layout and another needs a default two-column layout.

Option B is not the best answer because the extra setting “Allow each content item to have its layout customized” enables layout overrides for individual nodes. The question asks for different layouts by content type , not per individual content item, so overrides are unnecessary. Drupal documentation states that layout overrides are optional and are only needed when each entity may differ from the bundle default.

Option A is incorrect because field grouping and theme styling are not the Drupal core mechanism for bundle-level visual page layouts. Option C is also incorrect because content types are not assigned page layouts during field creation. In Drupal core, this is handled later through Manage display with Layout Builder enabled for each content type.

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.

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.