Sitecore-XM-Cloud-Developer Exam - Topic 6 Question 31 Discussion

Actual exam question for Sitecore's Sitecore-XM-Cloud-Developer exam

Question #: 31
Topic #: 6

[All Sitecore-XM-Cloud-Developer Questions]

A developer is using the Content Editor to set placeholder restrictions on a placeholder called headless-footer. Because these restrictions have been set on the placeholder settings within /sitecore/Layout/Placeholder Settings, which of the following statements is correct?

AThe restrictions apply for all placeholders called headless-footer within a single site in the XM Cloud Content Management instance.

BThe restrictions apply for all placeholders called headless-footer on every page of every site that is in the XM Cloud Content Management instance.

CThe restrictions only apply for a placeholder called headless-footer on a designated page.

DThe restrictions only apply for subsequently created versions of a placeholder called headless-footer.

Show Suggested Answer

Suggested Answer: B

According to the Sitecore XM Cloud Documentation for Developers1, in the Content Editor, you can set placeholder restrictions for your layout placeholders. These restrictions are applied on all pages in the site. For example, if you add restrictions for a footer, these apply for all footers on every page of the site. In this way, you can control the content that content authors can place in layout placeholders. To add a placeholder setting for a site, you need to create a placeholder item in the Layout/Placeholder Settings folder and enter the placeholder key and the allowed components2.

The other options are not correct:

A) The restrictions apply for all placeholders called headless-footer within a single site in the XM Cloud Content Management instance. This option is too narrow, as the placeholder restrictions apply to all sites that use the same placeholder key, not just one site.

C) The restrictions only apply for a placeholder called headless-footer on a designated page. This option is too specific, as the placeholder restrictions apply to all pages that use the same placeholder key, not just one page. However, you can create placeholder restrictions on specific pages in the Experience Editor, if you want to override the default settings3.

D) The restrictions only apply for subsequently created versions of a placeholder called headless-footer. This option is incorrect, as the placeholder restrictions apply to all versions of the placeholder, not just the new ones.

2: Set placeholder restrictions | Sitecore Documentation 3: Set placeholder restrictions | Sitecore Documentation 1: XM Cloud Documentation for Developers - Sitecore

by Fletcher at Feb 12, 2025, 09:49 PM

Limited Time Offer

25%

Off

Get Premium Sitecore-XM-Cloud-Developer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Aileen

3 months ago

Wait, are you sure about A? That sounds too broad!

upvoted 0 times

...

Linn

3 months ago

D seems a bit off, why would it only apply to new versions?

upvoted 0 times

...

Augustine

4 months ago

Nah, it’s definitely C, only for that specific page.

upvoted 0 times

...

Craig

4 months ago

I think B is the right choice, it should cover all pages.

upvoted 0 times

...

Valentine

4 months ago

A is correct, restrictions apply site-wide.

upvoted 0 times

...

Olen

4 months ago

I feel like option B makes sense since it mentions every page, but I wonder if there are exceptions for designated pages.

upvoted 0 times

...

Nieves

5 months ago

I'm a bit confused about how restrictions work across different pages. Does anyone know if they only apply to specific pages or all pages?

upvoted 0 times

...

Tess

5 months ago

I remember a similar question about placeholder settings, and I think it was about site-wide restrictions. Could it be option A?

upvoted 0 times

...

Hector

5 months ago

I think the restrictions might apply to all instances of the placeholder within the site, but I'm not entirely sure if it includes all pages.

upvoted 0 times

...

Shannon

5 months ago

I'm not 100% confident, but I'm going to go with B. The global nature of the Placeholder Settings seems to indicate the restrictions would apply across all sites and pages in the XM Cloud instance.

upvoted 0 times

...

Ashleigh

5 months ago

I'm leaning towards B as well. The wording about the restrictions being set in the Placeholder Settings makes me believe they have a broad, instance-wide application.

upvoted 0 times

...

Rasheeda

5 months ago

Okay, let me walk through this step-by-step. The question says the restrictions are set in the Placeholder Settings, which means they should apply across the entire instance, not just a single site or page. So I think the correct answer is B.

upvoted 0 times

...

Shoshana

5 months ago

Hmm, I'm a bit confused on this one. I'll need to think it through carefully to make sure I understand the scope of the placeholder restrictions.

upvoted 0 times

...

Herminia

5 months ago

I'm pretty sure the answer is B. The placeholder restrictions set in the Placeholder Settings apply globally across the entire XM Cloud instance.

upvoted 0 times

...

Lashawnda

12 months ago

B all the way! Placeholder Settings is like the Borg - resistance is futile.

upvoted 0 times

...

Franklyn

12 months ago

Option D is the way to go. Gotta keep those legacy placeholders free and clear, am I right?

upvoted 0 times

...

Eloisa

12 months ago

I'm going with C. No way the restrictions would affect every single page in the entire instance. That's just crazy.

upvoted 0 times

...

Brynn

12 months ago

B has to be the right answer. Why else would they call it 'Placeholder Settings' if it didn't apply globally?

upvoted 0 times

...

Ula

12 months ago

D sounds plausible. The restrictions should only affect new versions of the placeholder, not existing ones.

upvoted 0 times

Desire

11 months ago

True, it depends on the specific requirements for the project.

upvoted 0 times

...

Rocco

11 months ago

In that case, we should go with B. It would be more global.

upvoted 0 times

...

Phuong

11 months ago

But what if we want the restrictions to apply to all placeholders with that name on every page?

upvoted 0 times

...

Justine

11 months ago

I think D is correct. It should only apply to new versions of the placeholder.

upvoted 0 times

...

Cristy

11 months ago

That makes sense. It's important to understand how the restrictions work in the Content Editor.

upvoted 0 times

...

Alex

11 months ago

I agree, the restrictions should only affect placeholders created after the settings were applied.

upvoted 0 times

...

Angella

11 months ago

I think D is the correct option. It only applies to new versions of the placeholder.

upvoted 0 times

...

Katie

1 year ago

I think the restrictions apply for all placeholders called headless-footer on every page of every site that is in the XM Cloud Content Management instance.

upvoted 0 times

...