Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. Sitecore
  5. Sitecore-XM-Cloud-Developer

Sitecore Sitecore-XM-Cloud-Developer Exam
Sitecore XM Cloud Developer Certification (Page 3 )

Updated On: 1-Feb-2026
Page 2 of 11
PDF with 50 Questions

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?

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

Answer(s): B

Explanation:

Access to the GraphQL IDE for exploring and managing Sitecore content via the Authoring and Management API requires a developer to have the sitecore\Sitecore Client Users role. This role grants the necessary permissions to use the IDE for various operations, not just read-only access.


Reference:

The Sitecore XM Cloud documentation specifies the role requirements for using the GraphQL IDE1. It also provides guidance on setting up and authoring content with the GraphQL playgrounds, which are part of the IDE2.



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.

  1. Write
  2. Debug
  3. Access
  4. Read
  5. Inheritance

Answer(s): A,D,E

Explanation:

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 - Sitecore 3: The security tools | Sitecore Documentation
2: The access rights | Sitecore Documentation



A developer is working on managing environments within the XM Cloud Deploy app. They have created a new environment for the project and linked it to a specific repository branch. However, they realize that they need to change the linked repository branch due to new developments in the project.
Which steps should they follow to achieve this?

  1. Delete the current environment and create a new one with the desired repository branch.
  2. Unlink the current repository branch and then relink the desired branch to the environment through the project's "Options" menu.
  3. Link the desired branch to the environment directly from the repository settings. The XM Cloud Deploy app will automatically update the linked branch.
  4. Go to the project page, click the environment, choose "Options," and then "Edit environment details." In the dialog, select the desired branch from the "'Link to branch" drop-down menu and save the changes.

Answer(s): D

Explanation:

According to the Sitecore XM Cloud Documentation for Developers1, you can link an environment to a specific branch of your repository in the XM Cloud Deploy app. This allows you to deploy different versions of your code to different environments. To change the linked branch for an existing environment, you need to follow these steps2:
On the navigation pane of the XM Cloud Deploy app, click Projects. On the Projects page, click the project that contains the environment where you want to change the linked branch.
On the project page, click the environment where you want to change the linked branch. On the environment page, click Options, then click Edit environment details. In the Edit environment details dialog, select the desired branch from the Link to branch drop-down menu.
Click Save to confirm your changes.

2: Manage an environment in the XM Cloud Deploy app | Sitecore Documentation 1: XM Cloud Documentation for Developers - Sitecore



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?

  1. An Organization Admin or Organization Owner must update their role.
  2. An Organization Admin or Organization Owner must update their role using the XM Cloud Deploy app.
  3. Only the Organization Owner can update their role in the Sitecore Cloud Portal.
  4. Only the Organization Owner can update their role using the XM Cloud Deploy app.

Answer(s): A

Explanation:

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 organization 1: XM Cloud Documentation for Developers - Sitecore



What information can be found in the deployment logs?

  1. Content Management and Content Delivery deployment logs
  2. Content Management instance and Rendering Hosting logs
  3. Provisioning, Deployment, and Publishing information
  4. Provisioning, Build, Deployment, and Post Action information

Answer(s): D

Explanation:

According to the Sitecore XM Cloud Documentation for Developers1, the deployment log displays the progress, status, warnings, and errors of an XM Cloud deployment. From the deployment log, you can also cancel a running deployment, rerun a failed deployment, promote the deployment to another environment, download logs, or open the XM Cloud Dashboard. The logs include information about:
Provisioning ­ the process of creating and configuring the resources required for the environment, such as the Content Management and Content Delivery instances, the database, the storage, and the network.
Build ­ the process of compiling the source code, running tests, and generating the deployment package.
Deployment ­ the process of deploying the package to the environment and applying any configuration changes.
Post Action ­ the process of performing any additional tasks after the deployment, such as publishing, indexing, or clearing caches.

1: XM Cloud Documentation for Developers - Sitecore



Viewing page 3 of 11
Viewing questions 11 - 15 out of 50 questions



Post your Comments and Discuss Sitecore Sitecore-XM-Cloud-Developer exam prep with other Community members:

Join the Sitecore-XM-Cloud-Developer Discussion