• ホーム
  • ブログ
  • Sitecore-XM-Cloud-Developer試験問題集を試そう！ベストSitecore-XM-Cloud-Developer試験問題トレーニングを提供しています [Q16-Q36]

Sitecore-XM-Cloud-Developer試験問題集を試そう！ベストSitecore-XM-Cloud-Developer試験問題トレーニングを提供しています [Q16-Q36]

Share

Sitecore-XM-Cloud-Developer試験問題集を試そう！ベストSitecore-XM-Cloud-Developer試験問題トレーニングを提供しています

実践サンプルと問題集指導には2025年最新のSitecore-XM-Cloud-Developer有効なテスト問題集

質問 # 16
If a developer wants to limit the serialization of items under a Navigation item to just the item itself and then one step below, what property should the developer add to the includes to indicate this limitation?

  • A. Scope
  • B. Nothing-this is the default.
  • C. Name
  • D. Limit

正解：D

解説：
InSitecore XM Cloud,serializationis used to store and transfer content items between environments. If a developer wants tolimit the depth of serialized itemsunder aNavigation itemto only the item itself and one level below, they must use theLimitproperty in the serialization configuration.
* TheLimitpropertyrestricts how many levels deepthe serialization will include.
* SettingLimit: 1ensures thatonly the specified item (Navigation item) and its immediate childrenare serialized.
How the Limit Property Works:Example of Serialization Configuration:items:
includes:
- name: NavigationSerialization
path: /sitecore/content/MySite/Home/Navigation
limit: 1 # Only serializes the Navigation item and its immediate children
* In this example:
* /Navigationitself is serialized.
* Itsdirect childrenare also serialized.
* Grandchildren or deeper levels are excluded.
* Option A - Scope#Incorrect becauseScopeis not a valid property in Sitecoreserialization includes.
* Option B - Nothing-this is the default#Incorrect because the default behavior is toserialize all descendants, not just one level. You must explicitly define a limit.
* Option D - Name#Incorrect becauseNameis used to label the serialization include rule and does not control serialization depth.
Why Other Options Are Incorrect?Thus, the correct answer is:#C. Limit
* Sitecore Serialization in XM Cloud:https://doc.sitecore.com/xmc/en/developers/xm-cloud/sitecore- content-serialization.html
* YAML Serialization Configuration in Sitecore:https://doc.sitecore.com/developers/101/sitecore- experience-manager/en/sitecore-content-serialization-yaml-configuration.html References for XM Cloud Development:


質問 # 17
Which of the following statements accurately describes the purpose of Headless variants in Sitecore XM Cloud?

  • A. Headless variants define how a rendering appears and what content it displays.
  • B. Headless variants enable the creation of custom rendering items for components from scratch.
  • C. Headless variants determine the order in which renderings are displayed on a webpage.
  • D. Headless variants allow renderings to be edited and customized in the Content Editor.

正解：A

解説：
According to the Sitecore XM Cloud Documentation for Developers1, headless variants are a way to create different versions of a rendering that can be used in different contexts or scenarios. A headless variant defines the layout, style, and content of a rendering using HTML, CSS, and JavaScript. You can create headless variants for your components in the Components builder and use them in your XM Cloud Pages.Headless variants allow you to reuse the same component with different appearances and contents without creating multiple renderings2.
2:Create a headless variant for a component | Sitecore Documentation1:XM Cloud Documentation for Developers - Sitecore


質問 # 18
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 to the web database.
  • B. A developer must publish the related page items.
  • C. A developer must publish the data source item.
  • D. A developer must reconnect to the Experience Edge Connector module.

正解：B

