Sitecore-Experience-Solution-9-Developer Sitecore Experience Solution 9 Developer Exam Questions and Answers

In the Experience Editor, the user will be able to add any component to the placeholder.

In the Experience Editor, the user will not be able to add any component to the place-holder.

By deserializing them. How they get serialized will depend on the tools you have at your disposal.

By serializing them. How they get serialized will depend on the tools you have at your disposal.

Allow editing content in a sandbox without affecting the content on the live site

To be able to have multiple servers delivering your live site content

To make version upgrades much easier

To separate your own configuration from the standard one that comes with Sitecore

By adding a Content Editor Button to a toolbar

By adding a Frame Button to a toolbar

By adding a Field Editor Button to a toolbar

none

web

master

core

All

Instead of returning a null field value, it will check if the same field in the Standard Value item has a value and then it ' ll return that value.

Error

403

500 Internal Error

web, core, master

core, master

web, core

master

There is no need to access Sitecore database to query its value

Update index operations will be faster

The tokenization process will be more efficient

The index will take less space

master db

Core db

web db

None

provide default field values

avoid duplicating a field name within the same template

limit Rich Text Editors

All the above

The Rendering field is shared between selected item versions and is not used for global changes; The Final Renderings field is shared and does not stores language and version-specific changes.

None

The Rendering field is shared between all item versions and is used for global changes; The Final Renderings field is not shared and stores language and version-specific changes.

Name

Template

Location (parent node)

All

add only what ' s required to the index

add multiple indexes

avoid index

All

Click on the template > Builder tab > Options > Standard templates

Click on the design > Builder tab > Options > Standard values

Click on the design > Builder tab > Options > Standard templates

Click on the template > Builder tab > Options > Standard values

default field values (enter 1 of the 3 main tokens)

default insert options

default workflow

All

Create a Placeholder Settings item for that placeholder.

Set Datsource location for that

Set Datasource template for that

None

Content Editor

Experience Editor

Control Panel

All

Vertical Scaling

Horizontal Scaling

Inclined Scaling

None

A code file on the file system and definition item in the content tree

A definition item on the file system and code file in the content tree

No Presentation details

None

the core db

the web db

the master db

None

Text fields (Single-Line, Multi-Line, Rich Text)

Date/datetime

Image, General Link

All

In App-Config/Conclude folder, where folders and files are loaded alphabetically

Through IIS Settings

In App-Config/Include folder, where folders and files are loaded alphabetically

Cant be controlled

Experience Management ( xManagement)

Experience Platform

Sitecore Platform

Experience Editor

Html.Sitecore().FormHandler()

Html.Sitecore().ValidateHandler()

Both

None

By the Path field on the definition item.

By the Path field on the code files

Both a and b

Only b

FieldRenderer.Render()

By default all fields are editable

FieldRenderer.Option()

None

presentation details

Edit Frame

Component

None

$name

$date

$now

All

ItemService

EntityService

Both

None

Your Presentation artifacts are more reusable

Your code artifacts are more reusable

Performance increases

Indexing gets easier

TDS

Unicron

Github

and Sitecore Rocks

Both a and b

Collection Database (MongoDB)

Reporting

Session State

All

Sitecore Rocks or Sitecore interfaces

Experience editor

content editor

All

host name

rootPath

startItem

All

The construct Sitecore uses to store data, is the basic building block

which has the presentation details always

helps us to store images

helps in indexing

data definitions

Component Definition

LAyout

Presentation

The Experience Editor provides editing and designing functionality(Also accept: marketing)

The Content Editor provides editing and designing functionality. (Also accept: marketing)

Both

None

field section

data fields

data template

navigator

Store any shared content outside of any site structure

Store any shared content inside of any site structure

Store anywhere

All of the above

Sitecore shows a Layout not found error page.

403 Error

500 Error

Helix

Habitat

Sitecore Guidelines

None

Where

Contains

Any, All, OrderBy

All