Drupal-Site-Builder證照指南 - Drupal-Site-Builder考試大綱

Testpdf提供給你最權威全面的Drupal-Site-Builder考試考古題，命中率極高，考試中會出現的問題可能都包含在這些考古題裏了，我們也會隨著大綱的變化隨時更新考古題。它可以避免你為考試浪費過多的時間和精力，助你輕鬆高效的通過考試。即便您沒有通過考試，我們也將承諾全額退款！所以你將沒有任何損失。機會是留給有準備的人的，希望你不要錯失良機。

Acquia Drupal-Site-Builder Exam Syllabus Topics:

Section	Objectives
Topic 1: Content Management and Display	- Content creation and administration 1. Revision handling 2. Media management 3. Content editing workflows - Content display configuration 1. View modes and display settings 2. Blocks and regions 3. Layout builder usage
Topic 2: Site Building with Views	- Views configuration 1. Filters, sorting, and contextual filters 2. Relationships in Views 3. Creating lists and pages with Views
Topic 3: Drupal Site Building Fundamentals	- Content architecture concepts 1. Entity structure and field types 2. Content types and fields 3. Taxonomy basics
Topic 4: User Management and Permissions	- Roles and permissions 1. Permission assignment 2. User roles configuration - User administration 1. User accounts and authentication
Topic 5: Security, Performance, and Best Practices	- Site maintenance 1. Security best practices 2. Caching basics
Topic 6: Theming and Layout Basics	- Frontend structure 1. Responsive layout principles 2. Themes and templates overview
Topic 7: Configuration and Site Setup	- Modules and extensions 1. Enabling and configuring modules - Site configuration basics 1. Configuration management 2. Site information and settings

>> Drupal-Site-Builder證照指南 <<

最新更新的Drupal-Site-Builder證照指南 & Drupal-Site-Builder考試大綱：Acquia Certified Drupal Site Builder Exam for Drupal 10, 11

Testpdf是個可以為所有有關於IT認證考試提供資料的網站。Testpdf可以為你提供最好最新的考試資源。選擇Testpdf你可以安心的準備你的Acquia Drupal-Site-Builder考試。我們的培訓才料可以保證你100%的通過Acquia Drupal-Site-Builder認證考試，如果沒有通過我們將全額退款並且會迅速的更新考試練習題和答案，但這幾乎是不可能發生的。Testpdf可以為你通過Acquia Drupal-Site-Builder的認證考試提供幫助，也可以為你以後的工作提供幫助。雖然有很多方法可以幫你達到你的這些目的，但是選擇Testpdf是你最明智的選擇，Testpdf可以使你花時間更短金錢更少並且更有把握地通過考試，而且我們還會為你提供一年的免費售後服務。

最新的 Drupal 10/11 Drupal-Site-Builder 免費考試真題 (Q36-Q41):

問題 #36
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. Authenticated user
B. Content editor
C. Publisher
D. Site builder
E. Administrator

答案：A,B,E

解題說明：
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 .

問題 #37
You installed a new site using the Spanish language. You added new fields to article content type alongside the default fields. The custom fields labels are in Spanish.
Which of the following statements is true when you add the French language to your site?

A. Drupal will handle translation of content configuration for custom fields automatically. Built-in fields will need to be translated manually.
B. Drupal will handle translation of content configuration for built-in fields automatically. Custom fields will have to be translated manually.
C. Drupal will handle translations of both built in and custom field configurations to French automatically.
D. All content configurations should be translated to French manually.

答案：B

解題說明：
Drupal distinguishes between interface text and configuration text . The built-in labels and other text that come from Drupal core, modules, and themes are handled by the Interface Translation system, and Drupal can download those translations for added languages. The Drupal User Guide explains that this built-in text is typically translated by downloading available translations rather than translating it yourself.
By contrast, field labels are configuration. Drupal's multilingual documentation says that configuration text includes items such as labels for fields in your content types , and the Configuration Translation module provides the interface to translate that configuration into other languages. It also specifically lists Content fields as translatable configuration elements. That means field labels you created yourself in Spanish are not automatically translated into French just because French is added; they must be translated through configuration translation.
So, when French is added, Drupal can automatically provide translations for built-in field/interface text where translations exist, but custom field configuration labels still require manual translation . Therefore, option C is the correct answer.

