Practice Free Plat-Arch-201 Exam Online Questions
Universal Containers (UC) owns several Salesforce orgs across a variety of business units. UC management has declared that it needs the ability to report on Accounts and Opportunities from each org in one place. Once the data is brought together into a global view, management would like to use advanced Al-driven analytics on the dataset.
Which tool should a data architect recommend to accomplish this reporting requirement?
- A . Run standard reports and dashboards.
- B . Install a third-party AppExchange tool for multi-org reporting.
- C . Use Einstein Analytics for multi-org.
- D . Write a Python script to aggregate and visualize the data.
C
Explanation:
According to this article, Einstein Analytics for multi-org can help UC to report on accounts and opportunities from each org in one place. It can also provide advanced AI-driven analytics on the dataset using Einstein Discovery.
What makes Skinny tables fast? Choose three answers.
- A . They do not include soft-deleted records
- B . They avoid resource intensive joins
- C . Their tables are kept in sync with their source tables when the source tables are modified
- D . They can contain fields from other objects
- E . They support up to a max of 100 of columns
A, B, C
Explanation:
Skinny tables are custom tables that contain frequently used fields from a standard or custom object. They are used to improve performance by reducing the number of database joins required for queries. Skinny tables have the following characteristics1:
They do not include soft-deleted records, which means they only contain active records and save space.
They avoid resource intensive joins by storing data from multiple objects in one table, which reduces the query time and complexity.
Their tables are kept in sync with their source tables when the source tables are modified, which ensures data consistency and accuracy.
Company S was recently acquired by Company T. As part of the acquisition, all of the data for the Company S’s Salesforce instance (source) must be migrated into the Company T’s Salesforce instance (target). Company S has 6 million Case records.
An Architect has been tasked with optimizing the data load time.
What should the Architect consider to achieve this goal?
- A . Pre-process the data, then use Data Loader with SOAP API to upsert with zip compression enabled.
- B . Directly leverage Salesforce-to-Salesforce functionality to load Case data.
- C . Load the data in multiple sets using Bulk API parallel processes.
- D . Utilize the Salesforce Org Migration Tool from the Setup Data Management menu.
A
Explanation:
Pre-processing the data means transforming and cleansing the data before loading it into Salesforce. This can reduce the errors and conflicts that might occur during the data load. Using Data Loader with SOAP API to upsert with zip compression enabled can also improve the performance and efficiency of the data load by reducing the network bandwidth and avoiding duplication
Universal Containers (UC) is implementing a Salesforce project with large volumes of data and daily transactions. The solution includes both real-time web service integrations and Visualforce mash – ups with back -end systems. The Salesforce Full sandbox used by the project integrates with full-scale back -end testing systems.
What two types of performance testing are appropriate for this project? Choose 2 answers
- A . Pre -go -live automated page -load testing against the Salesforce Full sandbox.
- B . Post go -live automated page -load testing against the Salesforce Production org.
- C . Pre -go -live unit testing in the Salesforce Full sandbox.
- D . Stress testing against the web services hosted by the integration middleware.
A, D
Explanation:
Pre-go-live automated page-load testing against the Salesforce Full sandbox can help identify and resolve any performance bottlenecks or issues before deploying the solution to production. The Full sandbox is an ideal environment for performance testing as it replicates the production org in terms of data, metadata, and integrations. Stress testing against the web services hosted by the integration middleware can also help evaluate the scalability and reliability of the integration solution under high load conditions.
Universal Containers (UC) is expecting to have nearly 5 million shipments records in its Salesforce org. Each shipment record has up to 10 child shipment item records. The Shipment custom object has an Organization-wide Default (OWD) sharing model set to Private and the Shipment Item custom object has a Master-Detail relationship to Shipment. There are 25 sharing rules set on the Shipment custom object, which allow shipment records to be shared to each of UC’s 25 business areas around the globe. These sharing rules use public groups, one for each business area plus a number of groups for management and support roles. UC has a high turnover of Sales Reps and often needs to move Sales Reps between business areas in order to meet local demand.
What feature would ensure that performance, when moving Sales Reps between regions, remains adequate while meeting existing requirements?
- A . Implement data archiving for old Shipment records.
- B . Contact Salesforce to create Skinny tables on Shipment.
- C . Configure shipment OWD to Public Read/Write.
- D . Contact Salesforce to enable Defer Sharing Rules
D
Explanation:
Contacting Salesforce to enable Defer Sharing Rules is the feature that would ensure that performance, when moving Sales Reps between regions, remains adequate while meeting existing requirements. Defer Sharing Rules allows you to defer sharing rule recalculation when you make changes to public groups or roles that are used in sharing rules. This can improve performance and avoid locking issues when you move users between groups or roles2. Implementing data archiving for old Shipment records will not help with the performance issue related to sharing rules. Contacting Salesforce to create Skinny tables on Shipment will not help with the performance issue related to sharing rules. Configuring shipment OWD to Public Read/Write will not meet the existing requirements of having a Private sharing model.
Universal Containers (UC) is expecting to have nearly 5 million shipments records in its Salesforce org. Each shipment record has up to 10 child shipment item records. The Shipment custom object has an Organization-wide Default (OWD) sharing model set to Private and the Shipment Item custom object has a Master-Detail relationship to Shipment. There are 25 sharing rules set on the Shipment custom object, which allow shipment records to be shared to each of UC’s 25 business areas around the globe. These sharing rules use public groups, one for each business area plus a number of groups for management and support roles. UC has a high turnover of Sales Reps and often needs to move Sales Reps between business areas in order to meet local demand.
What feature would ensure that performance, when moving Sales Reps between regions, remains adequate while meeting existing requirements?
- A . Implement data archiving for old Shipment records.
- B . Contact Salesforce to create Skinny tables on Shipment.
- C . Configure shipment OWD to Public Read/Write.
- D . Contact Salesforce to enable Defer Sharing Rules
D
Explanation:
Contacting Salesforce to enable Defer Sharing Rules is the feature that would ensure that performance, when moving Sales Reps between regions, remains adequate while meeting existing requirements. Defer Sharing Rules allows you to defer sharing rule recalculation when you make changes to public groups or roles that are used in sharing rules. This can improve performance and avoid locking issues when you move users between groups or roles2. Implementing data archiving for old Shipment records will not help with the performance issue related to sharing rules. Contacting Salesforce to create Skinny tables on Shipment will not help with the performance issue related to sharing rules. Configuring shipment OWD to Public Read/Write will not meet the existing requirements of having a Private sharing model.
What is an advantage of using Custom metadata type over Custom setting?
- A . Custom metadata records are not copied from production to sandbox.
- B . Custom metadata types are available for reporting.
- C . Custom metadata records are deployable using packages.
- D . Custom metadata records are editable in Apex.
C
Explanation:
Custom metadata records are deployable using packages, which makes them easier to migrate from one environment to another. Custom settings records are not deployable using packages, and they are copied from production to sandbox. Custom metadata types are not available for reporting, and custom metadata records are not editable in Apex.
A large retail company has recently chosen SF as its CRM solution.
They have the following record counts:
2500000 accounts
25000000 contacts
When doing an initial performance test, the data architect noticed an extremely slow response for reports and list views.
What should a data architect do to solve the performance issue?
- A . Load only the data that the users is permitted to access
- B . Add custom indexes on frequently searched account and contact objects fields
- C . Limit data loading to the 2000 most recently created records.
- D . Create a skinny table to represent account and contact objects.
B
Explanation:
The correct answer is B, add custom indexes on frequently searched account and contact object fields. Custom indexes are a way to improve the performance of your queries and reports by creating indexes on specific fields that are often used in filters or joins. By adding custom indexes on frequently searched account and contact object fields, you can speed up the response time for reports and list views. Loading only the data that users are permitted to access, limiting data loading to the 2000 most recent records, or creating a skinny table are also possible solutions, but they are either not feasible, not scalable, or not supported by Salesforce.
A customer wishes to migrate 700,000 Account records in a single migration into Salesforce.
What is the recommended solution to migrate these records while minimizing migration time?
- A . Use Salesforce Soap API in parallel mode.
- B . Use Salesforce Bulk API in serial mode.
- C . Use Salesforce Bulk API in parallel mode.
- D . Use Salesforce Soap API in serial mode.
C
Explanation:
Using Salesforce Bulk API in parallel mode can reduce the migration time by processing multiple batches of records simultaneously and leveraging the server resources more efficiently. The Bulk API is designed for loading large amounts of data into Salesforce
Northern Trail Outfitters (NTO) wants to capture a list of customers that have bought a particular product. The solution architect has recommended to create a custom object for product, and to create a lookup relationship between its customers and its products.
Products will be modeled as a custom object (NTO_ Product__ c) and customers are modeled
as person accounts. Every NTO product may have millions of customers looking up a single product, resulting in a lookup skew.
What should a data architect suggest to mitigate Issues related to lookup skew?
- A . Create multiple similar products and distribute the skew across those products.
- B . Change the lookup relationship to master-detail relationship.
- C . Create a custom object to maintain the relationship between products and customers.
- D . Select Clear the value of this field option while configuring the lookup relationship.
A
Explanation:
creating multiple similar products and distributing the skew across those products can be a way to mitigate issues related to lookup skew. The article explains that lookup skew happens when a very large number of records are associated with a single record in the lookup object, and this can cause record locking and performance issues. The article suggests creating multiple copies of the same product record and assigning different child records to each copy, so that the number of child records per parent record is reduced.