解説：
InSitecore XM Cloud, when an item is published, theExperience Edge for XM Connectorgenerates a static snapshot of theLayout Serviceoutput for that specific item. This means that only the published state of the page, including its components and data sources, is pushed toExperience Edge.
If adata source item(such as a content item used in a component) is updated and published,that change alone will not update the published page on Experience Edge. This happens because the snapshot is linked to thepage item, not just the data source.
How to Make Data Source Changes Visible?To reflect changes made in adata source item, a developer must:
* Publish the related page item.This regenerates and updates the Experience Edge snapshot.
* Ifonly the data source is publishedwithout republishing the page, the changes will not be reflected on the live website.
Thus, the correct answer is:#B. A developer must publish the related page items.
* Sitecore Documentation on Experience Edge: https://doc.sitecore.com/xmc/en/developers/xm-cloud
/index-en.html
* Sitecore Headless Services (Layout Service & GraphQL): https://doc.sitecore.com/developers/101
/sitecore-experience-manager/en/sitecore-headless-services.html
* Publishing Content in XM Cloud: https://doc.sitecore.com/xmc/en/developers/xm-cloud/publishing- and-experience-edge.html References for XM Cloud Development:


質問 # 19
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. Add_name token to the template's standard values Title field.
  • C. Set $name token in the new item's content Title field.
  • D. Set_name token in the new item's content Title field.

正解：C

解説：
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.


質問 # 20
Where can a developer create and edit data templates?

  • A. Content Editor
  • B. Content Editor or Pages
  • C. Explorer or Portal
  • D. Pages or Explorer

正解：A

解説：
InSitecore XM Cloud,data templatesdefine the structure of content items, specifying which fields and field types are available. Developers canonly create and edit data templatesusing theContent Editor, which provides access to the template architecture under the/sitecore/templatesnode.
* Navigate to Content EditorinSitecore XM Cloud Portal.
* Expand/sitecore/templatesin the content tree.
* Right-clickthe folder where you want to create the template and selectInsert # Template.
* Define template sections and fieldsin the Template Builder.
* Save and Publishthe template to make it available for content creation.
* Content Editor is the designated tool for managing data templatesin Sitecore XM Cloud.
* Data templates do not exist in Pages or Explorer, as those are used for content and layout management.
* Portal does not include template editing functionality-it serves as an entry point for accessing Sitecore services.
* A. (Pages or Explorer)# Pages is used for visual editing, and Explorer is for browsing items, not creating templates.
* B. (Explorer or Portal)# Neither provides access to data templates.
* C. (Content Editor or Pages)# Pages is only for layout and content management, not for template editing.
* Managing Data Templates in Sitecore XM Cloud
* Sitecore Content Editor Overview
* Sitecore XM Cloud Official Documentation
Steps to Create and Edit Data Templates in Content EditorWhy is Option D Correct?Why Other Options Are Incorrect?Relevant XM Cloud Documentation References:


質問 # 21
When deploying to XM Cloud, how are Sitecore Content Serialization (SCS) serialized items created in the Content Management (CM) instance?

  • A. A build pipeline must be created to use the SCS CLI push commands to push content after the XM Cloud Deploy app finishes.
  • B. The XM Cloud deploy process uses the SCS CLI to do a push once the CM instance is active.
  • 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 serialized item batches through REST APIs at the XM Cloud CM to speed up serialization.

正解：C

