Drupal-Site-Builder練習問題を買いたい場合、自分のメールアドレスを記入してください。そうすれば、支払ったら、すくお客様にDrupal-Site-Builder練習問題を送付できます。だから、それは重要な情報です。また、もしDrupal-Site-Builder練習問題は更新されましたら、弊社は最新版をお客様のメールボックスに送付致します。
| Section | Weight | Objectives |
|---|---|---|
| Drupal 10/11 Specific Features | 15% | - Modern Module Usage - CKEditor 5 Configuration - Olivero and Claro Themes - JSON:API and REST Configuration |
| Site Configuration | 15% | - Module Configuration - Configuration Management - Search Configuration - User Role and Permission Management |
| Layout and User Interface | 20% | - View Modes and Display Settings - Layout Builder - Theme Configuration - Block System and Placement |
| Multilingual and Internationalization | 10% | - Configuration Translation - Content Translation - Language Configuration - Interface Translation |
| Site Building Fundamentals | 20% | - Taxonomy Architecture - Content Workflow and States - Entity Reference Relationships - Content Types and Fields |
| Site Display and Presentation | 20% | - Views Module Fundamentals - Media Management - Views Displays and Filters - Webform Integration |
>> Drupal-Site-Builderキャリアパス <<
It-PassportsのAcquiaのDrupal-Site-Builder試験トレーニング資料は君の成功に導く鍵で、君のIT業種での発展にも助けられます。長年の努力を通じて、It-PassportsのAcquiaのDrupal-Site-Builder認定試験の合格率が１００パーセントになっていました。もしうちの学習教材を購入した後、認定試験に不合格になる場合は、全額返金することを保証いたします。
質問 # 39
The UX team has suggested that "Social share" buttons currently visible in the sidebar region should be moved to the footer. The Social share buttons are implemented in a custom block.
How should you make the requested changes?
正解：B
解説：
In Drupal 10 and Drupal 11, blocks are placed and managed through the Block Layout system available at Structure # Block layout . Each theme defines regions such as Sidebar, Footer, Header, etc., and administrators can assign blocks to these regions.
Since the "Social share" buttons are implemented as a custom block , the correct approach is to reposition the block using the Block Layout admin interface . This interface allows site builders to move blocks between regions either by dragging or by editing the block's region setting. This matches Drupal's documented site- building practice for managing block placement.
Option A is incorrect because Manage display is used for configuring how fields are displayed on entities, not for block placement. Option C is incorrect because the Appearance page controls themes, not individual block placement. Option D is unnecessary because Layout Builder is used for per-content or per-entity layouts, not for globally placed blocks like a social share block.
Therefore, the simplest and correct solution is to move the block via the Block Layout page, making option B correct.
質問 # 40
You have created a custom block "Festival Offer" and placed this block in the header section of your site.
Your site has a "Premium customer" user role. You need to show this block only on the front page and only to users who have a "Premium customer" user role.
Which two visibility settings you need to make to the "Festival Offer" block to achieve these requirements?
正解：C、D
解説：
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.
質問 # 41
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?
正解：C
解説：
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.
質問 # 42
Recent log entries of your site show that there are too many failed login attempts for the site super admin user (user 1).
How can you better secure the Drupal super admin user (user 1) from outside attacks?
正解：C
解説：
Drupal's official security guidance for the super user account ( user 1 ) specifically recommends that administrators do not name the first account "admin" or something obvious . The reason is straightforward: obvious usernames make brute-force and credential-guessing attacks easier, because attackers already know half of the login credentials they need to target. Drupal's administration and security documentation also recommends limiting direct use of user 1 and protecting it carefully because it is a uniquely powerful account.
That makes option D the correct answer. The other options do not match Drupal's documented best practices.
There is no Drupal security rule about "members of the Drupal community in good standing" being allowed to use user 1. Canceling the user 1 account is not the recommended solution for this situation, and removing the Administrator role from user 1 would not make the account anonymous; in Drupal, user 1 is a special account with superuser behavior that is handled separately from ordinary role assignment. Drupal's own guidance emphasizes safer naming and tighter handling of the account, not these alternative actions.
質問 # 43
You are building a Drupal site for a company which has two content types, Page and Article. The layout of the content region on both the content types needs to be different. Page content type needs to have a three- column layout for the content section whereas the Article content type needs to use a two-column layout.
How will you build this functionality assuming all the core modules on the site are enabled?
正解：B
解説：
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.
質問 # 44
......
IT業界の発展するとともに、Drupal-Site-Builder認定試験に参加したい人が大きくなっています。でも、どのようにDrupal-Site-Builder認定試験に合格しますか？もちろん、Drupal-Site-Builder問題集を選ぶべきです。選ぶ理由はなんですか？お客様にDrupal-Site-Builder認定試験資料を提供してあげ、勉強時間は短くても、合格できることを保証いたします。不合格になる場合は、全額返金することを保証いたします。また、Drupal-Site-Builder認定試験内容が変えば、早速お客様にお知らせします。そして、もしDrupal-Site-Builder問題集の更新版があれば、お客様にお送りいたします。
Drupal-Site-Builder過去問: https://www.it-passports.com/Drupal-Site-Builder.html