Sitecore-10-NET-Developer Exam Dumps - Sitecore Engagement Cloud Questions and Answers

 If the Sitecore Content Management instance can be accessed by multiple host names, you need to add AllowedCorsOriginsGroup for each site to the Identity Server configuration. This will enable the users for each site to be able to log in to the Sitecore shell using the Identity Server. The AllowedCorsOriginsGroup element defines a group of URIs that are allowed to make cross-origin requests to the Identity Server. You can use multiple subnodes to define more than one URI, or you can use the | symbol to separate URIs within a node. You can also use the {AllowedCorsOrigin} template to simplify the configuration. When you use that template, all origins (hosts) are notified about the sign-out1. References:

• Single sign-out

Workflows consist of three elements – states, commands and actions1. A workflow state defines the status of an item in a workflow, such as Draft, Awaiting Approval, or Published. A workflow command defines the transition from one state to another, such as Submit, Approve, or Reject. A workflow action defines the operation that is performed when a command is executed, such as sending an email notification, validating an item, or publishing an item. Workflows can contain any number of workflow states and be as simple or complex as required. Items do not necessarily have to move through all the workflow states that you have defined. Some states can be optional or only applicable to certain kinds of content1. References:

• Workflows and the Workbox

Field editor buttons are custom experience editor buttons that allow content authors to edit multiple fields of an item in a pop-up window. This is useful for complex fields that are not easily editable in the experience editor, such as multilist fields, checkbox fields, or image fields. Field editor buttons can also be configured to edit the fields of the data source item of a rendering, rather than the page item. Field editor buttons can improve the content authoring experience by providing a convenient and consistent way to edit fields in the experience editor. References:

• 12
• 13
• 14

The $name token is a special token that can be used in fields on standard values items to instruct Sitecore to set the value of the field to the name of the item upon creation1. This token can be used in rich text, single-line text, and multi-line text fields2. To ensure that items created from a template automatically have the Title field populated with the name of the item, you should add the $name token to the template’s standard values Title field. This way, every item that inherits from the template will have the Title field set to the item name by default. You do not need to set the $name token in the new item’s content Title field, as this will only affect the specific item and not the template. The _name token is not a valid token in Sitecore and will not have any effect. References: 1: https://doc.sitecore.com/xp/en/developers/101/sitecore-experience-manager/the-name-token.html  2: https://doc.sitecore.com/xp/en/developers/sxa/93/sitecore-experience-accelerator/content-tokens.html

 Developing with the Sitecore ASP.NET Core Rendering SDK has the following benefits:

• It allows you to create independent applications that render Sitecore content. This means you can use any .NET Core framework or library to build your rendering host, and you do not need to install Sitecore on your development machine1.
• It helps you build small, lightweight .NET Core applications for Sitecore. These applications can run on any platform that supports .NET Core, such as Windows, Linux, or MacOS1.
• It depends on the Sitecore Layout Service. The Layout Service is a RESTful API that provides JSON data for Sitecore items and layouts. The ASP.NET Core Rendering SDK uses the Layout Service to fetch the data and metadata required to render Sitecore content12.
• It enables you to preview your code changes without having to restart the Sitecore environment. The ASP.NET Core Rendering SDK supports hot module replacement (HMR), which means you can see the changes you make to your code in the browser without refreshing the page or rebuilding the application13.

The following statements are not true about developing with the Sitecore ASP.NET Core Rendering SDK:

• It does not enable the Content Delivery instance to handle all of the development workload. The Content Delivery instance is still responsible for serving the Layout Service requests, but the rendering logic is handled by the ASP.NET Core application1.
• It does not allow you to remove ASP.NET from your solution. You still need ASP.NET to run the Sitecore Content Management and Content Delivery instances. The ASP.NET Core Rendering SDK only replaces the ASP.NET rendering engine for your rendering host1.
• It does not allow you to extend Sitecore pipelines using .NET Core. The Sitecore pipelines are part of the Sitecore configuration and run on the Sitecore server. The ASP.NET Core Rendering SDK does not have access to the Sitecore pipelines or the Sitecore context14.

References: 1: Sitecore ASP.NET Rendering SDK | Sitecore Documentation 2: Sitecore Layout Service | Sitecore Documentation 3: Headless development with the ASP.NET Rendering SDK | Sitecore Documentation 4: ASP.NET Core Rendering Engine | Sitecore Documentation