君はまだAcquia Drupal-Site-Builder認証試験を通じての大きい難度が悩んでいますか？ 君はまだAcquia Drupal-Site-Builder認証試験に合格するために寝食を忘れて頑張って復習しますか？ 早くてAcquia Drupal-Site-Builder認証試験を通りたいですか？Tech4Examを選択しましょう！Tech4ExamはきみのIT夢に向かって力になりますよ。
| Section | Weight | Objectives |
|---|---|---|
| Topic 1: Site Building Fundamentals | 20% | - Content Workflow and States - Content Types and Fields - Entity Reference Relationships - Taxonomy Architecture |
| Topic 2: Site Configuration | 15% | - Configuration Management - Search Configuration - Module Configuration - User Role and Permission Management |
| Topic 3: Drupal 10/11 Specific Features | 15% | - CKEditor 5 Configuration - Olivero and Claro Themes - Modern Module Usage - JSON:API and REST Configuration |
| Topic 4: Multilingual and Internationalization | 10% | - Content Translation - Configuration Translation - Interface Translation - Language Configuration |
| Topic 5: Layout and User Interface | 20% | - View Modes and Display Settings - Block System and Placement - Layout Builder - Theme Configuration |
| Topic 6: Site Display and Presentation | 20% | - Webform Integration - Views Module Fundamentals - Views Displays and Filters - Media Management |
>> Drupal-Site-Builder日本語版復習資料 <<
安全かつ最も信頼性の高いAcquia Drupal-Site-Builder問題集販売サイトとして、我々はお客様の個人情報を内緒し、支払いの安全性を保証しています。だから、我々社のAcquia Drupal-Site-Builder問題集のさまざまなバージョンを安心に購買できます。弊社は量豊かのIT試験資料を所有するから、あなたは別のAcquia Drupal-Site-Builder試験に関心を寄せるなら、Tech4Examでは需要したい資料を尋ねたり、弊社の職員に問い合わせたりしています。
質問 # 20
You are building a recipe site in which users submit their favorite recipes as nodes, tagged with common ingredients from a carefully curated taxonomy vocabulary. You've been asked to create a page on which site visitors can select the ingredients they have on hand and view all the site's recipes that use those ingredients.
You've already created a view listing all Recipe nodes.
How can you modify the view to support filtering by ingredient?
正解：A
解説：
Drupal's recommended way to let visitors narrow a Views listing by a field value is to add that field as a filter criterion and then expose the filter to site visitors . The core Views documentation explains that filters can be exposed so users can interact with the data shown in the view, instead of hard-coding separate displays or relying on free-text searching.
This question specifically says the recipes are tagged with a curated taxonomy vocabulary of ingredients.
Drupal's User Guide uses Ingredients as an example of a field that should be a taxonomy term reference , because the allowed values come from a managed list that can grow over time. That means the correct filter is the Recipe content type's Ingredients taxonomy-reference field in the View. Since visitors should be able to choose the ingredients they have on hand, the exposed filter should allow multiple selections .
The other options are not the standard Drupal site-building solution. Separate displays per ingredient do not scale, a combined-text search is not a structured taxonomy filter, and a menu block is navigation rather than a proper Views filter.
質問 # 21
You wish to display the "Recent content" block in the sidebar region on all the article pages only. The block should be hidden on all other pages.
How do you accomplish this?
正解：B
解説：
Drupal 10 and Drupal 11 provide block visibility conditions that allow administrators to control where blocks appear. According to Drupal's block system documentation, when placing a block through Structure # Block layout , you can configure visibility based on content types, pages, roles, or request paths .
To meet the requirement of showing the "Recent content" block only on Article pages, the correct approach is to place the block in the Sidebar region and configure its visibility condition to Content types # Article . This ensures the block is displayed only when viewing nodes of the Article content type and hidden elsewhere.
Option A is incorrect because using CSS to hide blocks is not a proper Drupal configuration and still renders the block unnecessarily. Options B and C are invalid because Drupal does not provide such settings in content type or site branding configurations.
Thus, using block visibility settings tied to the Article content type is the correct and recommended method in Drupal site building.
質問 # 22
Your content team needs to use < div > tags in the content of some articles. The default configuration does not allow for this.
How can you reconfigure the site to support this request? (Select 2 options)
正解：A、C
解説：
Drupal controls HTML markup through text formats and filters . The official User Guide explains that text formats such as Basic HTML and Full HTML determine which tags are allowed, and these formats exist specifically to protect the site from unsafe markup such as XSS. Because of that, if editors need to use < div > tags, one valid solution is to configure the content so it can use the Full HTML text format, which is the most permissive core format. Drupal also supports restricting or allowing which text formats are available on a formatted text field, including the Body field.
Another valid solution is to edit the Basic HTML text format and add < div > to the list of allowed HTML tags. Drupal's text format configuration page explicitly allows administrators to change the Allowed HTML tags for Basic HTML. That makes option C correct as well. Option B is incorrect because Drupal does not use a permission named "Use advanced HTML"; permissions are tied to specific text formats. Option D is incorrect because theme settings do not control which tags are allowed in editor input.
質問 # 23
You have installed a custom theme for your website, and you notice that the theme displays a Drupal icon as the favicon in the browser. As much as you love Drupal, you would like to remove this favicon and display your company's favicon instead.
How would you do this in the Drupal admin interface?
正解：C
解説：
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.
質問 # 24
While building a new site, you are working with the default frontend theme. You have placed custom blocks in available regions. After some time, you decide to install a new contributed theme, and set it as the default for the site.
After switching to the new theme, you notice that many of your blocks have disappeared!
What is the likely reason for this?
正解：A
解説：
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.
質問 # 25
......
何よりも、Acquiaハイクラスの運用システムを備えているため、Drupal-Site-Builder学習教材を使用してDrupal-Site-Builder試験の準備を開始できるのは、支払い後わずか5〜10分です。 第二Tech4Exam、Drupal-Site-Builderテスト問題の新しいバージョンをまとめたら、購入後1年間無料で最新バージョンのDrupal-Site-Builderトレーニング資料をお客様に送信します。 最後になりましたが、世界各地のアフターセールススタッフが、1日24時間、週7日、Drupal-Site-BuilderトレーニングガイドでAcquia Certified Drupal Site Builder Exam for Drupal 10, 11アフターサービスを提供します。
Drupal-Site-Builderトレーリング学習: https://www.tech4exam.com/Drupal-Site-Builder-pass-shiken.html