SF-Data-Arch Data Governance Practice Question
A retail company wants to ensure that customer email addresses are consistently formatted and that invalid values are rejected at the point of entry across web, mobile, and integration channels. The data governance lead asks the architect which Salesforce feature provides a single, reusable definition of the validation that all channels can share. Which feature should the architect recommend?
⚠ Common exam trap
Many exam-takers confuse detection or duplication controls with prevention, when the requirement is a shared validation definition that rejects invalid values at entry.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
A validation rule on the Contact object using a REGEX function to enforce a standard email pattern.
Validation rules are evaluated on every insert and update no matter which channel performs the write, so a REGEX-based rule gives one reusable definition of the email format standard. It prevents invalid values from being saved, which is what the governance policy requires. Formula fields, duplicate rules, and notification flows either do not validate or act only after the fact.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
A validation rule on the Contact object using a REGEX function to enforce a standard email pattern.
Why this is correct
Validation rules evaluate on insert and update regardless of channel, so the same REGEX-based rule applies to web, mobile, and integration writes. It provides one reusable definition of the format requirement and blocks invalid values at the point of entry. This directly satisfies the governance lead's request for consistency across all channels.
- ✗
A duplicate rule that matches contacts with similar email addresses.
Why it's wrong here
Duplicate rules identify and manage duplicate records; they do not validate the format of a single field. A contact with a malformed email address would not necessarily match an existing record, so the rule would not reject it. This addresses duplication, not data quality of the email value itself.
- ✗
A formula field that concatenates the email domain with a fixed suffix.
Why it's wrong here
A formula field computes a derived value; it does not validate input or reject invalid data. It would also produce incorrect addresses by appending a suffix rather than checking format. The requirement is for a shared validation definition that blocks bad values at entry, which a formula field does not provide.
- ✗
A record-triggered flow that sends a notification to the data steward when the email is malformed.
Why it's wrong here
A flow that notifies a steward is a detective, after-the-fact control. It allows the malformed email to be saved and relies on human follow-up, so it does not reject invalid values at entry. The requirement calls for prevention with a shared definition, which a notification flow does not deliver.
About these practice questions
One of 222 original SF-Data-Arch practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Salesforce exam blueprint
This SF-Data-Arch practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-Data-Arch exam.