SF-Data-Arch Data Governance Practice Question
A Salesforce org has a data governance policy that requires all new custom objects and fields to be reviewed and approved by a data governance council before creation. A developer needs to add a new field to the Account object to support a critical business process. What should the developer do first?
⚠ Common exam trap
The trap here is focusing on the technical steps of field creation and overlooking the mandatory governance approval process that must occur first.
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
✓
Submit a request to the data governance council for review and approval, providing business justification and impact analysis.
The governance policy clearly states that new custom objects and fields must be reviewed and approved before creation. The developer should first submit a request to the data governance council with business justification and impact analysis. This ensures the council can evaluate the request against data standards and avoid unnecessary or redundant fields. Only after approval should the field be created.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Ask the Salesforce administrator to create the field as a temporary workaround and document it in a technical debt log.
Why it's wrong here
Creating a temporary field as a workaround still bypasses the required governance review. Documenting it as technical debt does not satisfy the policy, which mandates approval before creation. This approach could lead to proliferation of unapproved fields and complicate future data governance efforts.
- ✗
Use the Salesforce Setup menu to create the field directly in production, then notify the governance council afterward.
Why it's wrong here
Creating the field directly in production without prior approval directly violates the governance policy. Notifying the council afterward is too late; the policy requires pre-approval. This approach also bypasses change management best practices and could introduce unvetted changes that impact data quality and integrations.
- ✗
Create the field in a sandbox and then submit a change set for deployment to production.
Why it's wrong here
Creating the field in a sandbox before approval violates the governance policy. The policy requires review and approval before creation, not after. Even if the field is later approved, the developer has already bypassed the governance process. This approach could lead to unauthorized changes and undermine the council's authority.
- ✓
Submit a request to the data governance council for review and approval, providing business justification and impact analysis.
Why this is correct
The governance policy explicitly requires review and approval by the data governance council before creating new custom objects or fields. Submitting a request with justification and impact analysis is the correct first step. It ensures the council can assess the need, check for redundancy, and maintain data standards. Only after approval should the developer proceed with creation.
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.