A developer created a custom metadata profile and assigned default values to some fields. The developer applied this cus

[answerhappygod]

A developer created a custom metadata profile and assigned default values to some fields. The developer applied this custom profile to a folder in the DAM that already uses a different metadata profile. When viewing the metadata properties of the existing assets in a subfolder, the developer noticed that the custom metadata profile was not applied to these assets.
What is the cause of this issue?

A. The contents are cached and clearing the browser cache should resolve this issue.
B. The new metadata profile will only be applied to new assets that will be added to the folder later.
C. The custom metadata profile has some invalid field values and is preventing it from being applied to a folder.
D. The new metadata profile will only be applied to assets that are direct children of the folder.