The correct Drupal site-building approach is to create a View of Hotel Review content and filter it dynamically based on the currently viewed Hotel node . Drupal’s Views documentation explains that contextual filters are used when a view should change depending on the current context, such as the URL or current page. It also notes that when the filter is based on related data rather than the base table alone, you may need to add a relationship first.

Here, the base content is Hotel Review nodes, and those reviews point to a Hotel through the entity reference field field_related_hotel . So the View should add the relationship to the referenced Hotel node, then use a Content: ID contextual filter on that relationship, with the default value set to Content ID from URL . This makes the block show only reviews whose referenced hotel matches the Hotel node currently being displayed. That is exactly what option A describes. The other options either use the wrong base content, rely on CSS instead of Views logic, or refer to a generic block that does not provide this relationship-based filtering behavior.

In Drupal 10 and Drupal 11, menus can be displayed as blocks and configured to show specific levels of the menu hierarchy. The “Main navigation” block includes settings such as “Starting level” (or initial visibility level) and “Maximum number of levels to display.” These settings allow site builders to control which part of the menu tree is visible in a given region.

To display only the child pages (submenu items) when a user is on a child page, you need to configure the block to start displaying from level 2 , which corresponds to the submenu under the current top-level section. This ensures that only relevant sibling pages within the same section are shown in the sidebar, improving usability and navigation.

Option B (level 1) would still show top-level menu items, not just the submenu. Option A is not recommended because using CSS to hide elements does not follow Drupal’s configuration best practices. Option D is unnecessary and inefficient, as Drupal’s menu system already supports hierarchical display without creating duplicate menus.

Thus, configuring the menu block with an initial visibility level of 2 is the correct and recommended approach.

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.

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.

Drupal 10 and Drupal 11 provide the Layout Builder module in core, which allows site builders and content editors to control how fields are displayed. There are two levels of control: content type–level layouts and per-content (per-node) layout overrides .

Option A only allows rearranging fields globally for all nodes of that content type, which does not meet the requirement of having different layouts per job posting. Option B involves theming and template overrides, which require developer intervention and are not intended for content editors or HR staff.

Option C enables Layout Builder but only at the content type level, meaning all job openings would share the same layout. This still does not satisfy the requirement for different arrangements per node.

Option D is correct because enabling Layout Builder and allowing each content item to have its layout customized activates the “Allow each content item to have its layout customized” setting. Drupal documentation explains that this allows individual nodes to override the default layout, giving flexibility to rearrange fields differently for each job opening while still using a structured, UI-based approach.

Thus, Layout Builder with per-node customization is the correct solution.

Drupal’s configuration management system is specifically designed to move site configuration —such as content types, fields, vocabularies, and Views—between environments by exporting configuration to files and then importing it elsewhere. Drupal documentation explicitly describes configuration as the administrative settings that determine how the site functions, and it lists fields and views as examples of configuration.

That makes option D the correct workflow: build the new fields and View on a development copy of the site, export the configuration to code, deploy that code to staging, import it for QA review, and then repeat the import in production after approval. This preserves live editorial activity such as comments , because comments are site content , not configuration, and configuration deployment avoids overwriting production content with a copied database.

Option A is risky because copying the staging database back to production could overwrite live comments and other newly created production content. Option B is false because staging and production do not automatically share configuration through one database in a normal deployment workflow. Option C is inferior because configuration should be created from a development copy of the actual site, where the existing modules, schema, and site setup already match the target environments.

In Drupal 10 and Drupal 11, block placement is defined per theme . The Block Layout documentation explains that when placing a block, you are assigning it to a region in a specific theme , not globally for all themes. So when you switch the site’s default theme, the new theme may have a different set of regions or different region names, and block placements from the previous theme may no longer map correctly.

Drupal’s theming documentation is even more explicit: if a theme does not define a region that blocks were assigned to, those blocks are treated as assigned to an invalid region and are disabled . The Block module documentation also states that disabled blocks (blocks not assigned to any region in your theme) are never shown . This is exactly why blocks can appear to “disappear” after changing themes.

The other options do not match Drupal’s documented behavior. Blocks do not need to be “registered” with a theme in this sense, contributed themes are not limited to system blocks, and custom blocks generally do not need to be recreated just because the theme changed. The issue is the theme-specific region mapping , which makes D the correct answer.