Free Practice Questions for Sitecore Sitecore-10-NET-Developer Exam

Compatible renderings are renderings that have identical datasources (or no datasources) and are placed in the same module. By adding each rendering definition item to the Compatible Renderings option within each of the renderings, you can allow thecontent author to easily switch between different renderings without losing the datasource query. This reduces the chance of user error and improves the content authoring experience. Compatible renderings can be configured in the Content Editor or in Sitecore Rocks. References:

18

19

20

Dynamic component binding is a technique that allows you to define a placeholder in your view and then use the Experience Editor or the Content Editor to add, remove, or reorder the components that are rendered in that placeholder. This gives you more flexibility and control over the presentation of a page, as you can change the components without modifying the code. Dynamic component binding also supports personalization, as you can use the Rule Set Editor to define conditions and actions that determine whichcomponents are displayed to different visitors or segments. For example, you can personalize a component by specifying that visitors who meet some predefined conditions are shown a particular variant of the component. Static component binding, on the other hand, is a technique that renders a specific component in a specific location on the page. This means that the component is always the same and cannot be changed or personalized by the Experience Editor or the Content Editor. Static component binding is useful when you want to ensure consistency and simplicity in the presentation of a page, but it does not allow you to use personalization to change the component. References:

Component binding - Sitecore

MVC rules and personalization - Sitecore

Walkthrough: Personalizing components - Sitecore

When using Sitecore MVC, the static class that contains information about any current HTTP request is Sitecore.HttpContext. This class is a wrapper for the System.Web.HttpContext class, which provides access to the intrinsic objects of ASP.NET, such as Request, Response, Session, and Server. Sitecore.HttpContext also exposes some Sitecore-specific properties, such as Database, Device, Domain, and Site. Sitecore.HttpContext is different from Sitecore.Context, which is another static class that provides information about the current Sitecore context, such as Item, User, Language, and ContentDatabase. Sitecore.Request and Sitecore.HttpContext.Request are not valid classes in Sitecore MVC. References:

Sitecore.HttpContext Class - Sitecore

Sitecore.Context Class - Sitecore

HttpContext Class - Microsoft

 When developing with the Sitecore ASP.NET Core Rendering SDK, you need to register component renderers within the rendering host’s Startup.cs class to map a Sitecore rendering component name to an implementation. This allows the Sitecore Rendering Engine to render the content fetched from the Sitecore Layout Service using the appropriate component renderer. For example, you can map a Sitecore layout component name to a view component rendering or a partial view rendering. You can use the AddViewComponent() and AddPartialView() extension methods to register component renderers in the Startup.cs class. References:

[Sitecore 10 .NET Developer Certification Study Guide], page 18

Sitecore Documentation: Sitecore Rendering Engine

 Workbox is a Sitecore application that allows you to view and manage items that are in a workflow. Workbox displays the items that are in each workflow state and the commands that are available for each item. You can use Workbox to perform workflow actions, such as approving, rejecting, or editing items. Workbox also shows you the history and comments of each item in a workflow. Workbox is useful for content authorsand editors who need to review and publish items in a workflow. References: Sitecore 10.0 Developer Documentation - Workbox