Practice Free Plat-Arch-201 Exam Online Questions
Universal Containers (UC) loads bulk leads and campaigns from third-party lead aggregators on a weekly and monthly basis. The expected lead record volume is 500K records per week, and the expected campaign records volume is 10K campaigns per week. After the upload, Lead records are shared with various sales agents via sharing rules and added as Campaign members via Apex triggers on Lead creation. UC agents work on leads for 6 months, but want to keep the records in the system for at least 1 year for reference. Compliance requires them to be stored for a minimum of 3 years. After that, data can be deleted.
What statement is true with respect to a data archiving strategy for UC?
- A . UC can store long-term lead records in custom storage objects to avoid counting against storage limits.
- B . UC can leverage the Salesforce Data Backup and Recovery feature for data archival needs.
- C . UC can leverage recycle bin capability, which guarantees record storage for 15 days after deletion.
- D . UC can leverage a “tier”-based approach to classify the record storage need.
D
Explanation:
Leveraging a “tier”-based approach to classify the record storage need is a true statement with respect to a data archiving strategy for UC. This approach involves defining different tiers of data based on their usage, value, and retention policies, and then applying appropriate storage and archiving solutions for each tier.
Prospects are maintained as Leads.
NTO needs to implement a standard communication preference management model for Person Accounts, Contacts, Users, and Leads.
Which option should the data architect recommend NTO to satisfy this requirement?
- A . Create custom fields for contact preferences in Lead, Person Account, and Users objects.
- B . Create case for contact preferences, and use this to validate the preferences for Lead, Person Accounts, and Users.
- C . Create a custom object to maintain preferences and build relationships to Lead, Person Account, and Users.
- D . Use Individual objects to maintain the preferences with relationships to Lead, Person Account, and Users.
D
Explanation:
The Individual object is a standard object that lets you store details about data privacy and protection preferences for person accounts, contacts, users, and leads. The Individual object can be used to implement a standard communication preference management model for NTO, with relationships to the other objects.
Universal Containers (UC) is a business that works directly with individual consumers (B2C). They are moving from a current home-grown CRM system to Salesforce. UC has about one million consumer records.
What should the architect recommend for optimal use of Salesforce functionality and also to avoid data loading issues?
- A . Create a Custom Object Individual Consumer c to load all individual consumers.
- B . Load all individual consumers as Account records and avoid using the Contact object.
- C . Load one Account record and one Contact record for each individual consumer.
- D . Create one Account and load individual consumers as Contacts linked to that one Account.
D
Explanation:
According to the exam guide, one of the objectives is to "describe best practices for implementing a single-org strategy in a B2C scenario"1. This implies that option D is the best practice for loading individual consumers as contacts in Salesforce. This approach avoids creating unnecessary accounts and reduces data duplication.
Option C is not correct because it creates one account per contact, which increases data volume and complexity.
Options A and B are not correct because they do not leverage the standard contact object, which provides native functionality and integration with other Salesforce features.
Universal Container (UC) has around 200,000 Customers (stored in Account object). They get 1 or 2 Orders every month from each Customer. Orders are stored in a custom object called "Order c"; this has about 50 fields. UC is expecting a growth of 10% year -over -year.
What are two considerations an architect should consider to improve the performance of SOQL queries that retrieve data from the Order _c object? Choose 2 answers
- A . Use SOQL queries without WHERE conditions.
- B . Work with Salesforce Support to enable Skinny Tables.
- C . Reduce the number of triggers on Order _c object.
- D . Make the queries more selective using indexed fields.
B, D
Explanation:
To improve the performance of SOQL queries that retrieve data from the Order_c object, the data architect should work with Salesforce Support to enable Skinny Tables and make the queries more selective using indexed fields. Skinny Tables are custom tables that contain frequently used fields and are kept in sync with the base tables3. They can improve performance by reducing the number of table joins and using indexes. Making the queries more selective using indexed fields can also improve performance by reducing the query execution time and avoiding query timeouts4. The other options are not effective or recommended for improving SOQL performance.
Universal Containers (UC) has three systems: Salesforce, a cloud -based ERP system, and an on – premise Order Management System (OMS). An architect has been tasked with creating a solution that uses Salesforce as the system of record for Leads and the OMS as the system of record for Account and Contacts. UC wants Accounts and Contacts to be able to maintain their names in each system (i.e., "John Doe" in the OMS and "Johnny Doe" in Salesforce), but wants to have a consolidated data store which links referenced records across the systems.
What approach should an architect suggest so the requirements are met?
- A . Have Salesforce poll the OMS nightly and bring in the desired Accounts and Contacts.
- B . Implement an integration tool to send OMS Accounts and Contacts to Salesforce.
- C . Implement a Master Data Management strategy to reconcile Leads, Accounts, and Contacts.
- D . Use the Streaming API to send Account and Contact data from Salesforce to the OMS.
C
Explanation:
Implementing a Master Data Management strategy to reconcile Leads, Accounts, and Contacts is the approach that the architect should suggest so that the requirements are met for UC. A Master Data Management strategy can provide a consistent and unified view of data across multiple systems, by defining and enforcing rules for data quality, governance, and integration. A Master Data Management strategy can also handle complex scenarios where different systems have different systems of record for different entities or fields, and where data can be modified in different systems with different values. A Master Data Management strategy can also provide a consolidated data store that links referenced records across systems and enables cross-system reporting and analysis. The other options are not suitable or sufficient for meeting the requirements, as they would either not provide a consolidated data store, not handle different systems of record, or not allow data modification in different system
Universal Containers (UC) has three systems: Salesforce, a cloud -based ERP system, and an on – premise Order Management System (OMS). An architect has been tasked with creating a solution that uses Salesforce as the system of record for Leads and the OMS as the system of record for Account and Contacts. UC wants Accounts and Contacts to be able to maintain their names in each system (i.e., "John Doe" in the OMS and "Johnny Doe" in Salesforce), but wants to have a consolidated data store which links referenced records across the systems.
What approach should an architect suggest so the requirements are met?
- A . Have Salesforce poll the OMS nightly and bring in the desired Accounts and Contacts.
- B . Implement an integration tool to send OMS Accounts and Contacts to Salesforce.
- C . Implement a Master Data Management strategy to reconcile Leads, Accounts, and Contacts.
- D . Use the Streaming API to send Account and Contact data from Salesforce to the OMS.
C
Explanation:
Implementing a Master Data Management strategy to reconcile Leads, Accounts, and Contacts is the approach that the architect should suggest so that the requirements are met for UC. A Master Data Management strategy can provide a consistent and unified view of data across multiple systems, by defining and enforcing rules for data quality, governance, and integration. A Master Data Management strategy can also handle complex scenarios where different systems have different systems of record for different entities or fields, and where data can be modified in different systems with different values. A Master Data Management strategy can also provide a consolidated data store that links referenced records across systems and enables cross-system reporting and analysis. The other options are not suitable or sufficient for meeting the requirements, as they would either not provide a consolidated data store, not handle different systems of record, or not allow data modification in different system
Universal Containers (UC) is planning to move away from legacy CRM to Salesforce. As part of one-time data migration, UC will need to keep the original date when a contact was created in the legacy system.
How should an Architect design the data migration solution to meet this requirement?
- A . After the data is migrated, perform an update on all records to set the original date in a standard Created Date field.
- B . Create a new field on the Contact object to capture the Created Date. Hide the standard Created Date field using Field -Level Security.
- C . Enable "Set Audit Fields" and assign the permission to the user loading the data for the duration of the migration.
- D . Write an Apex trigger on the Contact object, before insert event to set the original value in a standard Created Date field.
C
Explanation:
Enabling “Set Audit Fields” allows the user loading the data to set the value of the standard CreatedDate field to match the original date from the legacy system. This is a one-time permission that can be revoked after the migration is completed. The other options would either not work or require additional customization
Universal Containers (UC) is planning to move away from legacy CRM to Salesforce. As part of one-time data migration, UC will need to keep the original date when a contact was created in the legacy system.
How should an Architect design the data migration solution to meet this requirement?
- A . After the data is migrated, perform an update on all records to set the original date in a standard Created Date field.
- B . Create a new field on the Contact object to capture the Created Date. Hide the standard Created Date field using Field -Level Security.
- C . Enable "Set Audit Fields" and assign the permission to the user loading the data for the duration of the migration.
- D . Write an Apex trigger on the Contact object, before insert event to set the original value in a standard Created Date field.
C
Explanation:
Enabling “Set Audit Fields” allows the user loading the data to set the value of the standard CreatedDate field to match the original date from the legacy system. This is a one-time permission that can be revoked after the migration is completed. The other options would either not work or require additional customization
Universal Containers (UC) is implementing a formal, cross -business -unit data governance program As part of the program, UC will implement a team to make decisions on enterprise -wide data governance.
Which two roles are appropriate as members of this team? Choose 2 answers
- A . Analytics/BI Owners
- B . Data Domain Stewards
- C . Salesforce Administrators
- D . Operational Data Users
A, B
Explanation:
Analytics/BI Owners and Data Domain Stewards are appropriate roles as members of a team that makes decisions on enterprise-wide data governance. Analytics/BI Owners are responsible for defining the business requirements and metrics for data analysis and reporting, and Data Domain Stewards are responsible for defining and enforcing the data quality standards and rules for specific data domains. Salesforce Administrators and Operational Data Users are not suitable roles for this team, as they are more focused on the operational aspects of data management, such as configuration, maintenance, and usage.
Universal Containers is experiencing frequent and persistent group membership locking issues that severely restricts its ability to manage manual and a automated updates at the same time.
What should a data architect do in order to restore the issue?
- A . Enable granular locking
- B . Enable parallel sharing rule calculation.
- C . Enable defer sharing calculation
- D . Enable implicit sharing
A
Explanation:
Enabling granular locking allows concurrent sharing rule calculations and group membership updates to run without locking each other1. This can help resolve the group membership locking issues that UC is experiencing.