51 Sitecore Interview Questions To Prepare In 2024

September 2nd, 2020

Sitecore Interview Questions

This blog features 51 Sitecore Interview Questions, who are the most frequently asked questions by interviewers. These questions are bunched up after consulting with the top industry experts in the field of Sitecore Development. This blog is the only guide you need to master all the concepts required to clear a Sitecore interview.

 Sitecore Training should be your first choice to clear up your basics and move towards clearing the Sitecore certification exam. A good training will help you learn everything about the field, and this blog will only be needed for a reference for 51 Sitecore Interview Questions.

Now, without any further ado, let us begin to unlock the list of frequently asked 51 Sitecore interview questions. But first, here is a brief into Sitecore and its future.

An Introduction to Sitecore

Sitecore is a globally renowned software company that is known for its offering of two products. One is a powerful CMS (content management system) and the other is a completely-adaptive DMS (digital marketing system).

The demand for Sitecore developers is experiencing a good all-time high and is expected to continue on its upward graph. However, there is a greater degree of demand than there is supply, and once you complete your Sitecore online training, you will easily understand 51 Sitecore Interview Questions with Answers

These 51 Sitecore interview questions have been designed to help you gain insights on the current interview scenario. Having knowledge of the top questions will help you feel more confident during your interview and even ace it with flying colors.

51 Sitecore Interview Questions

Q1. What is Sitecore?

Ans: Sitecore is a very flexible Content Management System (CMS). It is one of the leading enterprise-level content management systems (CMS) using which you can create an enterprise websites and intranet portal websites. Sitecore was found in 2001 and it is built on Microsoft .NET platform. Sitecore also allows deployment via Microsoft Azure.

Q2. Why should you use Sitecore?

Ans: Here are the top features of Sitecore CMS that separates it from other CMS:

  • It provides out-of-the-box flexibility and is highly customizable
  • With Sitecore, you can create a multi-language site with little effort
  • Provide personalized user experience and content variation features
  • E-commerce Services
  • It has out-of-the-box engagement automation and engagement analytics
  • Email Campaign Manager
  • Integration with Cutting Edge Technology
  • Highly Scalable
  • Improved Search Engine Optimization
  • User-based and Role-based Security

Q3. Which is the latest version of Sitecore?

Ans: Latest Sitecore Version is 10.3 [February 15, 2023]

Q4. First look at Sitecore?

Ans: Sitecore user interface is very similar in look and feels to windows desktop, which makes it easy for new users to pick up and learn Sitecore. There are three ways you can log in to Sitecore – Desktop, Content Editor, and Page Editor.

Sitecore Login Screen:

Welcome to Sitecore
Sitecore Login Screen

Sitecore Desktop Screen:

Sitecore Desktop
Sitecore Desktop Screen

Sitecore Content Editor Screen:

Sitecore Content Editor
Sitecore Content Editor Screen

Sitecore Page Editor Screen:

Sitecore Page Editor
Sitecore Page Editor Screen

Q5. What is Desktop?

Ans: When you are login using Sitecore Desktop you will find a rich set of features using which you can

  • Create and Install packages
  • View files using File Explorer
  • Clean up a database using Control Panel
  • Change the desktop background
  • Change the application options
  • Many more Sitecore Desktop user interfaces have many feature options compared to the Content Editor user interface..

Q6. What is a Content Editor?

Ans: The Content Editor is designed for more experienced content authors who feel comfortable working with a computer, Microsoft Word, and familiar with Sitecore functionality to add, edit or remove the content of the website using a rich set of features. Content Editor Interface has fewer feature options compared to the Desktop interface but has more feature options compared to Page Editor Interface..

Q7. What is the Page Editor?

Ans: Content authors are generally focused on the quality and accuracy of the material displayed on the Web site and not on the design, style, and layout of the site. For this reason, most content authors prefer to work in such an interface that is designed to meet their needs and not those of the developers and designers who create Websites.

