Practice Free Plat-Arch-201 Exam Online Questions
Low Value
Which strategy should a data architect recommend to configure customer type?
- A . Lookup to a custom object with defined choices.
- B . Single-select restricted picklist with defined choices.
- C . Provide help text to guide users with defined choices.
- D . Create a validation rule to limit entry to defined choices.
B
Explanation:
single-select restricted picklist with defined choices can be a way to configure customer type. The article states that picklists are fields that allow users to select one or more predefined values from a list, and restricted picklists ensure that users can only select from the defined values. This can help to limit the choices for customer type and ensure data quality.
UC is trying to switch from legacy CRM to salesforce and wants to keep legacy CRM and salesforce in place till all the functionality is deployed in salesforce. The want to keep data in synch b/w Salesforce, legacy CRM and SAP.
What is the recommendation.
- A . Integrate legacy CRM to salesforce and keep data in synch till new functionality is in place
- B . Do not integrate legacy CRM to Salesforce, but integrate salesforce to SAP
- C . Integrate SAP with Salesforce, SAP to legacy CRM but not legacy CRM to Salesforce
- D . Suggest MDM solution and link MDM to salesforce and SAP
C, D
Explanation:
Integrate SAP with Salesforce, SAP to legacy CRM but not legacy CRM to Salesforce. This is a good recommendation because it allows both Salesforce and the legacy CRM to interact with the ERP system, which can be the source of truth for some data entities. However, it avoids creating a direct connection between Salesforce and the legacy CRM, which can cause data duplication and synchronization issues. Suggest MDM solution and link MDM to salesforce and SAP. This is another good recommendation because it can help manage the data lifecycle and quality across multiple systems, as well as provide a single view of the customer data
UC is trying to switch from legacy CRM to salesforce and wants to keep legacy CRM and salesforce in place till all the functionality is deployed in salesforce. The want to keep data in synch b/w Salesforce, legacy CRM and SAP.
What is the recommendation.
- A . Integrate legacy CRM to salesforce and keep data in synch till new functionality is in place
- B . Do not integrate legacy CRM to Salesforce, but integrate salesforce to SAP
- C . Integrate SAP with Salesforce, SAP to legacy CRM but not legacy CRM to Salesforce
- D . Suggest MDM solution and link MDM to salesforce and SAP
C, D
Explanation:
Integrate SAP with Salesforce, SAP to legacy CRM but not legacy CRM to Salesforce. This is a good recommendation because it allows both Salesforce and the legacy CRM to interact with the ERP system, which can be the source of truth for some data entities. However, it avoids creating a direct connection between Salesforce and the legacy CRM, which can cause data duplication and synchronization issues. Suggest MDM solution and link MDM to salesforce and SAP. This is another good recommendation because it can help manage the data lifecycle and quality across multiple systems, as well as provide a single view of the customer data
Northern Trail outfitters in migrating to salesforce from a legacy CRM system that identifies the agent relationships in a look-up table.
What should the data architect do in order to migrate the data to Salesfoce?
- A . Create custom objects to store agent relationships.
- B . Migrate to Salesforce without a record owner.
- C . Assign record owner based on relationship.
- D . Migrate the data and assign to a non-person system user.
A
Explanation:
The correct answer is A. To migrate the data to Salesforce, the data architect should create custom objects to store agent relationships. This will allow the data architect to replicate the look-up table structure from the legacy CRM system and maintain the relationship data in Salesforce.
Option B is incorrect because migrating to Salesforce without a record owner will cause errors and prevent the data from being imported.
Option C is incorrect because assigning record owner based on relationship will not preserve the agent relationships from the legacy CRM system.
Option D is incorrect because migrating the data and assigning to a non-person system user will not allow the users to access and modify the data.
UC has a variety of systems across its technology landscape, including SF, legacy enterprise resource planning (ERP) applications and homegrown CRM tools. UC has decided that they would like to consolidate all customer, opportunity and order data into Salesforce as part of its master data management (MDM) strategy.
What are the 3 key steps that a data architect should take when merging data from multiple systems into Salesforce? Choose 3 answers
- A . Create new fields to store additional values from all the systems.
- B . Install a 3rd party AppExchange tool to handle the merger
- C . Analyze each system’s data model and perform gap analysis
- D . Utilize an ETL tool to merge, transform and de-duplicate data.
- E . Work with Stakeholders to define record and field survivorship rules
C, D, E
Explanation:
The three key steps that a data architect should take when merging data from multiple systems into Salesforce are:
Analyze each system’s data model and perform gap analysis. This step involves understanding the structure and meaning of the data in each system, identifying the common and unique data elements, and mapping the data fields between the systems. This step also involves assessing the quality and consistency of the data, and identifying any data cleansing or transformation needs.
Utilize an ETL tool to merge, transform, and de-duplicate data. This step involves using an ETL tool to connect to the source systems, extract the data, apply any data transformations or validations, and load the data into Salesforce. This step also involves applying de-duplication rules or algorithms to avoid creating duplicate records in Salesforce.
Work with stakeholders to define record and field survivorship rules. This step involves collaborating with the business users and owners of the data to determine which records and fields should be retained or overwritten in case of conflicts or discrepancies. This step also involves defining the criteria and logic for record and field survivorship, and implementing them in the ETL tool or in Salesforce.
Creating new fields to store additional values from all the systems is not a key step, but rather a possible outcome of the gap analysis. It may not be necessary or desirable to create new fields for every value from every system, as it may result in redundant or irrelevant data. Installing a 3rd party AppExchange tool to handle the merger is not a key step, but rather a possible option for choosing an ETL tool. It may not be the best option depending on the requirements, budget, and preferences of the organization.
(NTO) has multiple salesforce orgs based on geographical reports (AMER, EMEA, APAC). NTO products are in the AMER org and need to be created in the EMEA and APAC after the products are approved.
Which two features should a data architect recommend to share records between salesforce orgs? Choose 2.
- A . Change data capture (CDC)
- B . Salesforce connect.
- C . Federation search
- D . Salesforce 2 Salesforce
A, D
Explanation:
The two features that a data architect should recommend to share records between Salesforce orgs are:
Change Data Capture (CDC): This is a feature that publishes change events for changes in Salesforce records, such as create, update, delete, and undelete operations. Change events can be subscribed by external systems or other Salesforce orgs using various tools, such as Platform Events, Streaming API, or CometD. CDC can help keep data in sync between Salesforce orgs in near real time89.
Salesforce to Salesforce (S2S): This is a feature that allows sharing records and related data with other Salesforce orgs that you partner with. You can choose which records and fields to share, and which orgs to share with. You can also accept updates from the other orgs to keep the data consistent10.
Salesforce Connect is not a good feature to share records between Salesforce orgs because it is intended for integrating external data sources with Salesforce using external objects. Federation Search is not a good feature to share records between Salesforce orgs because it is intended for searching across multiple Salesforce orgs without sharing data.
A Salesforce customer has plenty of data storage. Sales Reps are complaining that searches are bringing back old records that aren’t relevant any longer. Sales Managers need the data for their historical reporting.
What strategy should a data architect use to ensure a better user experience for the Sales Reps?
- A . Create a Permission Set to hide old data from Sales Reps.
- B . Use Batch Apex to archive old data on a rolling nightly basis.
- C . Archive and purge old data from Salesforce on a monthly basis.
- D . Set data access to Private to hide old data from Sales Reps.
C
Explanation:
Archiving and purging old data from Salesforce on a monthly basis is a good strategy to improve the user experience for the Sales Reps, as it will reduce the clutter and improve the search performance. Creating a permission set or setting data access to private are not effective ways to hide old data from Sales Reps, as they will still consume data storage and affect search results. Using Batch Apex to archive old data on a rolling nightly basis is also not a good option, as it will consume API requests and processing time, and may not comply with the data retention policy.
Universal Containers has a legacy system that captures Conferences and Venues. These Conferences can occur at any Venue. They create hundreds of thousands of Conferences per year. Historically, they have only used 20 Venues.
Which two things should the data architect consider when denormalizing this data model into a single Conference object with a Venue picklist? Choose 2 answers
- A . Limitations on master -detail relationships.
- B . Org data storage limitations.
- C . Bulk API limitations on picklist fields.
- D . Standard list view in -line editing.
C, D
Explanation:
When denormalizing a data model into a single object with a picklist field, the data architect should consider the Bulk API limitations on picklist fields and the standard list view in-line editing. The Bulk API has a limit of 1,000 distinct picklist values per file1, which could be an issue if there are more than 1,000 venues in the future. The standard list view in-line editing allows users to edit multiple records at once, which could introduce data quality issues if the venue picklist is not validated or restricted2. The other options are not relevant to denormalizing a data model.
Developers at Universal Containers need to build a report for the business which displays Accounts opened in the past year grouped by industry. This report will also include information from contacts, opportunities, and orders. There are several million Accounts in the system.
Which two options should be recommended to make this report perform well and satisfy the business need?
- A . Use triggers to populate denormalized related fields on the Account.
- B . Use an indexed data field with bounded data filters.
- C . Use Formula fields to surface information I related entities on the report.
- D . Use unbounded date ranges to filter the report.
B, C
Explanation:
Using an indexed data field with bounded data filters can improve the report performance by making the query more selective and reducing the number of records to scan. Using formula fields to surface information from related entities on the report can also enhance the report performance by avoiding joins and complex calculations
UC is preparing to implement sales cloud and would like to its users to have read only access to an
account record if they have access to its child opportunity record.
How would a data architect implement this sharing requirement between objects?
- A . Create a criteria-based sharing rule.
- B . Implicit sharing will automatically handle with standard functionality.
- C . Add appropriate users to the account team.
- D . Create an owner-based sharing rule.
B
Explanation:
Implicit sharing will automatically handle this sharing requirement with standard functionality, as it grants read-only access to parent accounts when users have access to child opportunities. This is also known as account-opportunity sharing3. Creating a criteria-based sharing rule (option A) or an owner-based sharing rule (option D) is not necessary, as they are used to grant additional access based on record criteria or ownership. Adding appropriate users to the account team (option C) is also not required, as it is used to grant access to specific users or groups for individual accounts.