Q: 7
A client wants to ensure that only specific components are available to content authors when using
an editable template in AEM. Additionally, they require that certain fields within a content fragment
model adhere to strict validation rules for data integrity.
Which two steps would the developer take to meet both requirements? (Choose two.)
Options
Discussion
B/E? A is tempting but field validation isn't actually in editable templates. B and E fit what the question asks.
Nice catch on B and E. You need policies in the editable template to restrict which components show up (that's E), and content fragment models have their own validation configs (that's B). The others don't really fit those needs. Pretty sure that's how it's done, but open if someone has a different approach.
I thought A, editable templates seem like they should cover field validation directly too. Trap answer maybe?
C
Makes sense to pick B and E here. Templates control allowed components (E), and field validation is handled in the content fragment model (B). Not 100% but that's how I read it, open to other takes.
B and E imo. Editable template policies (E) let you lock down which components show for authors, and for validation, that has to be set in the content fragment model itself (B), not the template. Other options don't actually enforce those requirements. Pretty sure that's right, correct me if I've missed something.
I'm not sure about B for validations. Wouldn't A handle field validation rules directly in the editable template? I might be missing something with content fragment models though. Can someone clarify?
B and E make the most sense. From what I remember, field validation has to be set up directly in the content fragment model (so B). For limiting components on editable templates, you define policies (E). Saw a similar question in an exam report. Not 100% sure if workflow (C) could help, but pretty sure it's not the main way. Agree?
B and E tbh. Only policies on editable templates (E) limit components for authors, while field validation needs to be set in the fragment model itself (B). Trap here is thinking editable templates can handle validation-can't. Seen this come up before, but let me know if I missed something.
For the part about field validation in content fragment models, why not A? Doesn't editable templates touch validation at all?
Be respectful. No spam.
