After going live with an Adobe Real-Time CDP implementation, a data architect notices that a field defined in field group A should actually be part of field group B. How can this issue be resolved?

Question

Options

• ARemove the field from field group A and create it inside of field group B after creating all datasets
• BUse the move schema endpoint in the schema registry API after deleting all datasets linked to the
• CRemove the field from field group A and create it inside of field group B after deleting all datasets
• DUse the schema editor in the AEP UI to directly move the field to the new field group

• A
  12% (7)
• B
  7% (4)
• C
  78% (45)
• D
  3% (2)

Explanation

Option C is correct because Adobe Experience Platform enforces schema immutability once datasets are linked - you cannot modify field group structure while datasets exist that reference those schemas. The required process is: delete all associated datasets first, then remove the field from field group A, and recreate it in field group B, after which datasets can be rebuilt.

Why the distractors fail:

• A is wrong because it says "after creating all datasets" - you must delete datasets before restructuring field groups, not after creating them. The order is inverted.
• B is wrong because no "move schema endpoint" exists in the Schema Registry API. This is a fabricated capability designed to tempt candidates who expect a shortcut.
• D is wrong because the AEP Schema Editor UI has no "move field" drag-and-drop or direct transfer feature between field groups - this functionality simply does not exist in the interface.

Memory tip: Think of it as "demolish before you rebuild" - AEP won't let you renovate a room while furniture (datasets) is still inside. Delete the datasets, restructure the schema, then repopulate.

No community discussion yet for this question.