With this in mind, Sitecore CMS allows content authors to edit and create items directly on the Web page with the Page Editor. The Page Editor is the simplest editing tool that Sitecore contains. It is designed for inexperienced content editors who edit and write content items directly on the page. It is a WYSIWYG editor (what you see is what you get) and limits the amount of functionality that is presented to the user.

When you log in to the Content Editor, the items that make up your Web site are presented to you in a very different way than they are in the Page Editor. In the Page Editor, you see the items as they are presented on the Web site.

Q8. How many databases are associated with Sitecore?

Ans: There are three databased associated with Sitecore:

  1. Core Database
  2. Master database
  3. Web database

Q9. What is the core database?

Ans: This core database has two purposes:

  • The core database contains all Sitecore settings. It contains definitions for the Sitecore user interface (Content Editor, Page Editor, etc.). This is where you can add a context menu option to the Content Editor or a new ribbon button to the Page Editor.
  • It contains the ASP.NET membership tables that drive authentication and security.

You May Also Read - What Is Sitecore? A Beginner's Guide To Learn Sitecore

Q10. What is the master database?

Ans: The master database is the authoring database - it contains all versions of content. Whenever a new piece of content is created, edited, or deleted it is stored here. This is the database that content authors interact with and is the default database used by the Sitecore Content Editor.

Q11. What is a web database?

Ans: The web database contains the live content of the website. When a content editor publishes some content then it is copied from the master database to the web database. It is a subset of the master database and optimized for size and speed.

12. What is the content author?

Ans: A website content writer or the content author is a person who specializes in providing relevant content for websites. Every website has a specific target audience and requires a different type and level of content. Content should contain words (keywords) that attract and retain users on a website. Content written specifically for a website should concentrate on a specific topic. It should further be easy to read, offering the information in easy to understand clusters or laid out in bullet points.

Q13: What is Item in Sitecore?

Ans: An item is a record in the database. Items are the basic building blocks of a Sitecore Site. An item may represent any kind of information, e.g. a piece of content, a media file, a layout, etc. Items always have a name and ID that uniquely identifies the item within the database. Items have a template that defines which fields the item contains. An item representing a single version of a piece of content is a single language. An item can be retrieved from a database using Items.

Q14. What is Template in Sitecore?

Ans: Sitecore uses data templates to define structures of items. Templates contain fields to represent individual elements. Each data template field has a type, such as Text, Image, Checkbox, and various other field types.

Q15. What is publishing?

Ans: By this time you are now aware of the fact that whenever you add, edit and delete any item in Sitecore, it will be stored in the master database. Now in order to move this change to a live website, you need to use publishing. Publishing is a process that will help you to copy updated items from the master database to a web database.

Q16. Which are the different types of publishing?

  1. Republish: As the name implies, it will publish every item no matter whether it is changed or not. It is intended to be used when you are publishing a new site first time. This is most time-consuming publishing method as it blindly publishes all items
  2. Smart Publish: This method works smartly by comparing each item in the master database with the item in a web database. Sitecore maintains a revision number for each item which gets changed whenever the item gets updated. By comparing this revision number with the web database, it will create a list of updated items changes and will publish only those items changes. Even though this method is comparing each item, it is much faster than the republish method.
  3. Incremental Publish: Every time an item is changed, it is added to the publishing queue. This applies both to changes made through the Sitecore user interface and changes made programmatically. Doing an incremental publish will only publish the items in the publishing queue. Therefore only items that have been changed will be published and Sitecore does not have to do any comparisons to figure out which items have been changed. This way of publishing is therefore by far the fastest. Republish and smart publish do not use the publishing queue

Q17. What is a Staging Environment?

Ans: As the best Sitecore practice, there should be separate Sitecore instances where all changes should be deployed before they are moved to the live site (production environment). This Sitecore instance is treated as a staging environment. A meaningful URL is given to the stage environment like http://stag.yoursite.com

Once the user is happy with the changes on staging environment, deployment is then roll-out to production environment.

Q18. What is the Production Environment?

