AD0-E605 · Question #98
A data architect is working for a global marketing agency that utilizes Adobe Experience Platform to manage and analyze client data. The architect's team is responsible for designing schemas that…
The correct answer is B. Renaming an existing field in the schema D. Removing a previously defined field from the schema. Renaming a field (B) and removing a field (D) are breaking changes because they invalidate previously ingested data - existing records reference the old field name or rely on the field's presence, so renaming breaks field-level mapping and removing destroys data integrity for…
Question
A data architect is working for a global marketing agency that utilizes Adobe Experience Platform to manage and analyze client data. The architect's team is responsible for designing schemas that define the structure and format of various data sets. One day, a client requests changes to an existing schema to accommodate new data points they want to capture for their customer profiles. The architect needs to ensure that the schema evolution principles are followed while making the necessary updates. Which two changes to a schema are considered breaking changes when data is already loaded within Adobe Experience Platform? (Choose two.)
Options
- AAdding new fields to the schema to capture additional data
- BRenaming an existing field in the schema
- CEnabling the schema to participate in Profile
- DRemoving a previously defined field from the schema
How the community answered
(67 responses)- A6% (4)
- B78% (52)
- C16% (11)
Explanation
Renaming a field (B) and removing a field (D) are breaking changes because they invalidate previously ingested data - existing records reference the old field name or rely on the field's presence, so renaming breaks field-level mapping and removing destroys data integrity for all records already loaded into AEP.
Adding new fields (A) is non-breaking because it is purely additive; existing data simply lacks values for the new field, which is acceptable - AEP schemas are designed to handle this gracefully through forward compatibility. Enabling Profile participation (C) is also non-breaking - it changes how data is used (unified profile stitching) but does not alter the structure or field definitions that existing data depends on.
Memory tip: Think "CRUD minus the C" - you can Create (add) new fields safely, but Update (rename) or Delete (remove) fields will break things once data is loaded. If it touches an existing field's identity or existence, it's breaking.
Topics
Community Discussion
No community discussion yet for this question.