New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Certified Platform Data Architect (Plat-Arch-201) Exam - Topic 6 Question 61 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Data Architect (Plat-Arch-201) exam
Question #: 61
Topic #: 6
[All Salesforce Certified Platform Data Architect (Plat-Arch-201) Questions]

Get Cloud Consulting needs to integrate two different systems with customer records into the Salesforce Account object. So that no duplicate records are created in Salesforce, Master Data Management will be used.

An Architect needs to determine which system is the system of record on a field level.

What should the Architect do to achieve this goal?

Show Suggested Answer Hide Answer
Suggested Answer: B

Key stakeholders from both systems should collaborate with the Architect to determine which system is the system of record on a field level is what the Architect should do to achieve this goal of integrating two different systems with customer records into the Salesforce Account object using Master Data Management. The system of record is the authoritative source of truth for a given entity or field in a given context. Different systems may have different levels of accuracy, completeness, timeliness, or relevance for different fields. Therefore, it is important to involve key stakeholders from both systems who have knowledge and expertise about their data quality and business needs to decide which system should be the system of record for each field. The Architect should facilitate this collaboration and document the decisions and rationale for each field. The other options are not correct or feasible, as they would either delegate or abdicate the responsibility of determining the system of record, ignore or disregard the input from key stakeholders, or assume or impose a default system of record without considering the data quality and business needs.


by Corinne at Jun 14, 2025, 02:00 AM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified Platform Data Architect (Plat-Arch-201) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Glen
2 months ago
Wait, D suggests no system of record? That sounds risky!
upvoted 0 times
...
Eva
3 months ago
I disagree with A. The Architect needs to know the data sources.
upvoted 0 times
...
Alpha
3 months ago
Definitely B. Collaboration is crucial for data integrity.
upvoted 0 times
...
Loren
3 months ago
C is interesting, but what if fields have different meanings?
upvoted 0 times
...
Twila
3 months ago
B makes the most sense. Stakeholder input is key!
upvoted 0 times
...
Floyd
3 months ago
I vaguely recall that input fields can be tricky, but I'm not sure if they can never have a system of record. That seems a bit extreme.
upvoted 0 times
...
Latrice
4 months ago
I feel like reviewing the database schema is crucial, but I'm not convinced that different field names always mean they should be separate in Salesforce.
upvoted 0 times
...
Josephine
4 months ago
I think option B makes sense because involving stakeholders could help clarify how fields are used across systems. We practiced something similar in our last session.
upvoted 0 times
...
Andra
4 months ago
I remember we discussed the importance of identifying the system of record, but I'm not sure if it's just about the Master Data Management system deciding that.
upvoted 0 times
...
Ezekiel
4 months ago
I feel pretty confident about this one. The key is that Master Data Management will handle the deduplication, so the Architect doesn't have to worry about that. They just need to focus on identifying the system of record for each field.
upvoted 0 times
...
Golda
4 months ago
Okay, I've got a strategy for this. I'll start by reviewing the database schemas for the external systems to understand how the fields are named and structured. Then I can work with the key stakeholders to map out which system should be the system of record for each field.
upvoted 0 times
...
Junita
5 months ago
Hmm, I'm a bit confused on this one. The question mentions Master Data Management, but it's not clear how that plays into determining the system of record. I'll need to think through the different options carefully.
upvoted 0 times
...
Chu
5 months ago
This question seems straightforward - we need to determine the system of record for each field that will be integrated into Salesforce. I think reviewing the key stakeholders' input on how the fields will be used is the way to go.
upvoted 0 times
...
Emiko
8 months ago
A) sounds a bit too hands-off for me. I'd want the Architect to have a clear understanding of where the data is coming from.
upvoted 0 times
Heidy
7 months ago
A) sounds a bit too hands-off for me. I'd want the Architect to have a clear understanding of where the data is coming from.
upvoted 0 times
...
Bettyann
7 months ago
C) The database schema for each external system should be reviewed, and fields with different names should always be separate fields in Salesforce.
upvoted 0 times
...
Johnna
7 months ago
B) Key stakeholders should review any fields that share the same purpose between systems to see how they will be used in Salesforce.
upvoted 0 times
...
...
Domonique
8 months ago
I believe key stakeholders should also review fields that share the same purpose between systems to avoid any confusion.
upvoted 0 times
...
Charlena
8 months ago
Haha, D) is just asking for trouble. Overwriting data based on the last record integrated? No way, that's a recipe for disaster!
upvoted 0 times
Victor
7 months ago
User 2: Definitely! We need a better solution to avoid data overwriting.
upvoted 0 times
...
Trevor
8 months ago
User 1: I agree, D) sounds like a disaster waiting to happen.
upvoted 0 times
...
...
Novella
8 months ago
I agree with Cathrine. It's important to ensure that fields with different names are separate in Salesforce.
upvoted 0 times
...
Cathrine
8 months ago
I think the Architect should review the database schema for each external system.
upvoted 0 times
...
Leatha
8 months ago
C) makes sense to me. Reviewing the database schema and ensuring separate fields for different data sources is a good way to avoid issues.
upvoted 0 times
...
Audra
8 months ago
B) seems like the most logical approach. Getting key stakeholders involved to review the fields and determine the system of record is crucial.
upvoted 0 times
Micheline
8 months ago
A) Master Data Management systems determine system of record, and the Architect doesn't have to think about what data is controlled by what system.
upvoted 0 times
...
Dolores
8 months ago
B) That makes sense. It's important to ensure that the data is properly mapped and integrated without creating duplicates.
upvoted 0 times
...
Lucy
8 months ago
C) The database schema for each external system should be reviewed, and fields with different names should always be separate fields in Salesforce.
upvoted 0 times
...
Madelyn
8 months ago
B) Key stakeholders should review any fields that share the same purpose between systems to see how they will be used in Salesforce.
upvoted 0 times
...
...

Save Cancel