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

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.

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

Get Premium Sitecore-XM-Cloud-Developer Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

35 comments · newest first

Aileen 11 months ago

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

Linn 11 months ago

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

Augustine 11 months ago

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

Craig 11 months ago

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

Valentine 12 months ago

A is correct, restrictions apply site-wide.

Olen 12 months ago

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

Nieves 1 year 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?

Tess 1 year ago

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

Hector 1 year 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.

Shannon 1 year 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.

Ashleigh 1 year 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.

Rasheeda 1 year 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.

Shoshana 1 year 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.

Herminia 1 year 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.

Lashawnda 2 years ago

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

Franklyn 2 years ago

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

Eloisa 2 years ago

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

Brynn 2 years ago

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

Ula 2 years ago

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

Desire 2 years ago

↳ replying to Ula

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

Rocco 2 years ago

↳ replying to Ula

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

Phuong 2 years ago

↳ replying to Ula

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

Justine 2 years ago

↳ replying to Ula

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

Cristy 2 years ago

↳ replying to Ula

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

Alex 2 years ago

↳ replying to Ula

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

Angella 2 years ago

↳ replying to Ula

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

Katie 2 years 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.

Gianna 2 years ago

I think C is the correct answer. The restrictions only apply to a specific page, not the entire site.

Nichelle 2 years ago

Option B seems logical since the placeholder settings are defined at the instance level.

Emmanuel 2 years ago

↳ replying to Nichelle

Exactly, it's important to understand where the restrictions are being applied.

Herminia 2 years ago

↳ replying to Nichelle

That makes sense, since the restrictions are set at the instance level.

Berry 2 years ago

↳ replying to Nichelle

Yes, the restrictions apply to every page of every site in the instance.

Marva 2 years ago

↳ replying to Nichelle

I think option B is correct.

Chau 2 years ago

I disagree, I believe the restrictions only apply for a placeholder called headless-footer on a designated page.

Paulene 2 years ago

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

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