Ans: Like staging Sitecore instance, there should be separate Sitecore instances for the production environment. The production environment is nothing but a live site that is getting used by the outside world. If this Sitecore instance gets down, that means your live website is down. Respective live URL of above stage URL http://stag.yoursite.com would be http://www.yoursite.com

You May Also Read - Sitecore Developer: Skills, Experience, And Salary

Q19. What is versioning in Sitecore?

Ans: In Sitecore content, authors have the ability to make a piece of content versionable. Each version of an item begins as a replica of the original or of another version and are all stored in Sitecore. Previous versions operate individually and can be published as the active version of a content item instead of the most recent version. At any time an active version can be rolled back to a previous version and vice versa.

Q20. Which are different types of view modes in Sitecore?

  1. Preview Mode
  2. Page-Editor mode
  3. Normal mode

Q21. What are the standard values in Sitecore?

Ans: Standard values were first introduced in Sitecore 5.3 to overcome some of the issues experienced with the predecessors of standard values – “Masters”. In Sitecore 6 masters were completely removed and the concept of standard values took over.

Standard values are a way of having default or fallback values for fields in Sitecore, meaning that when items are created, you can specify a field value that should be used by default. This does not only account for custom fields you build but also standard fields in Sitecore such as presentations and insert options. This means that you can specify a value on the standard values, and when you create a new item that inherits from this template, it will by default use the values specified on the standard values.

Q22. What is standard fields?

Ans: Sitecore provides few common fields for all items, these fields are called standard fields. These fields can help you to:

  1. Set icon of your Sitecore item
  2. Check last item update status
  3. Check the current status of the item's workflow
  4. And many more…

Q23. What is raw values?

Ans: Sitecore always stores field values as plain text in the appropriate Sitecore database (in the Value column of the Fields table). In Sitecore, there are two ways of getting data out of a field – the raw value or the rendered value.

A field's raw value is how the data is stored in the underlying database – for simple fields such as Single Line Text, there is no difference between the rendered and raw values; it's just plain text. This is not the case for more complex field types, such as General Link, Image, or Rich Text. Take the raw value of a General Link field, for instance – if you enable raw values in the Content Editor (by clicking the View tab and ticking Raw values) and look at an item with a General Link field, you will see that the value stored in the database is custom XML:

The following table provides an example of each field type, as the value is stored in the Sitecore database.

Sitecore Database

Q24. Which field contains item sort value?

Ans: The sort order field under the Appearance section contains item sort value. Decrease sort value to move up and increase sort value to move down items in the tree.

Sitecore Field

Q25. What is Layout in Sitecore?

Ans: Whenever a user sends any request to Sitecore through a URL, Sitecore resolves that item by generating a visual representation of that item. The layout provides the basic structure of this visual representation. The layout is a container that contains a different component of the page. Technically speaking, your.ASPX page is the layout and.ASCX, .CS or.XSLT file is a component (user control).

Q26. Which are the different types of rendering in Sitecore?

Ans: There are basically three types of rendering used by Sitecore developers.

  1. Sub layout Rendering (mostly used): This is the developer's favorite and most used rendering method. Sub layout is nothing but.ASCX user control.
  2. Web Control Rendering (average used): ASP.NET web controls are created to use this rendering. Create.CS file for this rendering.
  3. XSL Rendering (rarely used): Very few programmers are using this rendering as writing the XSLT program is a bit difficult and it has limited features. Create.XSLT file to use XSL rendering.

Q27. What is the difference between the droplist and drop link field type?

Ans: By the time you reach to this question, you must be knowing that Sitecore always stores field values as plain text in the appropriate Sitecore database (in the Value column of the Fields table).

Sitecore has two different types of drop-down lookup fields that are available: Droplist and Drop link. Both of them function essentially the same way: they point to a Sitecore data item and list its children in a drop-down list for a content editor. This is a great tool because it allows you (as a data designer) to build a nice set of lookup values and not worry that editors will fat-finger these values.

But why are there the two, and what's the difference between them? Droplist data type only stores the string value of the item that was chosen by the content editor, while Droplink stores the GUID of the item that was chosen by the content editor.