解説：
InXM Cloud, Sitecore Content Serialization (SCS) is used to manage serialized items and synchronize them with theContent Management (CM) instance. Unlike traditional Sitecore deployments where items are manually pushed usingSCS CLI, XM Cloud follows an automated approach usingItems as Resources (IAR).
* During the Deployment Process:
* TheXM Cloud Deployprocess packagesserialized contentinto anItems as Resources (IAR) file.
* This IAR file contains theserialized Sitecore itemsand is included in the deployment package.
* When the CM Instance Starts:
* The IAR file is automaticallylayered into the CM database, ensuring the content structure is synchronized without requiring manual SCS CLI commands.
* Benefits of the IAR Approach:
* Faster and More Reliable: Instead of pushing serialized items manually, theIAR file is pre- packagedand automatically applied.
* No Additional Build Steps Required: Unlike traditional deployments where a separate script or pipeline is needed to push items, XM Cloudhandles this automatically.
* Ensures Content Integrity: Items in the IAR file are versioned and deployedconsistently across environments.
How Sitecore Content Serialization (SCS) Works in XM Cloud Deployments:
Why Are the Other Options Incorrect?#A. The XM Cloud deploy process uses the SCS CLI to do a push once the CM instance is active.
* Incorrect, because XM Cloud doesnot rely on the SCS CLI for pushing itemsduring deployment.
Instead, it packages the items into anIAR file, which is automatically applied.
#C. A build pipeline must be created to use the SCS CLI push commands to push content after the XM Cloud Deploy app finishes.
* Incorrect, because XM Cloudautomatically deploys items via the IAR file. There is no need for a separate pipeline to push serialized content manually.
#D. The XM Cloud deploy process uses serialized item batches through REST APIs at the XM Cloud CM to speed up serialization.
* Incorrect, because Sitecore doesnot use REST APIs to push serialized itemsin XM Cloud deployments. Instead, the IAR mechanism ensures content is deployed efficiently.
* Sitecore XM Cloud Content Serialization (SCS) Overview- Sitecore Content Serialization in XM Cloud
* Understanding Items as Resources (IAR) in XM Cloud- IAR Deployment in Sitecore XM Cloud
* Best Practices for XM Cloud Deployments- XM Cloud Deployment Guide
References for Further Learning:


質問 # 22
When a developer designates a Sitecore template field multilist type, what should they do next?

  • A. Add standard values to the item.
  • B. Set the multilist list item's data source.
  • C. Add a multilist field to the template.
  • D. Add the list items to the multilist item.

正解：B

解説：
After designating a Sitecore template field as a multilist type, the next step is to set the data source for the multilist. This involves specifying the location within the content tree from which the list items will be drawn.
The data source defines the scope of items that can be selected and displayed in the multilist.
References:The Sitecore XM Cloud documentation provides guidance on configuring selection fields, including multilists.It details how to control the list of items by setting the Source property, which determines the items that appear in the selection list1.Additionally, developers can use the Sitecore.Data.Fields.
MultilistField class to manage the items in a multilist field, including setting the data source2.


質問 # 23
Why should a developer assign security to roles instead of users when setting up security on a site?

  • A. Security can be managed more efficiently as the rights and permissions apply to a group of users.
  • B. Individual users with a role can set and configure their own item security permissions.
  • C. Role-based security allows multiple users to have the same username.
  • D. Security roles can assign individual rights and permissions to be configured by users.

正解：A

解説：
According to the Sitecore XM Cloud Documentation for Developers1, security roles define how different users access different types of records in Sitecore. To control access to data and resources, you can create or modify security roles and change the security roles that are assigned to your users. A user can have multiple security roles. Security role privileges are cumulative.Users are granted the privileges that are available in each role that's assigned to them2.
This makes it easier for you to manage your security system because you do not necessarily have to assign access rights for each item in your content tree.Instead, you only need to assign and manage the access rights on the parent items and then specify whether their descendants can inherit these access rights3.


質問 # 24
Which of the following are ways to create an XM Cloud environment?

  • A. The CLI, the Deploy app, or Rest API.
  • B. Environments are automatically created during the deployment; it is not required to create environments explicitly.
  • C. The only way to create a cloud environment is from the Sitecore Cloud Portal Ul.
  • D. Defining the environment at .env file from the source code (laC) and re-deploying it.

正解：A

