A customer warns to ado a field to the properties of all existing and new assets in AEM Assets to capture the asset rating. After the team uploads an asset the review team needs to go through the…

Question

Options

• ABuild a new schema with the rating property via the Metadata Schemas tool
• BCreate a new schema with the rating property via the Folder Metadata Schemas tool
• CGuild a new profile with the rating property for assets via the Metadata Profiles tool
• DCreate a new profile with the rating property via the image Profiles tool

• A
  3% (1)
• B
  3% (1)
• C
  82% (28)
• D
  12% (4)

Explanation

Option C is correct because Metadata Profiles in AEM Assets are designed to apply metadata fields to assets within folders - both retroactively to existing assets and automatically to newly uploaded ones. When a Metadata Profile containing the rating property is created and assigned to a folder, AEM processes all current assets and continues applying the field to future uploads, giving the review team a consistent property to fill in.

Why the distractors are wrong:

• A (Metadata Schemas) defines the form layout shown in the asset properties UI but doesn't push the field onto existing assets - it only changes what the form looks like when someone opens a property panel.
• B (Folder Metadata Schemas) applies metadata to folders themselves, not to the asset files contained within them.
• D (Image Profiles) controls image processing configurations such as renditions, crops, and sharpening - it has nothing to do with metadata fields.

Memory tip: Think of it this way - a Schema is a template (it shapes the form), while a Profile is a stamp (it actively applies properties to assets). The question requires stamping a rating field onto all assets, old and new, so you need a Profile, not a Schema.

No community discussion yet for this question.