Sitecore-10-NET-Developer Exam Dumps : Sitecore 10 .NET Developer Exam

 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

Versioned layouts allow you to create different layouts for different versions of an item. This means you can have a specific layout for a specific version of the main page that is published for a specific period, such as a company anniversary celebration. You can easily revert to the original layout by switching back to the previous version of the main page. Versioned layouts are stored in the __Renderings field of the item, which is a versioned field. Versioned layouts are enabled by default in Sitecore 10. References:

• [Sitecore 10 .NET Developer Certification Study Guide], page 14
• [Sitecore Documentation: Versioned layouts]

Presentation details are the settings that define how and where content will be displayed on a webpage. They include the layout, the renderings, the placeholders, and the datasources for each rendering. Presentation details can be set at different levels in Sitecore, such as standard values, content items, or device items. However, for non-SXA websites, it is recommended to avoid setting presentation details directly on new content items, and instead use standard values. Standard values are the default values for the fields of a template, including the presentation details. By defining presentation details on standard values, you can ensure that all content items created from the same template will have the same presentation details by default. This eliminates the need to set presentation details for each individual content item, which can be time-consuming and error-prone. It also makes it easier to maintain and update the presentation details for a group of content items, as you only need to change the standard values once, and the changes will be inherited by all the content items based on that template. Setting presentation details on standard values also allows content authors to use the Experience Editor to edit the content and presentation of the items, without having to switch to the Content Editor. The Experience Editor is a more user-friendly and intuitive interface for content editing, as it shows the content in the context of the webpage. Therefore, by avoiding setting presentation details directly on new content items, you can improve the efficiency and consistency of your content creation and presentation process. References: Sitecore 10.0 Developer Documentation - Presentation details, Sitecore 10.0 Developer Documentation - Standard values