Sitecore Droplist and drop link field

So you may be wondering – so what?

This will cause a problem when you want to read the selected item's field value. If you use a drop list, you are not going to get the selected item and will get only the selected item's string value. But if you use a drop link, you can easily get the selected items and then can read any field value of that selected item.

Q28. What is the pipeline?

Ans: A lot of things happen when you request a page in Sitecore which is handled by pipelines. Pipelines define a sequence of processors that implement different functions such as handling page requests, uploading files, and saving items through the UI. If you have a series of tasks, which need to be performed to accomplish a task, then a pipeline may be the way to go.

Each processor in a pipeline contains a method named Process() that accepts a single argument and returns void. This method should return immediately if the processing context is not relevant to the processor. A processor can abort the pipeline, preventing Sitecore from invoking subsequent processors.

Sitecore separates the pipelines into two groups: those defined within the /configuration/Sitecore/pipelines and /configuration/Sitecore/processors elements in the web.config file. In general, those defined within the /configuration/Sitecore/processors define pipelines that operate for UI requests and can interact with the user. Those defined with the /configuration/Sitecore/pipelines tend to define system processes.

You May Also Read - Sitecore CMS Tutorial for Beginners

Q29. What is the processor?

Ans: Each step in the pipeline is called a ‘processor'. The sequence of processors within a pipeline is defined in the web.config file. Each Processor contains a unique operation and all these steps together create a pipeline. define system process such as initialize Sitecore application, load content editor warning. define UI process such as copy item, delete item, drag item, and so on.

define system process such as initialize Sitecore application, load content editor warning. define UI process such as copy item, delete item, drag item and so on.

Q30: Under which pipeline Sitecore context gets defined?

Ans: under configuration/sitecore/pipelines in web.config pipeline defines Sitecore context.

Q31. How many processors are there under the pipeline?

Ans: By default, there are 19 processors under pipeline but it may vary based on different modules you have installed in Sitecore. For example: If you have installed Sitecore DMS then you will find 21 processors under pipeline.

Q32. What is the command?

Ans: When you click any button within the Sitecore interface, the respective command gets called. Typically Sitecore commands are used to map actions to c# code. This mapping is defined in /App_Config/Commands.config file.

If you want to add your own commands you can edit the /App_Config/Commands.config file or set up a patch file in /App_Config/Include.

The Core database contains the command definition.

Q33. Which are the steps to add a new command in Sitecore?


  • Create a class that inherits from Sitecore.Shell.Framework.Commands.Command class
  • Add your command either at /App_Config/Commands.config file or setup a patch file in /App_Config/Include.
  • Add your command definition in the core database

Q34. Which options are provided by the Sitecore interface to move items from one instance to another instance?

Ans: Once you are ready with your Sitecore website, and you want to give it to QA people to test on their Sitecore instance () – how can you achieve this? In short, how to move your Sitecore items from the Development environment to the QA environment?

There are two options to achieve this requirement:

  • Package
Sitecore Package Designer
  • Serialization

If you are not seeing the “Developer” option in the menu bar, then configure it as shown in below screen capture.

Sitecore Developer

Q35. What is the difference between Package and Serialization?


  1. Sitecore Package:
  • There is a size limit of 2 GB for package creation in Sitecore, so you need to create multiple packages instead of creating one package if your deployment exceeds 2 GB size.
  • After installing the package, if you have changed a few items and now you want to revert these items back to the original version then there is no way to achieve it.
  • For example: If your package contains 50 new items, then you will have 50 new items in your Sitecore instance after installing this package. Now let's say you have changed 10 of these 50 items and you want to revert these 10 items back to the previous version (same version when you installed the package), then there is no such mechanism in package installation which will help you to revert these specific 10 items.

2. Sitecore Serialization:

  • There is no size limit of serialization items in Sitecore.
  • You have the option to revert your installation using revert options (e.g. revert tree, revert items) in serialization.
Sitecore Serialization
Sitecore Serialization

