100%無料Sitecore-XM-Cloud-Developer試験問題集で試験を簡単に合格させるPassTest
無料Sitecore-XM-Cloud-Developer試験問題Sitecore-XM-Cloud-Developer実際のリアル試験問題
質問 # 10
What does the default scope for a serialization include if the scope parameter is not defined?
- A. ItemAndDescendants
- B. ItemAndChildren
- C. DescendantsOnly
- D. Singleitem
正解：A
解説：
The default scope for a serialization in Sitecore Content Serialization (SCS) includesall the content itemsunder the specified path andall their descendants1.You can configure what and how content items are included and excluded from serialization in a module file such as Project.module.json1.You can also use rules to configure the serialization of content item trees with different scopes1.
References:
Sitecore Content Serialization structural overview
The default serialization format
質問 # 11
The XM Cloud Pages editor comes with a set of devices (for example, Desktop Regular and Mobile) with predefined settings. Which of the following fields must a developer specify to add and configure an additional device?
- A. Device width, visibility, responsive breakpoints
- B. Device height, visibility, an icon to represent the device
- C. Device height, visibility, responsive breakpoints
- D. Device width, visibility, an icon to represent the device
正解：D
解説：
When adding and configuring an additional device in the XM Cloud Pages editor, a developer must specify the device width in pixels, the visibility options (Disabled, Fixed, Optional), and an icon to represent the device.
These settings are crucial for simulating how content will appear on different devices within the Pages editor.
References:The Sitecore XM Cloud documentation provides detailed instructions on adding and configuring devices in the Pages editor, including specifying the device width, visibility options, and selecting an icon1.
質問 # 12
Users in XM Cloud Pages want to modify and add specific components at a given point on the page. What would a developer do to allow the users to accomplish this task?
- A. Set the standard values for the page template to include component modification options and make sure the template used by the page inherits appropriately.
- B. Enable the insert options of the components to be included forthe page template and set the appropriate allowed components.
- C. Include a placeholder as part of the layout markup and create a corresponding placeholder settings item with the appropriate allowed components.
- D. Enable the correct placeholder settings of the components to be modified to include the page template used for the content item users are editing.
正解：C
解説：
According to the Sitecore XM Cloud Documentation for Developers1, a placeholder is a named location on a page where components can be inserted. A placeholder can have one or more components assigned to it, and the content author can add, remove, or reorder the components in the XM Cloud Pages editor.To create a placeholder for a page, you need to follow these steps2:
In the Content Editor, create or select a rendering item that defines the metadata and parameters for your component.
In the rendering item, in the Data section, in the Layout field, enter the HTML markup for your component. Include a placeholder tag with a unique name, such as<sc-placeholder key="my-placeholder" />.
In the Content Editor, create or select a placeholder settings item that defines the allowed components for your placeholder. You can also clone an existing placeholder settings item and modify it as needed.
In the placeholder settings item, in the Data section, in the Key field, enter the same name as the placeholder tag, such asmy-placeholder.
In the placeholder settings item, in the Data section, in the Allowed Controls field, select the components that you want to allow in the placeholder. You can also use the Edit button to open the Allowed Controls dialog box and select the components from a tree view.
Register the component and the placeholder settings in the Components builder and add them to the Components library.
In the XM Cloud Pages editor, drag and drop the component to the page and use the placeholder to insert other components as needed.
2:Create a placeholder for a component | Sitecore Documentation1:XM Cloud Documentation for Developers
- Sitecore
質問 # 13
Which of these options best describes the purpose of the following query to the Experience Edge GraphQL schema?
query {
layout(site: "experienceedge", routePath: "/", language: "en") {
item {
homeltemPath: path
contentRoot: parent {
id
path
}
}
}
}
- A. To get an item by ID
- B. To get information about a specific content site
- C. To get the item layout for a URL
- D. To get the root item of a site
正解：D
解説：
The given GraphQL query is using thelayoutquery in Sitecore Experience Edge to retrieve information about a specific route in a site. Let's break it down:
* Querying thelayoutfield
* layout(site: "experienceedge", routePath: "/", language: "en")
* This retrieves the layout data for the homepage (routePath: "/") of the"experienceedge"site in English (language: "en").
* Fetchingitemfields
* homeltemPath: path# This retrieves thepath of the itemrepresenting the homepage.
* contentRoot: parent { id path }# This fetches theparent itemof the homepage, meaning the root content item of the site.
* The query's main purpose isnot to get an item by ID(A) since no ID filtering is used.
* It is alsonot fetching the item layout(C) because no layout/rendering data (placeholders, renderings) is requested.
* The query isnot retrieving specific content about a site(D), but instead identifying the root item.
Why is the correct answer B?Thus, the correct answer isB. To get the root item of a sitebecause the query retrieves the root content item by accessing the parent of the homepage.
* Sitecore GraphQL Schema for Experience Edge- Sitecore Docs
* GraphQL Query for Layout Service- Sitecore Layout Service
* Sitecore Experience Edge Concepts- Sitecore Experience Edge
XM Cloud Development References
質問 # 14
A developer wants to deploy to XM Cloud, but the project is not using a source code provider that has an out-of-the-box connector for XM Cloud. How can they deploy the site to XM Cloud?
- A. Create a Sitecore Update Package using SCS to include items and files.
- B. Use Vercel to connect to their source code provider and deploy.
- C. Use the Sitecore Cloud CLI to create a project and deployment.
- D. Create a custom connector to be used with the XM Cloud Deploy app.
正解：C
解説：
According to the Sitecore XM Cloud Documentation for Developers1, the Sitecore Cloud CLI is a command-line tool that allows you to perform operations against local or remote XM Cloud instances. You can use the Sitecore Cloud CLI to deploy your existing XM Cloud-compatible Sitecore XM solution in the cloud, regardless of the source code provider you are using.To deploy your solution to XM Cloud using the Sitecore Cloud CLI, you need to follow these steps2:
Install the Sitecore Cloud CLI on your workstation.
Authorize the Sitecore Cloud CLI with your Sitecore Cloud Portal organization.
Create a project in the XM Cloud Deploy app using the Sitecore Cloud CLI.
Connect your local environment to the project using the Sitecore Cloud CLI.
Push your serialized items to the project using the Sitecore Cloud CLI.
Deploy your solution to an XM Cloud environment using the Sitecore Cloud CLI.
2:Walkthrough: Creating an XM Cloud project using the Sitecore CLI1:XM Cloud Documentation for Developers - Sitecore
質問 # 15
A developer creates templates and adds standard values; items created from the templates should automatically have the Title field populated with the name of the item. What should they do to ensure this occurs?
- A. Add sname token to the template's standard values Title field.
- B. Set_name token in the new item's content Title field.
- C. Add_name token to the template's standard values Title field.
- D. Set $name token in the new item's content Title field.
正解：D
解説：
In Sitecore XM Cloud, to automatically populate the Title field of items created from a template with the name of the item, the developer should set the$nametoken in the Title field of the template's standard values. This token is replaced with the actual item name when the item is created, ensuring that the Title field is automatically filled with the correct name.
References:The use of the$nametoken in standard values is supported by Sitecore and is documented in their developer resources.It is specifically mentioned that Sitecore replaces the$nametoken with the item's name during creation1.
質問 # 16
A developer wants to create a new component to display content from a datasource. Of the options listed below, what are the optimal steps to do this?
- A. Create or reuse a SXA Module, clone an existing component that uses a context item, and create the React component based on the original cloned component.
- B. Create or reuse a SXA Module, clone an existing component that uses a data source item, and create the React component based on the original cloned component.
- C. Create the new component in the Next.js application and import it to XM Cloud.
- D. Create or reuse a SXA Module, insert a new rendering, and use the JSS CLI to scaffold out a new component.
正解：B
解説：
According to the Sitecore XM Cloud Documentation for Developers1, a data source item is a content item that provides the content for a component. A data source item can have fields, such as text, image, or link, that can be edited by the content author in the XM Cloud Pages editor.To create a new component that displays content from a data source item, you need to follow these steps2:
Create or reuse a SXA Module, which is a folder that contains the renderings, data templates, and media items for your components.
Insert a new rendering item in the SXA Module, which defines the metadata and parameters for your component. You can also clone an existing rendering item that uses a data source item and modify it as needed.
Use the JSS CLI to scaffold out a new React component in your Next.js application, which defines the layout, style, and logic for your component. You can also copy and paste an existing React component that uses a data source item and modify it as needed.
Register the React component in the Components builder and add it to the Components library.
In the XM Cloud Pages editor, drag and drop the component to the page and select or create a data source item for the component. You can also edit the data source item's fields in the Properties panel.
2:Create a component that uses a data source item | Sitecore Documentation1:XM Cloud Documentation for Developers - Sitecore
質問 # 17
A developer creates a new data template for a page. How do they ensure that the new template is available through Experience Edge?
- A. Create the template in the configured locations for Experience Edge (Feature, Foundation, Project, User Defined).
- B. Add the parent path of the template to the Experience Edge config using a patch file.
- C. Create the template anywhere in the /sitecore/templates folder.
- D. Use the Experience Edge Admin API to add the template to the schema.
正解：A
解説：
To ensure that a new data template is available through Experience Edge, it must be created in the configured locations that are recognized by the Experience Edge schema. These locations are typically structured under Feature, Foundation, Project, and User Defined paths within the Sitecore templates directory.
References:The Experience Edge schema documentation specifies that GraphQL types are generated only for templates under the configured paths for Feature, Foundation, Project, and User Defined, which aligns with the Helix content structure principles1.
質問 # 18
When deploying to XM Cloud, how are Sitecore Content Serialization (SCS) serialized items created in the Content Management (CM) instance?
- A. The XM Cloud deploy process uses serialized item batches through REST APIs at the XM Cloud CM to speed up serialization.
- B. A build pipeline must be created to use the SCS CLI push commands to push content after the XM Cloud Deploy app finishes.
- C. TheXM Cloud deploy process creates an Items as Resources (IAR) file and layers this into the CM instance.
- D. The XM Cloud deploy process uses the SCS CLI to do a push once the CM instance is active.
正解：A
解説：
TheSitecore Content Serialization (SCS)system serializes content items in and out of a Sitecore instance usingYAML files1.When deploying toXM Cloud, the XM Cloud deploy process usesserialized item batchesthroughREST APIsat the XM Cloud CM to speed up serialization2.This way, you can serialize large amounts of content items without affecting the performance of the Content Management (CM) instance2.
References:
Sitecore Content Serialization structural overview
Sitecore Content Serialization in XM Cloud
質問 # 19
A developer wants to add a new language to a headless SXA site. Which steps are required to add a new language in XM Cloud?
- A. Add language in /sitecore/system/languages. Then, on the content item, change the language dropdown to the new language and add a new version.
- B. Add language in /sitecore/system/languages, right click the site root, and go to scripts -> Add Site language.
- C. Install a language pack on the Content Management instance and then add the language in
/sitecore/system/languages. - D. They must enter the country code in the Language field. Then, on the content item, change the language dropdown to the new language and add a new version.
正解：B
質問 # 20
To connect Sitecore Pages to your local XM Cloud instance, which steps are involved?
- A. Open Pages and create an entry in Local Storage for the key "Sitecore.Pages.LocaIXmCloudUrl" with the following value: https://pages.sitecorecloud.io
- B. Open the local Content Management instance and set the predefined rendering host field value in Sitecore to https://pages.sitecorecloud.io
- C. Open the local Content Management instance and set the predefined rendering host field value in Sitecore tohttps://xmcloudcm.localhost
- D. Open Pages and create an entry in Local Storage for the key "Sitecore.Pages.LocaIXmCloudUrl" with the following value: https://xmcloudcm. localhost
正解：D
解説：
According to the Sitecore XM Cloud Documentation for Developers1, after setting up your local XM Cloud development environment, Sitecore Pages is not connected to your locally running XM Cloud instance. You can connect your local XM Cloud application to Sitecore Pages by setting a local storage key in your browser.
This allows you to use Sitecore Pages to edit content and layouts on your local front-end application.To connect Sitecore Pages to your local XM Cloud instance, you need to follow these steps2:
In your browser, navigate to the Sitecore Pages application.
Open the developer tools console of your browser and find the local storage section.The location differs between browsers:
For Chrome and Edge, open the Application panel. In the Storage section, expand the Local Storage section.
For Firefox, open the Storage panel, and expand the Local Storage section.
In the Local Storage panel, click the entry for Sitecore Pages9to reveal the local storage entries.
Create a new entry by adding a new row with the following values:
Key: Sitecore.Pages.LocalXmCloudUrl.
Value: the URL of your local XM Cloud instance.For example,10.
Refresh the9page to see your local front-end application.
2:Connect Sitecore Pages to your local XM Cloud instance1:XM Cloud Documentation for Developers - Sitecore
質問 # 21
A developer changed the CSS grid system after a site was created. Which of the following can happen due to references to the previous grid system?
- A. The Grid Setup item and its dependencies were automatically updated.
- B. The new grid was automatically added as one of the grid options.
- C. The changes break the layout of the site.
- D. A new custom theme with a grid definition item was created.
正解：C
解説：
Changing the CSS grid system after a site has been created can lead to broken layouts due to references to the previous grid system. This is because grid systems have specific rules, classes, and options that are not automatically updated or compatible with the new system, requiring manual changes to ensure the layout functions correctly.
References:The Sitecore XM Cloud documentation provides insights into the implications of changing the grid system, emphasizing the need for manual updates to avoid breaking the site layout1.
質問 # 22
A developer needs to log in to the XM Cloud Deploy app to create a project using a starter template but requires the correct permissions. Which of the following should happen?
- A. Only the Organization Owner can update their role using the XM Cloud Deploy app.
- B. An Organization Admin or Organization Owner must update their role using the XM Cloud Deploy app.
- C. Only the Organization Owner can update their role in the Sitecore Cloud Portal.
- D. An Organization Admin or Organization Owner must update their role.
正解：D
解説：
According to the Sitecore XM Cloud Documentation for Developers1, to use the XM Cloud Deploy app, you must be an Organization Admin or Organization Owner in your Sitecore Cloud Portal organization.An Organization Admin or Organization Owner can grant a team member access to the XM Cloud Deploy app by changing their organization role to Admin2. This can be done in the Sitecore Cloud Portal, not in the XM Cloud Deploy app.
2:Invite team members to your Sitecore Cloud Portal organization1:XM Cloud Documentation for Developers
- Sitecore
質問 # 23
A developer creates templates and adds standard values; items created from the templates should automatically have the Title field populated with the name of the item. What should they do to ensure this occurs?
- A. Add sname token to the template's standard values Title field.
- B. Set_name token in the new item's content Title field.
- C. Add_name token to the template's standard values Title field.
- D. Set $name token in the new item's content Title field.
正解：D
解説：
In Sitecore XM Cloud, to automatically populate the Title field of items created from a template with the name of the item, the developer should set the$nametoken in the Title field of the template's standard values.
This token is replaced with the actual item name when the item is created, ensuring that the Title field is automatically filled with the correct name.
References:The use of the$nametoken in standard values is supported by Sitecore and is documented in their developer resources.It is specifically mentioned that Sitecore replaces the$nametoken with the item's name during creation1.
質問 # 24
A developer is updating the security access rights for a new role in the Security Editor. Which of the following permissions are they able to manage? Select all that apply.
- A. Inheritance
- B. Debug
- C. Read
- D. Write
- E. Access
正解：A、C、D
解説：
According to the Sitecore XM Cloud Documentation for Developers1, the Security Editor is a tool that allows you to assign access rights to your security accounts, such as users and roles.You can grant or deny the following access rights to individual items in the content tree2:
Write- grants or denies the right to edit the item and its fields.
Read- grants or denies the right to view the item and its fields.
Inheritance- grants or denies the right to inherit the access rights from the parent item.
The other access rights, such as Debug, Access, Rename, Create, Delete, and Administer, are not available in the Security Editor, but can be assigned using other tools, such as the Access Viewer or the User Manager13.
1:XM Cloud Documentation for Developers - Sitecore3:The security tools | Sitecore Documentation2:The access rights | Sitecore Documentation
質問 # 25
When an item is published, the Experience Edge for XM Connector publishes a static snapshot of the Layout Service output of that item. If a change is made to a data source item that is referenced on the page, how is that content made visible on the website?
- A. A developer must publish the data source item.
- B. A developer must reconnect to the Experience Edge Connector module.
- C. A developer must publish the related page items.
- D. A developer must publish to the web database.
正解：A
解説：
When a change is made to a data source item in Sitecore XM Cloud, the updated content becomes visible on the website after the data source item itself is published. This is because the Experience Edge for XM Connector publishes a static snapshot of the Layout Service output, and any changes to the data source items require republishing to reflect on the website.
References:The Sitecore XM Cloud documentation explains that the Experience Edge for XM Connector uses a static publishing model, meaning that dynamic content structures are flattened at publishing time.Therefore, if a data source item changes, it must be republished for the changes to take effect on the website12.
質問 # 26
......
Sitecore Sitecore-XM-Cloud-Developer 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
| トピック 6 |
|
最新100%合格率保証付きの素晴らしいSitecore-XM-Cloud-Developer試験問題PDF：https://www.passtest.jp/Sitecore/Sitecore-XM-Cloud-Developer-shiken.html
検証済みのSitecore-XM-Cloud-Developer問題集52格別な問題：https://drive.google.com/open?id=1b62G54wl4QQDnyjSXa90olx0efVT4aRz