A process document says table metadata changes are requested by emailing the data platform team, who apply them manually. What is the weakness of this approach?
Select an answer to reveal the explanation.
Short Explanation
Email is not a change control system. You end up with no history, no review, and no record of what was applied, while the platform already has a managed interface that records the change as it happens.
Full Explanation
The weakness is that routing metadata changes through email leaves no durable record of what changed, who authorised it, or when it took effect. Data manager exists to perform these operations within the platform, where they are visible and consistent with governance. The claim that email cannot represent schema definitions accurately enough to be applied is incorrect because email can carry a schema description perfectly well; expressiveness is not the defect. The claim that the platform rejects metadata changes that did not originate from an automated source is incorrect because the platform does not police the origin of a request; the administrator applying it looks like any other authorised user. The claim that it is a sound approach as long as the team responds within an agreed service level is incorrect because responsiveness does not address the absence of tracking and consistency; a prompt undocumented change is still undocumented. For the exam, treat “manage this by email” as a distractor pattern that appears whenever a purpose-built interface exists.