So it's better to use "Serialization" than "Package" - lesson I learnt.

Note: Always use a firefox browser while installing items from “package” or “serialization” because Internet Explorer gets a time-out issue while installing a big package.

Q36. Which are the options to move items from the master database to the web database?

Ans: By the time you are reading this question, you may be knowing that in the real-world there are two Sitecore environments.

  1. Staging Environment which points to master database
  2. Live/Production Environment which points to web database

In order to move Sitecore items from staging environment (master database) to live environment (web database), there are two options available in Sitecore:

  1. Publish (recommended) – you should always use the publish option if you want to move item(s) from a staging environment (master database) to a production environment (web database).
Sitecore Publish

2. Transfer (rarely used in specific scenarios) – you should refrain from the transfer option if you want to move item(s) from a staging environment (master database) to a production environment (web database).

Sitecore Transfer

Q37. What is the difference between Publish and Transfer?

Ans: Whenever any item is published in Sitecore, there are a couple of tasks getting executed in the background. One of these tasks is clearing cache. That means whenever any item is published, Sitecore clears the cache of that item so that you will not find any caching issue on the live website.

On the opposite side, there is no cache clear job performed while using the transfer option. That means when you transfer any item(s), it will simply move item(s) from the master database to the web database. So it's your responsibility to clear the cache manually by using the cache clear tool.

Now let's talk about circumstances in which you can use the transfer option. If you have published tons of items which will take hours of time to get complete and suddenly you come across a situation where you want to publish a single/few items (s) instantly. You cannot publish this item until the publishing queue completes the current running publishing items (tons of items).

Even if you publish that urgently required item, it will be queued and will be published last. In such a situation, you can take advantage of the transfer option to move instantly required items from the stage environment (master database) to the live environment (web database).

This will push your item to the live environment instantly although you need to clear the cache manually by using the cache clear tool. If you don't know what a cache clear tool is, then don't worry we will discuss Sitecore cache and cache clear tool in upcoming questions.

Q40. What is the scheduler? How can you define the scheduler in Sitecore?

Ans: As the name implies, the scheduler is a task that gets executed at some interval. There are three ways to schedule a process in Sitecore CMS.

Configure agent in the web.config. This is very straightforward and the most common way to create a scheduler in Sitecore. Using this approach will restart the ASP.NET worker process, as it requires changing the web.config file.

Create schedule tasks in the Sitecore database In this option, you can define a scheduler in Sitecore database under /sitecore/system/Tasks/Schedules. This option is user-friendly as you can configure the scheduling options from the CMS directly. This approach would not restart ASP.NET worker process as you don't require to change the web.config file.

Scheduler in Sitecore
Sitecore Scheduler

3) Create a Window Task Scheduler (window service) to call web service in Sitecore.

You May Also Read - How To Become A Sitecore CMS Developer?

Q41. What is the publishing target?

Ans: Where can you define publishing targets in Sitecore? In order to move items from the master database to the live (web) database, we use the publish option. If you have got a chance to observe the publishing window, you may have seen the publishing target section at the bottom of the window.

 Sitecore Publishing Target

So, where are these checkbox values coming from? They are coming from publishing target configuration.

 Sitecore Publishing Target Database

As per the above screens “Internet” publishing target is pointing to “web” databases. And the “web” database definition is configured in the web.config file.

Sitecore Web

You can configure more than one publishing target database as per your need. It is worth noting that the master database contains all versions items, while publishing the target database (e.g. web) contains only a single latest version of each language item. If you have multiple publishing targets, then you will see all of them in the publishing window as checkbox items. In case you want to set any of these publishing target databases as your default target database, then you can configure it via the DefaultPublishingTargets setting in the web.config file.

 Sitecore Publishing Target

Q42. What is the workflow? How can you check the current workflow status of an item?

Ans: Sitecore is famous for its flexible architecture. You can achieve many requirements without doing any code and by doing some configuration only. One of its eye-catching features is its workflow.