問題 #38
Your website has a content type named "Cars for sale" with a Taxonomy reference field for "Manufacturer" vocabulary. You have a view listing all the cars for sale. You wish to display different background colors to the cars rows based on the value of the Manufacturer field.
How can you add a CSS class to each row of the view based on the value of the Manufacturer field?

A. Add an attachment to the view that use field token for the Manufacturer field as CSS class values to all rows
B. Add the field token for Manufacturer field as a Row class in the Format > Settings of the display.
C. Add a new custom field to the view named CSS class and add a field token for Manufacturer field as values.
D. Add the field token for the Manufacturer field under group-by options of the display.

答案：B

解題說明：
In Drupal 10 and Drupal 11 Views, the correct place to add a CSS class to each rendered row is the Format # Settings # Row class option. Drupal core's Views API shows that style plugins can provide a Row class text field, and when the display uses fields, this option explicitly supports field tokens . The documentation in core states: "You may use field tokens ... for all fields." That means you can add the Manufacturer field to the View and use its token in the Row class setting so each row gets a class derived from that field's value.
Drupal then token-replaces the value for each row and sanitizes it into a valid CSS identifier.
The other options do not match how Drupal Views handles per-row CSS classes. Attachments do not assign row classes to the main display, a separate custom field is not required for this built-in capability, and group- by options are for grouping results rather than applying row-level CSS classes. So the Drupal-native, documented method is to put the Manufacturer field token directly into the Row class setting in the display's Format settings .

問題 #39
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. Install the user_blocks module from Drupal.org, select the fields you need and place block via block layout.
B. Create a new Users View with user name field and user picture and an exposed filter on uid. Add a block display to the view and place the block in the block layout.
C. Add a custom block and select the type "user account information", activate the user name and picture fields.
D. Create a user view mode with user name and picture. Add a user reference field to one of your block types and let the user reference field use the new user view mode.

答案：D

解題說明：
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.

問題 #40
The site you are managing has a "Comments approval" process. You have moderators with appropriate permissions to review and approve comments. The moderators want to see all the unapproved comments sorted by the node on which they are posted, but they can't do this on the Comments approval page.
What is the simplest way to solve this problem?

A. Edit the Comments View, and update the table settings to make the Entity ID field sortable.
B. Have the content editor review comments by visiting the node instead of using the Comments page.
C. Create an Export view, so the content editor can review comments in a spreadsheet.
D. Create a View of unapproved comments and set the sort order to "Entity ID."

答案：A

解題說明：
In Drupal 10 and Drupal 11, the administrative Comments listing is provided by the core comment View. In core's default views.view.comment configuration, the comments administration display uses the table style, includes the entity_id field labeled "Posted in" , and that column is present in the table configuration.
However, core sets that column's table option to sortable: false , while other columns such as Subject, Author, and Updated are sortable. That is why moderators cannot sort the approval page by the content item the comment belongs to, even though the field is already there.
Because the existing approval page already uses a View, the simplest solution is to edit that View and enable sorting for the Entity ID / Posted in column in the table settings. Creating a brand-new View would work, but it is not the simplest option because it duplicates an existing administrative display. The other options do not address the actual issue with the current moderation screen. Drupal's content administration documentation also confirms that comments are managed from the Comments administration page, making improvement of that interface the most appropriate site-building solution.

問題 #41
......

Testpdf 就是一個可以滿足很多參加 Acquia 的 Drupal-Site-Builder 認證考試的IT人士的需求的網站，但是要想通過 Drupal-Site-Builder 考試還需要大家認真理解。即使是Acquia 的 Drupal-Site-Builder 擬真試題和真實考試中的差不多，建議大家考試的時候，還是要把題看清楚，不能完全按照 Drupal-Site-Builder 擬真試題中的命令去做。要靈活運用，積極思考，不能死搬硬套。通過這個考試是需要豐富的知識和經驗的，而積累豐富的知識和經驗是需要時間的。

Drupal-Site-Builder考試大綱: https://www.testpdf.net/Drupal-Site-Builder.html