弊社のDrupal-Site-Builder練習資料は、さまざまな学位の受験者に適しています。これらの受験者は、この分野の知識のレベルに関係ありません。これらのDrupal-Site-Builderトレーニング資料は当社にとって名誉あるものであり、お客様の目標達成を支援するための最大限の特権として扱っています。私たちの知る限り、Drupal-Site-Builder試験準備は何百万人もの受験者に夢を追いかけ、より効率的に学習するように動機付けました。 Drupal-Site-Builderの練習資料は、あなたを失望させません。
| Section | Weight | Objectives |
|---|---|---|
| Site Building Fundamentals | 20% | - Entity Reference Relationships - Content Workflow and States - Content Types and Fields - Taxonomy Architecture |
| Multilingual and Internationalization | 10% | - Content Translation - Configuration Translation - Language Configuration - Interface Translation |
| Drupal 10/11 Specific Features | 15% | - JSON:API and REST Configuration - Olivero and Claro Themes - CKEditor 5 Configuration - Modern Module Usage |
| Site Configuration | 15% | - Search Configuration - User Role and Permission Management - Module Configuration - Configuration Management |
| Layout and User Interface | 20% | - Layout Builder - Block System and Placement - Theme Configuration - View Modes and Display Settings |
| Site Display and Presentation | 20% | - Media Management - Views Module Fundamentals - Views Displays and Filters - Webform Integration |
>> Drupal-Site-Builderキャリアパス <<
AcquiaのDrupal-Site-Builderのオンラインサービスのスタディガイドを買いたかったら、ShikenPASSを買うのを薦めています。ShikenPASSは同じ作用がある多くのサイトでリーダーとしているサイトで、最も良い品質と最新のトレーニング資料を提供しています。弊社が提供したすべての勉強資料と他のトレーニング資料はコスト効率の良い製品で、サイトが一年間の無料更新サービスを提供します。ですから、弊社のトレーニング製品はあなたが試験に合格することを助けにならなかったら、全額で返金することを保証します。
質問 # 44
You manage a local restaurants guide website. You are creating a page listing all the restaurants registered on your site. You've been asked to make sure that each restaurant in the list includes an image, a title, and cuisine style. When the user clicks the title or picture, the user will be taken to a detail page showing a full description of the restaurant.
Which 2 options will ensure that the listing page only contains the fields noted, without removing the description field from the detail page?
正解：C、D
解説：
Drupal 10 and Drupal 11 provide multiple ways to control how content is displayed without altering the underlying data. The requirement here is to show only selected fields (image, title, cuisine) in a listing, while keeping the full description available on the detail page.
Option A is correct because Views allows you to display content as fields , meaning you can explicitly choose which fields to show. This is a core feature of the Views module and is commonly used for listing pages.
Option C is also correct because Drupal supports view modes (like Teaser and Full). The documentation explains that you can configure the Teaser view mode to show only selected fields. Then, in Views, you can display content using that view mode. This approach is reusable and aligns with Drupal's display system.
Option B is incorrect because creating a duplicate content type is unnecessary and violates content modeling best practices. Option D is incorrect because hiding fields with CSS does not remove them from the rendered output and is not a proper Drupal solution.
Thus, using Views fields or Teaser view mode are the correct, documented approaches.
質問 # 45
You manage an online store which sells digital photos. The site hosts thousands of photos from multiple categories. Each photo has a unique description. Your client has specified that the photo description should be stored along with the image file while adding images to the photo content type. The images can be reused on other pieces of content like landing pages, blog posts etc.
How will you build the functionality to store image descriptions along with images? (Select 2 options)
正解：B、C
解説：
Drupal's recommended solution for reusable images with their own metadata is to use Media entities , not ordinary image fields on content. Core documentation and issue work around Media in Drupal explain that moving from regular image fields to media image fields is what enables reuse of the same image asset across multiple pieces of content.
That means the description should live on the media item itself , together with the image, and content types should reference that media item through a media reference field . Drupal field documentation also confirms that fields can be attached to entities and reused appropriately through references. So creating a new media type with an image field plus a description field is valid, and adding a description field to an existing Image media type is also valid. Both approaches satisfy the requirement that the image and its description stay together and can be reused elsewhere.
Option B is incorrect because Drupal core already provides Media for this use case. Option C is not the best content model because a content type represents publishable content, while reusable images-with-metadata are better modeled as Media assets.
質問 # 46
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)
正解：C、D
解説：
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.
質問 # 47
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.
質問 # 48
You have a content type named "Job opening" used by your HR department. The content type has several fields. The HR department wants to rearrange how the fields are displayed on the job opening nodes. They also want to have a different arrangement of fields on different job opening posts. All the core modules are enabled on your site.
How will you build this feature?
正解：A
解説：
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.
質問 # 49
......
当社ShikenPASSのDrupal-Site-Builder学習教材は常に高い合格率を維持していることがわかっています。教材の質の高さによるものであることは間違いありません。合格率は、Drupal-Site-Builderトレーニングファイルを証明する最も重要な標準であるというのは常識の問題です。教材の高い合格率は、当社の製品がすべての人々がDrupal-Site-Builder試験に合格し、関連する認定を取得するために非常に効果的かつ有用であることを意味します。そのため、当社からDrupal-Site-Builder試験問題を購入すると、短時間で認定資格を取得できます。
Drupal-Site-Builder必殺問題集: https://www.shikenpass.com/Drupal-Site-Builder-shiken.html