Workflow is a controllable way by which you can define a series of tasks to add, review and publish content. In every CMS there are broadly three types of users:

  1. Content Author/Editor – responsible for adding and updating content only. This type of user should not be allowed to publish the content.
  2. Content Reviewer – responsible for reviewing content that is submitted by the author. This type of user should not be allowed to publish the content.
  3. Content Publisher – responsible for publishing content approved by the reviewer.

In order to achieve the above series of tasks, you can take advantage of the Sitecore Workflow feature. You can find workflow at /sitecore/system/Workflows in the Sitecore content tree. The below figure shows an example of sample workflow.

Sitecore WorkFLow States

Draft State: The draft state is the initial state and it will be assigned to the item whenever the user creates or edits the content. Sitecore items cannot be published if it is in draft state.

Sitecore Submit

Awaiting Approval State: Once content editing is completed and the item is ready to review, the user can submit that item to the reviewer. This submission action will move the item from draft state to awaiting approval state. Sitecore items cannot be published if they are awaiting approval.

Approved State: This is the last state of the item. There are two types of actions can be executed under this state:

  1. Approve: this action will move Sitecore item to the final state and the item can be published now.
  2. Reject: this action will move Sitecore item to draft state again.
Sitecore Approve Reject

At any point of the item if you want to know the current state of the item, you can either check the workflow section fields of an item or by looking into the workbox.

Q43. Which are different tokens supported by Sitecore?

Ans: When you create an item, Sitecore replaces the token with the corresponding value of that item.

For example: if you have specified the $name token at “Title” field in standard value, then Sitecore will replace “Title” field with the item name that you provided while creating the item.

Here is the list of tokens supported by Sitecore:

  • $name: The name of the item
  • $id: The ID of the item
  • $parentid: The ID of the parent of the item
  • $parentname: The name of the parent of the item
  • $date: The system date (yyyyMMdd)
  • $time: The system time (HHmmss)
  • $now: The date and time (yyyyMMddTHHmmss)

Q44. How can you check if a particular item is referred to by which other items in Sitecore?

Ans: In your day to day Sitecore work you may come across a situation where you want to know how many items are referring to a particular item. For example, you are working on a template item and you want to know how many items are created using this template or how many items are using this template? Below screenshot will guide you on how to get referrers list.

Sitecore Service Area

If you want to check this for multiple items then it will be a time-consuming job to select every item and check links for all those items. For that, you can download the “Sitecore Informatics'' module from Sitecore Marketplace which will show you all your site templates and items created using those templates.

Q45. How can you add help text for a particular field in Sitecore?

Ans: Many times you want to provide some help text to users to understand the purpose of a particular field. You want to convey a message to the user what should be the value of that field. This can be accomplished by configuring help text for that field. Below screen-shots will help you to configure help text for any field.

Sitecore Journey
Sitecore Title

Q46. What is the display name? Why should one use it?

Ans: Whenever you create an item in Sitecore, you want to give a user-friendly name so that the content author can easily understand the purpose of that item. But do you know there are few restrictions in the item name, you cannot add special characters in the Sitecore item name.

For example – if you want to create an item “What we do?” Sitecore will not allow it as it contains a special character “?”


So how can you achieve it? The answer is – use the Display Name field. Once you create items by following item name criteria. You can then change the display field of that item by including characters which are not allowed while creating the item.

Sitecore What We Do

Display name (e.g. “Who we are?”) will be shown in CMS user interface such as content tree in place of item name (e.g. “Who we are”).

The advantages of using display name fields are:

  • The display name can include characters not allowed in item names.
  • Display names can vary by language while item names cannot.
    It is worth to note that Sitecore constructs the default URL of an item based on its name not based on the display name.

Q47. Which characters are not supported by default for item name in Sitecore?
By default, Sitecore allows alphanumeric, $ and – character in item name. You cannot use any other special characters in item names. In case if you want to allow some special character in item name, then you need to change ItemNameValidation setting value in web.config file.

Q48: How can you configure the log folder path of your Sitecore site?
Ans: Sitecore uses log4net API to log all the events and information. By default, Sitecore creates date wise logs in the log folder.

