ExamPassdump에서 Acquia인증 Drupal-Site-Builder덤프를 구입하시면 퍼펙트한 구매후 서비스를 제공해드립니다. Acquia인증 Drupal-Site-Builder덤프가 업데이트되면 업데이트된 최신버전을 무료로 서비스로 드립니다. 시험에서 불합격성적표를 받으시면 덤프구매시 지불한 덤프비용은 환불해드립니다.
| Section | Weight | Objectives |
|---|---|---|
| Topic 1: Understanding Drupal and working with a Drupal Site | 12% | - Troubleshooting content, configuration and maintenance issues - Content vs block differentiation - Drupal features and terminology |
| Topic 2: Security and Performance | 8% | - Security risks from configuration - Performance impacts from configuration |
| Topic 3: Site Configuration | 20% | - Core site settings: accounts, content, search, media etc. - Configuration import, export, synchronization - User accounts and permissions setup |
| Topic 4: Contributed Module and Theme Management | 12% | - Add, update, remove contributed modules - Community participation and issue reporting - Add, update, remove contributed themes |
| Topic 5: Content Modeling | 28% | - Content types and vocabularies - Menus, menu items and menu blocks - Rich media usage via Media module - Block types and blocks configuration - Multilingual content and interface configuration - Contact forms setup and management - Comment types and comments management |
| Topic 6: Site Display | 20% | - Content lists creation and management with Views - Layout building with Layout Builder - Content display control using block system - Entity presentation customization |
>> Acquia Drupal-Site-Builder시험대비 덤프 최신자료 <<
ExamPassdump 에서는 IT인증시험에 대비한 퍼펙트한Acquia 인증Drupal-Site-Builder덤프를 제공해드립니다. 시험공부할 시간이 충족하지 않은 분들은ExamPassdump 에서 제공해드리는Acquia 인증Drupal-Site-Builder덤프로 시험준비를 하시면 자격증 취득이 쉬워집니다. 덤프를 구매하시면 일년무료 업데이트서비스도 받을수 있습니다.
질문 # 30
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.
질문 # 31
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?
정답：A
설명：
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.
질문 # 32
You have a website which is using a custom theme made specifically for that website. The client complains that content creators see an admin theme called "Claro" while creating or editing content. They want to see the content edit page in their own custom theme, but keep the other admin section in the Claro theme.
How can you achieve this?
정답：B
설명：
Drupal core provides a specific setting for whether node add/edit forms should use the administration theme.
On the Appearance page, this is the checkbox labeled "Use the administration theme when editing or creating content" . When that setting is enabled, content creation and editing routes are treated as admin-theme routes; when it is disabled, those forms use the site's default front-end theme instead, while the rest of the administration area can still use the admin theme such as Claro. This behavior is implemented in core through the node.settings configuration value use_admin_theme and the node route subscriber that marks node operation routes as admin routes only when that setting is turned on.
That makes option A correct. Option B would not solve the requirement, because setting the admin theme as the default theme would affect the whole site's front-end presentation. Options C and D are incorrect because Drupal does not use a role permission like "View Admin Theme" to control this behavior for node edit pages.
The documented control for this requirement is the Appearance-page checkbox tied to node.settings.
use_admin_theme .
질문 # 33
You just installed Drupal 10 with a standard installation profile.
When you visit the User roles list, which three user roles are already available by default?
정답：A,C,D
설명：
In Drupal 10 (Standard installation profile), several roles are created automatically to support common editorial workflows. These include Authenticated user , Content editor , and Administrator .
* Authenticated user is a core default role in all Drupal installations. It represents any logged-in user and is always present.
* Content editor is provided by the Standard installation profile as part of Drupal's out-of-the-box editorial workflow, allowing users to create and manage content.
* Administrator is also included and has full permissions to manage the entire site.
Options A (Site builder) and C (Publisher) are not default roles created by Drupal core or the Standard profile.
While such roles can be created manually or may appear in specific distributions, they are not included by default.
Drupal's documentation for installation profiles confirms that the Standard profile provides a pre-configured editorial setup, including roles like Content editor, in addition to the core Authenticated user and Administrator roles.
Therefore, the correct answers are B, D, and E .
질문 # 34
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?
정답：B
설명：
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.
질문 # 35
......
우리ExamPassdump 사이트에서Acquia Drupal-Site-Builder관련자료의 일부 문제와 답 등 샘플을 제공함으로 여러분은 무료로 다운받아 체험해보실 수 있습니다.체험 후 우리의ExamPassdump에 신뢰감을 느끼게 됩니다.빨리 우리 ExamPassdump의 덤프를 만나보세요.
Drupal-Site-Builder인증덤프 샘플문제: https://www.exampassdump.com/Drupal-Site-Builder_valid-braindumps.html