解説：
According to the Sitecore XM Cloud Documentation for Developers1, there are three ways to create an XM Cloud environment:
Using theSitecore CLI, which is a command-line tool that allows you to perform operations against local or remote XM Cloud instances.You can use the Sitecore CLI to create a project and an environment using thesitecore project createandsitecore environment createcommands2.
Using theXM Cloud Deploy app, which is a web application that allows you to create and manage projects, environments, and deployments.You can use the XM Cloud Deploy app to create a project and an environment using the user interface3.
Using theXM Cloud Deploy API, which is a RESTful API that allows you to programmatically interact with the XM Cloud Deploy app.You can use the XM Cloud Deploy API to create a project and an environment using HTTP requests4.
2:Walkthrough: Creating an XM Cloud project using the Sitecore CLI3:Create a project in the Deploy app4:
[XM Cloud Deploy API Reference]1:XM Cloud Documentation for Developers - Sitecore


質問 # 25
A developer is tasked with creating an item using the Sitecore Authoring and ManagementGraphQL API.
Which of the following GraphQL mutations is the correct way to create a new item?

  • A. create Templateltem
  • B. createltem
  • C. updateltem
  • D. createOrUpdateltem

正解：B

解説：
InSitecore XM Cloud, the correct GraphQL mutation to create a new item using theAuthoring and Management GraphQL APIiscreateItem. This mutation allows developers to programmatically create content items within Sitecore while specifying the required parent item, template, and field values.
Correct Mutation Examplemutation {
createItem(
parent: "/sitecore/content/Home",
name: "NewPage",
template: "Sample/Sample Item",
fields: [
{ name: "Title", value: "My New Page" },
{ name: "Text", value: "This is a sample text content." }
]
) {
item {
id
name
path
}
}
}
* parent# The path or ID of the parent item where the new item should be created.
* name# The name of the new item.
* template# The template that defines the structure of the item.
* fields# The array of field values assigned to the new item.
* A.createOrUpdateItem# This mutation does not exist in Sitecore GraphQL API.
* B.createTemplateItem# This is an incorrect name; Sitecore does not provide such a mutation.
* D.updateItem# This mutation is used to update an existing item, not create a new one.
* Sitecore GraphQL API for Authoring and Management
* GraphQL Mutation to Create an Item
* Sitecore XM Cloud Developer Documentation
Explanation of Parameters:Why Other Options Are Incorrect?Relevant XM Cloud Documentation References:


質問 # 26
Which of the following is part of the out-of-the-box technology stack for XM Cloud?

  • A. Python
  • B. jQuery
  • C. React
  • D. Svelte Kit

正解：C

解説：
XM Cloud includes a modern technology stack that supports various frameworks and libraries for development. React is part of this stack, as it is commonly used in conjunction with Sitecore's headless services and JSS (JavaScript Services) for building dynamic user interfaces.
References:The Sitecore XM Cloud documentation mentions the use of modern frameworks and libraries, including React, as part of its technology stack1. This aligns with the industry's move towards more flexible and modular front-end development practices.


質問 # 27
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, an icon to represent the device
  • B. Device width, visibility, responsive breakpoints
  • C. Device height, visibility, an icon to represent the device
  • D. Device height, visibility, responsive breakpoints

正解：A

解説：
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.


質問 # 28
Which of the following needs to happen for a developer to be able to log in into the XM Cloud Deploy app?

  • A. An Organization Admin or Organization Owner must update their role using the XM Cloud Deploy app.
  • B. Only the Organization Owner can update their role in the Sitecore Cloud Portal.
  • C. Only the Organization Owner can update their role using the XM Cloud Deploy app.
  • D. An Organization Admin or Organization Owner must update their role in the Sitecore Cloud Portal.

正解：D