You will find this logs folder under the data folder variable path. data folder is the variable that defines exact path of your logs folder.

Q49. Where does Sitecore store all packages? How can you configure this package folder path?
Ans: As we have seen earlier, Sitecore stores all the packages under dataFolder variable path. . dataFolder is the variable that defines the exact path of your logs folder.

Q50. Which are different types of caching in Sitecore?
Ans: Sitecore provides a number of caching layers. Each cache serves as a key/value collection. These caching layers are:
1. HTML Cache: It caches actual HTML output generated from rendering and sublayout. It can be configured from the caching section of rendering controls.

Each website can be configured to enable or disable HTML cache along with allowed HTML cache size in web.config file under section.

2. Item Cache: Sitecore items are cached under this cache layer. This cache contains objects of the Sitecore class Sitecore.Data.Items.Item, which are the one you use in your code most of the time. Whenever any sitecore item is requested, it will be served from item cache and if it is not there then it will be served from data cache (next layer of cache) and will populate cache in item cache layer. So that whenever the next request for the same item is made, it will be directly served from the item cache.

3. Data Cache: Data cache contains items of the Sitecore class ItemInformation. Whenever any request is made, data is pulled from the data cache. But if it is not present there it will be pulled from prefetch cache and then will be put into data cache. So that whenever the next request for the same item is made, it will be directly served from the data cache. Data cache can be configured in web.config file under Caching.DefaultDataCacheSize setting:

4. Prefetch Cache: There is a prefetch cache for each database. The cache contains items of Sitecore class PrefetchData which is the same as data pulled from the database. Prefetch cache loads the cache at Sitecore start-up as per specified in App_Config/Prefetch folder. The below diagram illustrates how all these are actually working.

Q51: Where can you add a new site in Sitecore?
Ans: Creating a new site in Sitecore instance (e.g. http://local.sitecore7.com) involves three steps process:
Step-1: Configure your site hostname in Sitecore Instance.
There are two ways to add a new site in your Sitecore instance.
1. Add element under section in web.config file

2. Add element under section in SiteDefintion.config file

You will find SiteDefintion.config.example file at \Website\App_Config\Include\ folder. You should remove the .example extension in order to use it.

Now you may be wondering which one is a good option. Well, let me help you with this. It is good to add a new site in SiteDefinition.config file because it's always advisable not to touch the default web.config file and override your custom settings in config files situated under the App_Config folder provided by Sitecore. After adding a new site in the config file, there are two more steps that need to be performed outside of Sitecore to access the newly added site.
Step2: Add your site hostname in IIS binding.

Step3: Add your site hostname in hosts file (under WINDOWS\System32\drivers\etc\ folder)

After completing these three steps your newly added Sitecore website is ready to access.


These are the top 51 Sitecore Interview Questions that should be enough to get you started. You can refer to our course section for the list of professional courses.

Latest 51 Sitecore Interview Questions FAQs

Question. What is the salary of a Sitecore CMS developer?

The average annual salary of a Sitecore CMS developer in the US is $103777. On the contrary, the average annual salary of a Sitecore CMS developer in India is ₹7,80,000. This salary is subject to change and differs as per the geographical location you work in, your company, experience level, skill set, and much more.

Question. How do I start learning Sitecore?

If you wish to start learning Sitecore, then the first step should be to enroll in a trusted Sitecore training online program. igmGuru is a great option for the same as you get assurance of quality training by industry experts of 10+ years experience.

Question. What type of CMS is Sitecore?

Sitecore XM Cloud is a widely popular enterprise-ready SaaS CMS. It reimages how content management is done by using a hybrid architecture for delivering developer agility.

Question. What language does Sitecore use?

Even though Sitecore is written in C#, you do not have to necessarily learn this language for building a solution. It is an ASP.NET-oriented product and hence, any language that is supported by ASP.NET is also fine.

Drop Us a Query

Fields marked * are mandatory

Your Shopping Cart

Your shopping cart is empty.