Drupal-Site-Builder学習ガイドは多くの利点を高め、購入する価値があります。購入する前に、Drupal-Site-Builder試験トレントを無料でダウンロードして試用できます。Acquia製品を購入したら、すぐにDrupal-Site-Builder学習資料をダウンロードできます。 5〜10分以内に製品を郵送します。古いクライアントには無料のアップデートと割引を提供します。 Drupal-Site-Builder試験の教材は高い合格率を高めます。 Drupal-Site-Builderの学習準備には時間と労力がほとんどかからず、主に仕事やその他の重要なことに専念できます。
| Section | Weight | Objectives |
|---|---|---|
| Topic 1: Security and Performance | 8% | - Security risks from configuration - Performance impacts from configuration |
| Topic 2: Content Modeling | 28% | - Comment types and comments management - Block types and blocks configuration - Rich media usage via Media module - Content types and vocabularies - Contact forms setup and management - Menus, menu items and menu blocks - Multilingual content and interface configuration |
| Topic 3: Contributed Module and Theme Management | 12% | - Community participation and issue reporting - Add, update, remove contributed themes - Add, update, remove contributed modules |
| Topic 4: Site Display | 20% | - Content display control using block system - Entity presentation customization - Layout building with Layout Builder - Content lists creation and management with Views |
| Topic 5: Site Configuration | 20% | - Core site settings: accounts, content, search, media etc. - Configuration import, export, synchronization - User accounts and permissions setup |
| Topic 6: Understanding Drupal and working with a Drupal Site | 12% | - Content vs block differentiation - Drupal features and terminology - Troubleshooting content, configuration and maintenance issues |
>> Drupal-Site-Builder試験参考書 <<
Drupal-Site-Builder学習ガイドの高品質と高効率は、同じ業界の製品で際立っています。私たちの教材は常にユーザーのために考慮されています。 Drupal-Site-Builder試験問題を選択すると、より良い自己になります。 Drupal-Site-Builder実際の試験では、輝かしい未来に貢献したいと考えています。私たちの教材は常に改善されています。良いアイデアがあれば、私たちの教材は喜んで受け入れます。 Drupal-Site-Builder試験資料は、このファミリーに参加するパートナーを増やすことを楽しみにしています。私たちは一緒に進歩し、より良くなります。
質問 # 43
You need to add a "Star performer" block into your company's website. The block should show the name and picture of a selected star performer employee and should be editable in the normal block layout interface. All the employees are users of the website.
How do you implement the block?
正解：C
解説：
Drupal 10 and Drupal 11 recommend using entity references and view modes to display structured entity data (like users) within other entities such as blocks. The requirement is to display a selected user (employee) with their name and picture and allow editors to choose which user appears in the block through the block editing UI.
Option D follows Drupal best practices. First, you create a custom view mode for users (e.g., "Star Performer") and configure it to display only the necessary fields such as user name and profile picture. Then, you create a custom block type with a user reference field , allowing editors to select a specific user. The display of that referenced user can be configured to use the custom view mode, ensuring consistent formatting.
Option B is less suitable because it relies on Views filtering rather than allowing editors to directly select a specific user. Option A depends on a contributed module unnecessarily. Option C is incorrect because Drupal does not provide a default block type for selecting arbitrary user entities in that way.
Thus, using a user reference field with a dedicated view mode is the correct and scalable Drupal solution.
質問 # 44
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?
正解：C
解説：
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.
質問 # 45
You have created a new Article node with a title, an image and a body field. Your site is configured to use Drupal's core search. If you search for a phrase which is used in your new article, the article is not returned in the search results. Search is otherwise working correctly.
Why is your article not appearing in the search results?
正解：A
解説：
Drupal core search does not index newly created or updated content immediately in the default workflow.
According to the official Drupal core Search module overview , content actions such as creating, editing, or deleting content automatically mark the affected content items for indexing or reindexing at the next cron run
. Until cron runs, the new or changed content is not updated in the search index, so a newly created article may not appear in search results even though search is otherwise functioning correctly.
This makes option C the correct answer. The other options do not match Drupal core behavior. There is no normal site-building step where you configure core search to "recognize" a specific term, and Drupal does not provide an "Add to search index" checkbox when creating an article in core search. Also, while contributed search solutions exist, the question states that Drupal core search is already working correctly, so the missing result is best explained by indexing timing, not by a flaw requiring another module. Drupal's search documentation is explicit that cron is responsible for updating the index after content changes.
質問 # 46
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?
正解：A
解説：
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.
質問 # 47
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?
正解：A
解説：
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.
質問 # 48
......
Drupal-Site-Builder認定試験の準備を効率的にするために、どんなツールが利用に値するものかわかっていますか。私は教えてあげますよ。ShikenPASSのDrupal-Site-Builder問題集が一番頼もしい資料です。この問題集がIT業界のエリートに研究し出されたもので、素晴らしい練習資料です。この問題集は的中率が高くて、合格率が100％に達するのです。それはIT専門家達は出題のポイントをよく掴むことができて、実際試験に出題される可能性があるすべての問題を問題集に含めることができますから。不思議だと思っていますか。しかし、これは本当のことですよ。
Drupal-Site-Builder日本語学習内容: https://www.shikenpass.com/Drupal-Site-Builder-shiken.html