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

 Sitecore headless development is based on a decoupled architecture where the rendering host is a separate application that handles the presentation logic and the Content Delivery role is a Sitecore instance that handles the content management and delivery. The rendering host communicates with the Content Delivery role using Sitecore headless services, which are APIs that expose Sitecore content and layout data in a JSON format. The rendering host translates a visitor request to a content item in the Sitecore instance. The Sitecore instance using Sitecore headless services returns the content item and the associated presentation details, and so on, to the rendering host. The rendering host renders the content item for the visitor. This way, the rendering host can use any technology or framework that supports HTTP requests and JSON parsing, such as ASP.NET Core, React, Angular, Vue, etc. References:

• Headless development with the ASP.NET Rendering SDK
• Sitecore Headless Development FAQ
• Sitecore Headless Development

 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

 When creating your containerized Sitecore environment with Docker, you need two files to launch the containers: docker-compose.yml and .env. The docker-compose.yml file contains the configuration of the services that make up the Sitecore environment, such as the roles, networks, volumes, and dependencies. The .env file contains the environment variables that are used by the docker-compose.yml file, such as the Sitecore license path, the image tags, the host names, and the passwords. These files are recommended because they simplify the process of launching the containers and allow you to customize the environment according to your needs. References:

• Sitecore Containers documentation
• Docker Compose file reference
• [Environment variables in Compose]