解説：
InSitecore XM Cloud, access to theXM Cloud Deploy appis managed throughthe Sitecore Cloud Portal.
To allow a developer to log in, theiruser role must be updatedto include the necessary permissions.
* TheSitecore Cloud Portalis the central place whereuser roles and permissionsare managed.
* Only users with thecorrect role assignmentscan access theXM Cloud Deploy app.
* Both anOrganization Adminand anOrganization Ownerhave the ability toupdate a user's roleto grant them access.
* (B) Only the Organization Owner can update their role in the Sitecore Cloud Portal # Incorrect
* TheOrganization Adminalso has permission to manage users and update roles.
* It isnot restrictedto just theOrganization Owner.
* (C) Only the Organization Owner can update their role using the XM Cloud Deploy app # Incorrect
* User role management cannot be done from the XM Cloud Deploy app.
* Allrole updates must be made in the Sitecore Cloud Portal.
* (D) An Organization Admin or Organization Owner must update their role using the XM Cloud Deploy app # Incorrect
* The XM Cloud Deploy app does not handle user management.
* Roles must be managedthrough the Sitecore Cloud Portal, not through XM Cloud Deploy.
#Correct answer: A (An Organization Admin or Organization Owner must update their role in the Sitecore Cloud Portal)#Why Other Options Are Incorrect:
* Log in to the Sitecore Cloud Portal(https://portal.sitecorecloud.io).
* Go to "User Management."
* Find the developer's user account.
* Assign the appropriate role(e.g., "Deployment User" or another suitable role).
* Save changes- the developer should now be able to access the XM Cloud Deploy app.
Steps to Grant Access to the XM Cloud Deploy App
* Sitecore Cloud Portal Documentation- Managing Users and Roles
* Sitecore XM Cloud Deployment Guide- Working with XM Cloud Deploy
* Security Best Practices in Sitecore XM Cloud- User Access Control
References:


質問 # 29
What is the sitecore.json file in a development solution?

  • A. The configuration file for the Sitecore development tooling
  • B. The environment variables file for the Sitecore Docker deployment
  • C. A custom configuration file defining a solution for headless environments
  • D. The solution integration file needed for deploying code changes to the environment

正解：A

解説：
InSitecore headless development (JSS with Next.js), thesitecore.jsonfile plays a crucial role in configuring Sitecore development tooling. It contains settings related toJSS applications, including SitecoreAPI endpoints, deployment configurations, and serialization settings.
* Thesitecore.jsonfile is primarily used inJSS applicationsto configure development tools such as:
* JSS CLI(@sitecore-jss/sitecore-jss-cli)
* API endpoint definitions
* Serialization and deployment settings
* This file is located at therootof a JSS-based Sitecore project.
#Correct answer: B (The configuration file for the Sitecore development tooling)Example: Typical sitecore.jsonStructure{
"instancePath": "..\\docker\\build",
"apiKey": "{YOUR_SITECORE_API_KEY}",
"sitecore": {
"instanceUrl": "https://xmcloud.localhost",
"layoutService": "/sitecore/api/layout/render/jss"
},
"jss": {
"appName": "my-jss-app",
"watchPaths": ["src/components", "src/content"]
},
"serialization": {
"root": "./src/sitecore",
"modules": ["core", "master"]
}
}
* Defines the Sitecore instance URLfor headless applications.
* Specifies API keysfor connecting withSitecore Layout Service & GraphQL API.
* Controls serialization settingsfor content synchronization.
* Configures JSS app name and deployment paths.
* Used by JSS CLIfor deploying and syncing data with Sitecore.
Key Features ofsitecore.json:
* (A) The environment variables file for the Sitecore Docker deployment # Incorrect
* Environment variables for Sitecore Docker are typically stored in.envordocker-compose.override.
yml,notsitecore.json.
* Thesitecore.jsonfile isspecific to Sitecore JSS and development tooling, not Docker.
* (C) The solution integration file needed for deploying code changes to the environment # Incorrect
* Code deploymentis managed byXM Cloud Deploy, Next.js build processes, or GitHub Actions.
* sitecore.jsonis usedfor development configuration, not deployment automation.
* (D) A custom configuration file defining a solution for headless environments # Incorrect
* Whilesitecore.jsonisrelated to headless development, it isnot a custom configuration file.
* It is astandardized configuration filefor Sitecore'sJSS tooling and CLI.
#Why Other Options Are Incorrect:
* Ensure correct API keysand Sitecore instance URL are configured.
* Use serialization settingsto sync Sitecore items between local and cloud environments.
* Leverage JSS CLI(jss deploy config) to verify thesitecore.jsonsettings before deployment.
Best Practices for Usingsitecore.jsonin XM Cloud Development
* Sitecore JSS Documentation- Understanding sitecore.json
* JSS CLI & Development Setup- Sitecore JSS CLI Guide
* Sitecore XM Cloud Serialization- Using Serialization in Headless Development References:


