Free Acquia Certified Drupal Site Builder Exam for Drupal 10, 11 Practice Questions

Drupal 10 and Drupal 11 let you control block display through visibility conditions on the block configuration form. Drupal’s block management documentation explains that a block’s visibility can depend on page-specific visibility settings and also on user role conditions. For page visibility, Drupal specifically notes that the front page is an exception and must be entered as < front > . To show a block only on the homepage, you add < front > in the Pages visibility settings and choose “Show for the listed pages.”

To limit the block to a specific audience, you use the Roles visibility condition and select the exact role that should see the block. In this case, that is Premium customer , not the broader Authenticated user role, because selecting Authenticated user would show the block to all logged-in users who have that role, not just premium customers. Drupal core’s block form API also confirms that block visibility is built through configurable visibility conditions in the block UI.

So the correct combination is:

A for the role restriction, and B for the front-page-only restriction.

In Drupal’s official documentation, headless Drupal is described as decoupled Drupal . The documentation explains that decoupled, or headless, Drupal separates the backend content management part of Drupal from the frontend presentation layer . In this architecture, Drupal is used as a content repository and content API, while the frontend can be built with other technologies such as JavaScript frameworks or consumed by other clients. This directly supports option C

Drupal documentation also explains that this architecture allows Drupal content to be exposed to other systems and applications through APIs such as JSON:API or REST. That means Drupal can provide content to websites, mobile apps, kiosks, or other digital channels, which matches option B . The purpose of headless Drupal is therefore not automatic updates or automatic publishing, so options A and D are not correct.

So, according to Drupal 10 and Drupal 11 documentation, the correct understanding is that headless Drupal means decoupled Drupal and involves exposing Drupal-managed content to external systems or applications through APIs .