SF-Data-Arch Data Modeling and Database Design Practice Question
An organization wants to use 'Person Accounts' to manage B2C relationships. Which consideration is most important for a Data Architect when evaluating this change?
⚠ Common exam trap
Candidates often treat Person Accounts as a minor configuration change, failing to realize the massive, permanent impact on the data model and existing integrations.
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
✓
They fundamentally change the object model and are non-reversible.
Person Accounts merge the Account and Contact models into a single entity, which has long-term implications for the data schema. Once enabled, this change cannot be reversed, and it impacts existing integrations, custom code, and reporting. A Data Architect must ensure that all third-party systems are updated to handle the new object structure, as the standard Account-Contact hierarchy is fundamentally altered, potentially breaking legacy processes that expect distinct objects.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Person Accounts can be disabled by contacting Salesforce Support.
Why it's wrong here
Person Accounts are a permanent change to the organization's data model. Once enabled, they cannot be deactivated or removed. This makes the initial decision to implement them extremely critical, as it requires extensive testing and planning to avoid long-term structural issues with the database and integrations.
- ✗
They replace the need for custom objects for B2C data.
Why it's wrong here
While Person Accounts simplify the Account-Contact model, they do not necessarily replace all custom objects. If the business has unique requirements that go beyond simple B2C contact information, custom objects may still be required. The decision should be based on architectural fit, not just object reduction.
- ✓
They fundamentally change the object model and are non-reversible.
Why this is correct
Person Accounts merge the Account and Contact entities. This is a irreversible change that affects almost every part of the system, including API integrations and reporting. A data architect must perform a thorough impact analysis because this change is permanent and alters the core structure of the database.
- ✗
They require a Business Account for every Person Account.
Why it's wrong here
Person Accounts are a distinct record type and do not require the existence of traditional Business Accounts. They operate as their own entity within the Account object, meaning you can have a system consisting entirely of Person Accounts if that fits the specific business use case.
About these practice questions
Courseiva writes every SF-Data-Arch question from scratch — 222 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.