質問 # 30
A developer is working with Sitecore's Authoring and Management API to manage their Sitecore content using GraphQL. They want to explore and interact with the API using the GraphQL integrated development environment (IDE). Which of the following statements is correct about using the GraphQL IDE?

  • A. The GraphQL IDE provides read-only access to the API.
  • B. The GraphQL IDE is only available for non-production environments to ensure secure interactions.
  • C. A developer needs to be in the sitecore\Admin role to access the GraphQL IDE.
  • D. A developer needs to be in the sitecore\Sitecore Client Users role to access the GraphQL IDE.

正解：C

解説：
Sitecore XM Cloud provides aGraphQL Integrated Development Environment (IDE)to allow developers toexplore and interactwith the Sitecore Content API. This IDE is available at:
#/sitecore/api/graph/ide
For security reasons,only users with the sitecore\Admin role can access this GraphQL IDE. This restriction ensures that only authorized users can interact with and test queries against the Sitecore content data.
Now, let's analyze each option:
* (A) Correct## A developer must have the sitecore\Admin role to access the GraphQL IDE.
* (B) Incorrect## The sitecore\Sitecore Client Users role does not grant access to the GraphQL IDE.
* (C) Incorrect## The GraphQL IDE allows bothread and writeoperations, not just read-only access.
* (D) Incorrect## The GraphQL IDE is available for both development and production environments, but proper access control should be enforced in production.
References & Learning Resources
#Sitecore XM Cloud GraphQL Overview#GraphQL IDE Access Control#Sitecore Roles and Permissions


質問 # 31
A developer needs to remove a site collection folder. Which script should they run from the Content Editor?

  • A. Remove Site Collection Folder
  • B. Remove Site Folder
  • C. Remove Site Collection
  • D. Remove Folder

正解：A

解説：
To remove a site collection folder in Sitecore XM Cloud, the developer should run the "Remove Site Collection Folder" script from the Content Editor. This script is specifically designed to remove site collection folders and all associated items, ensuring a clean removal process.
References:The Sitecore XM Cloud documentation provides instructions on how to remove site collections, site collection folders, sites, and site folders using scripts available in the Content Editor1.


質問 # 32
A developer wants to invite a team member to their organization in the Sitecore Cloud Portal andgive them access to only three specific apps. What role should they assign to this new team member?

  • A. Organization Member
  • B. Organization Owner
  • C. Organization User
  • D. Organization Admin

正解：A

解説：
InSitecore XM Cloud, user access and role management are handled through theSitecore Cloud Portal.
When inviting a new team member,the appropriate role must be assignedto ensure they have the correct level of access to specific applications.
* "Organization Member"is the correct role because:
* Itallows access to specific appswithin the organization.
* Admins canmanually assign accessto only thethree specific appsrequired.
* It provideslimited permissions, ensuring the user does not get full control over all resources.
* (A) Organization User # Incorrect
* There isno "Organization User" rolein Sitecore Cloud Portal.
* (C) Organization Owner # Incorrect
* AnOrganization Ownerhasfull controlover all apps and settings.
* This role istoo broadand gives unnecessary administrative access.
* (D) Organization Admin # Incorrect
* AnOrganization Admincan manageall applicationswithin the organization.
* This role istoo powerfulif the user only needs access to three apps.
#Correct answer: B (Organization Member)#Why Other Options Are Incorrect:
* Log into the Sitecore Cloud Portal.
* Navigate to "User Management."
* Invite the team memberby entering their email.
* Assign the "Organization Member" role.
* Manually grant accessto the specific three apps they need.
Best Practice for Inviting Users to Sitecore XM Cloud
* Sitecore Cloud Portal Documentation- Managing Users and Roles
* Best Practices for Access Control- User Roles in Sitecore XM Cloud
* Sitecore Cloud Portal Overview- Inviting Team Members
References:


質問 # 33
A developer has set up a local XM Cloud development environment and would like to connect Sitecore Pages to their locally running XM Cloud instance. However, after following the necessary steps, they're facing issues with the connection. Of the options below, what is the most likely potential reason for this issue?

  • A. The environment variable "SITECORE_Pages_CORS_Allowed_Origins" is not correctly configured to include pages.sitecorecloud.io.
  • B. The value of the local storage entry ''Sitecore.Pages.LocaIXmCloudUrl" should be set to https://pages.
    sitecorecloud.io.
  • C. The value of the local storage entry "Sitecore.PagesXmCloud" should be setto enabled.
  • D. The browser developer tools console does not support the local storage functionality required for this connection.

正解：A

解説：
When connectingSitecore Pages(the visual page editor in XM Cloud) to alocal XM Cloud development environment, the connection may fail due toCORS (Cross-Origin Resource Sharing) restrictions.
* Sitecore Pagesis hosted onhttps://pages.sitecorecloud.io, which loads content from the developer's local Sitecore instance.
* Thelocal Sitecore instance must allow requests frompages.sitecorecloud.io, or the connection will fail due toCORS policy restrictions.
* To fix this, the developer must ensure that theenvironment variable
SITECORE_Pages_CORS_Allowed_Originsis correctly setto includehttps://pages.sitecorecloud.io.
* In a localDocker-based XM Cloud setup, this can be configured indocker-compose.override.ymllike this:
#Correct answer: D (The environment variableSITECORE_Pages_CORS_Allowed_Originsis not correctly configured to include pages.sitecorecloud.io.)environment:
- SITECORE_Pages_CORS_Allowed_Origins=https://pages.sitecorecloud.io
* If running Sitecore locally without Docker, this setting should be added to theappsettings.jsonfile or set as a system environment variable.
* (A) The value of the local storage entry'Sitecore.Pages.LocaIXmCloudUrl'should be set to
https://pages.sitecorecloud.io# Incorrect
* Thecorrect keyis'Sitecore.Pages.LocalXmCloudUrl', but it should point tothe local Sitecore instance, nothttps://pages.sitecorecloud.io.
* Example:
#Why Other Options Are Incorrect:localStorage.setItem('Sitecore.Pages.LocalXmCloudUrl',
'https://xmcloud.localhost');
* This step helps Sitecore Pages find the local instance, butCORS issues must still be resolved separately.
* (B) The browser developer tools console does not support the local storage functionality required for this connection # Incorrect
* Browserdeveloper tools do supportlocal storage.
* If local storage were an issue, developers couldmanually add entriesvia the console.
* Example:
localStorage.getItem('Sitecore.Pages.LocalXmCloudUrl'); // Should return 'https://xmcloud.localhost'
* (C) The value of the local storage entry"Sitecore.PagesXmCloud"should be set to"enabled"# Incorrect
* There isno such required settingnamed"Sitecore.PagesXmCloud".
* The required setting is'Sitecore.Pages.LocalXmCloudUrl', which must be set tothe local instance URLinstead.
* Ensure CORS settings are correctly configured:
* Addhttps://pages.sitecorecloud.ioto theSITECORE_Pages_CORS_Allowed_Origins environment variable.
* Manually set the local Sitecore URL in browser storage:
* Open Developer Tools (F12in Chrome).
* Run:
Best Practices for Connecting Sitecore Pages to a Local XM Cloud InstancelocalStorage.setItem('Sitecore.
Pages.LocalXmCloudUrl', 'https://xmcloud.localhost');
* Verify network requests:
* Check for CORS-related errors in the browserConsole (F12 > Console tab).
* Checkfailed requests in the Network tab.
* Sitecore Pages Integration with Local Development- Troubleshooting Sitecore Pages
* CORS Configuration in XM Cloud- Allowing Origins for Sitecore Pages
References:


質問 # 34
A developer can reference an external code base that includes components so they can be used in the Components builder interface. Which of the following are possible results of adding React components to the Components builder? Select all that apply.

  • A. The registered component is part of the Components library.
  • B. The registered component is scoped to only one environment.
  • C. A content author can enter values for the defined input parameters.
  • D. The registered component can be previewed in the Component builder.

正解：A、C、D

解説：
According to the Sitecore XM Cloud Documentation for Developers1, the Components builder is a tool that allows you to create and manage components for your XM Cloud Pages. You can use the Components builder to register React components from an external code base, such as a GitHub repository or a local folder. When you add a React component to the Components builder, the following results are possible:
B: A content author can enter values for the defined input parameters.When you register a React component, you can define input parameters that allow the content author to customize the component's appearance and behavior. For example, you can define a text parameter that lets the content author enter the title of the component.The input parameters are displayed in the Properties panel of the XM Cloud Pages editor2.
C: The registered component is part of the Components library.When you register a React component, it becomes available in the Components library, which is a collection of components that you can use in your XM Cloud Pages. You can access the Components library from the Components builder or the XM Cloud Pages editor.You can also organize your components into categories and subcategories in the Components library3.
D: The registered component can be previewed in the Component builder.When you register a React component, you can preview how it looks and behaves in the Component builder.You can also edit the component's code, input parameters, and metadata in the Component builder4.
The following result is not possible:
A: The registered component is scoped to only one environment.When you register a React component, it is available in all the environments of your XM Cloud project. You cannot limit the component's availability to a specific environment.However, you can controlthe component's visibility and accessibility by using the Publish and Archive actions in the Component builder4.
2:Register a React component | Sitecore Documentation3:Manage the Components library | Sitecore Documentation4:Manage a component in the Component builder | Sitecore Documentation1:XM Cloud Documentation for Developers - Sitecore


質問 # 35
A multinational clothing company wants to create a structured online presence for its various brands and countries. They want to ensure that the different brands and countries have their own dedicated content within the same Sitecore instance. Which approach should they take to achieve this using XM Cloud's content architecture?

  • A. Create a single site collection and site for all brands and countries and also manage their resources manually.
  • B. Use separate instances of XM Cloud for each brand and country to maintain separation.
  • C. Create individual site collections for each brand and a site for each country.
  • D. Create a separate site for each brand and use a language per country.

正解：C

解説：
XM Cloud's content architecture supports the creation of individual site collections for each brand, with separate sites for each country. This approach allows a multinational company to maintain a structured online presence, ensuring dedicated content for different brands and countries within the same Sitecore instance.
References:The Sitecore XM Cloud documentation outlines the ability to create headless site collections and sites, supporting multiple brands for a single company or multiple languages or locations for a single brand1.
This is part of the SXA content architecture, which includes site collections and sites, allowing for multiple sites on a single instance of Sitecore1.


質問 # 36
......

最新100%合格率保証付きの素晴らしいSitecore-XM-Cloud-Developer試験問題PDF：https://www.passtest.jp/Sitecore/Sitecore-XM-Cloud-Developer-shiken.html

Sitecore-XM-Cloud-Developer有効な認定試験問題集解答学習ガイド：https://drive.google.com/open?id=1NiYYZc3DVJM1RhNg8YVoHDpmKo5FQ_Wc

関するブログ

もっと
Sitecore-XM-Cloud-Developer 無料問題集