Question 1

Which three characteristics of a skinny table help improve report and query performance?

Accepted Answer

A, D, E

Explanation: The three characteristics of a Skinny table that help improve report and query performance are: Skinny tables can contain frequently used fields and thereby help avoid joins. Skinny tables are kept in sync with changes to data in the source tables. Skinny tables do not include records that are available in the recycle bin. These characteristics are beneficial because they reduce the query complexity and execution time, and improve the data accuracy and freshness. For example, skinny tables can contain frequently used fields from multiple objects, such as Account and Contact, and thereby help avoid joins that can slow down queries4. Skinny tables are updated automatically when the source tables are modified, so they always reflect the latest data5. Skinny tables do not include records that are available in the recycle bin, so they only contain active records that are relevant for reports and queries.

Question 2

Universal Containers (UC) has built a custom application on Salesforce to help track shipments
around the world. A majority of the shipping records are stored on premise in an external data
source. UC needs shipment details to be exposed to the custom application, and the data needs to be
accessible in real time. The external data source is not OData enabled, and UC does not own a
middleware tool.
Which Salesforce Connect procedure should a data architect use to ensure UC's requirements are
met?

Accepted Answer

D

Explanation: According to this article, the Apex Connector Framework enables developers to create custom adapters for Salesforce Connect to access data from external systems that are not OData enabled. This can meet UC’s requirements of exposing shipment details to the custom application and accessing the data in real time.

Question 3

Universal Containers (UC) has lead assignment rules to assign leads to owners. Leads not routed by
assignment rules are assigned to a dummy user. Sales rep are complaining of high load times and
issues with accessing leads assigned to the dummy user.
What should a data architect recommend to solve these performance issues?

Accepted Answer

B

Explanation: According to the official Salesforce guide1, assigning leads to a single dummy user can cause performance issues and data skew, especially if the dummy user owns more than 10,000 records. Data skew occurs when a single user or a small number of users own a disproportionately large number of records, which can affect query performance and sharing calculations. Option B is the correct answer because it suggests creating multiple dummy users and assigning leads to them, which can distribute the load and reduce data skew. Option A is incorrect because assigning the dummy user to the last role in the role hierarchy does not affect the performance or data skew issues. Option C is incorrect because assigning the dummy user to the highest role in the role hierarchy can worsen the performance and data skew issues, as it will grant access to more users and records. Option D is incorrect because periodically deleting leads can cause data loss and does not address the root cause of the problem.

Question 4

Universal Container (UC) has accumulated data over years and has never deleted data from its
Salesforce org. UC is now exceeding the storage allocations in the org. UC is now looking for option
to delete unused from the org.
Which three recommendations should a data architect make is order to reduce the number of
records from the org?
Choose 3 answers

Accepted Answer

A, C, E

Explanation: Using hard delete in Bulk API, identifying records that have not been modified or used in last 3 years, and archiving the records in EDW before deleting from Salesforce are all good recommendations to reduce the number of records from the org1. Using hard delete in batch Apex or Rest API may not be as efficient or scalable as Bulk API

Question 5

Universals Containers’ system administrators have been complaining that they are not able to make
changes to its users’ record, including moving them to new territories without getting “unable to lock
row” errors. This is causing the system admins to spend hours updating user records every day.
What should the data architect do to prevent the error?

Accepted Answer

B

Explanation: Enabling granular locking (option B) is the best option to prevent the error, as it allows finer control over how records are locked during automated or manual processes, and reduces the chances of lock contention or deadlock. Reducing number of users updated concurrently (option A) is not a good option, as it may limit the productivity and efficiency of the system admins, and it does not address the root cause of the error. Analyzing Splunk query to spot offending records (option C) is also not a good option, as it may require more time and effort, and it does not provide a permanent solution for the error. Increasing CPU for the Salesforce org (option D) is also not a good option, as it may introduce additional cost and complexity, and it does not solve the root cause of the error.

Question 6

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?

Accepted Answer

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.

Question 7

Universal container (UC) would like to build a Human resources application on Salesforce to manage
employee details, payroll, and hiring efforts. To adequately and store the relevant data, the
application will need to leverage 45 custom objects. In addition to this, UC expects roughly 20,00 API
calls into Salesfoce from an n-premises application daily.
Which license type should a data architect recommend that best fits these requirements?

Accepted Answer

C

Explanation: Lightning Platform Plus is the license type that best fits UC’s requirements, as it allows up to 50 custom objects and 40,000 API calls per user per 24-hour period4. Service Cloud does not provide enough custom objects or API calls. Lightning Platform Start only allows up to 10 custom objects and 5,000 API calls per user per 24-hour period. Lightning External Apps Start is for external users and does not provide enough API calls.

Question 8

Universal Container require all customers to provide either a phone number of an email address when registering for an account. What should the data architect use to ensure this requirement is met?

Accepted Answer

A

Explanation: Using a validation rule is the best way to ensure that all customers provide either a phone number or an email address when registering for an account, as it allows defining a formula that evaluates whether a record meets certain criteria. Using required fields may not work if both phone number and email address are required. Using an Apex class or a Process Builder may be more complex or cumbersome than using a validation rule.

Question 9

North Trail Outfitters (NTD) is in the process of evaluating big objects to store large amounts of asset
data from an external system. NTO will need to report on this asset data weekly.
Which two native tools should a data architect recommend to achieve this reporting requirement?

Accepted Answer

B, D

Explanation: Async SOQL with a custom object (option B) and Einstein Analytics (option D) are the two native tools that can be used to report on big object data. Async SOQL allows querying big object data and storing the results in a custom object, which can then be used for reporting. Einstein Analytics can connect to big object data sources and provide advanced analytics and visualization features. Standard reports and dashboards (option A) and standard SOQL queries (option C) cannot be used to report on big object data, as they do not support big object fields

Question 10

Universal Containers (UC) has implemented a master data management strategy, which uses a
central system of truth, to ensure the entire company has the same customer information in all
systems. UC customer data changes need to be accurate at all times in all of the systems. Salesforce
is the identified system of record for this information.
What is the correct solution for ensuring all systems using customer data are kept up to date?

Accepted Answer

D

Explanation: Having each system pull the record changes from Salesforce using change data capture (option D) is the correct solution for ensuring all systems using customer data are kept up to date, as it allows the systems to subscribe to real-time events from Salesforce and receive notifications when customer records are created, updated, deleted, or undeleted. Sending customer data nightly to the system of truth in a scheduled batch job (option A) or sending customer record changes from Salesforce to each system in a nightly batch job (option B) are not good solutions, as they may cause data latency and inconsistency, and they do not provide real-time updates. Sending customer record changes from Salesforce to the system of truth in real time (option C) is also not a good solution, as it does not address how the other systems will receive the updates from the system of truth.

Question 11

Universal Containers has been a customer of Salesforce for 10 years. Currently they have 2 million
accounts in the system. Due to an erroneous integration built 3 years ago, it is estimated there are
500,000 duplicates in the system.
Which solution should a data architect recommend to remediate the duplication issue?

Accepted Answer

D

Explanation: Implementing duplicate rules (option D) is the best solution to remediate the duplication issue, as it allows the data architect to identify and merge duplicate accounts in Salesforce using native features and tools. Developing an ETL process that utilizes the merge API to merge the duplicate records (option A) is not a good solution, as it may require more coding and testing effort, and it does not prevent duplicates from being created in Salesforce. Utilizing a data warehouse as the system of truth (option B) is also not a good solution, as it may introduce additional complexity and cost, and it does not address the duplication issue in Salesforce. Extracting the data using data loader and using excel to merge the duplicate records (option C) is also not a good solution, as it may be time- consuming and error-prone, and it does not prevent duplicates from being created in Salesforce.

Question 12

A casino is implementing Salesforce and is planning to build a customer 360 degree view for a
customer who visits its resorts. The casino currently maintains the following systems that record
customer activity: L Point-of-sale system: All purchases for a customer
2. Salesforce; All customer service activity and sales activities for a customer
3. Mobile app: All bookings, preferences, and browser activity for a customer
4. Marketing: All email, SMS, and social campaigns for a customer
Customer service agents using Salesforce would like to view the activities from all four systems to
provide support to customers. The information has to be current and real time.
What strategy should the data architect implement to satisfy this requirement?

Accepted Answer

A

Explanation: Exploring external data sources in Salesforce to build a 360 degree view of the customer (option A) is the best strategy to satisfy this requirement, as it allows customer service agents to view the activities from all four systems in real time without storing or replicating the data in Salesforce. Using a customer data mart to create the 360 degree view of the customer (option B) is not a good strategy, as it may introduce additional complexity and cost, and it does not leverage the native Salesforce features. Periodically uploading summary information in Salesforce to build a 360 degree view (option C) is also not a good strategy, as it may cause data latency and inconsistency, and it does not provide real-time information. Migrating customer activities from all four systems into Salesforce (option D) is also not a good strategy, as it may cause data redundancy and conflicts, and it does not scale well with large volumes of data.

Question 13

Universal Container is using Salesforce for Opportunity management and enterprise resource
planning (ERP) for order management. Sales reps do not have access to the ERP and have no visibility
into order status.
What solution a data architect recommends to give the sales team visibility into order status?

Accepted Answer

C

Explanation: The correct answer is C, leverage Salesforce Connect to bring the order line item from the legacy system to Salesforce. Salesforce Connect is a feature that allows you to integrate external data sources with Salesforce and access them in real time without copying or synchronizing the data. This way, the sales team can view the order status from the ERP system without having access to it. Leveraging Canvas, building batch jobs, or building real-time integration are also possible solutions, but they are more complex and costly than using Salesforce Connect.

Question 14

Northern trail Outfitters (NTO) runs its entire out of an enterprise data warehouse (EDW), NTD’s
sales team starting to use Salesforce after a recent implementation, but currently lacks data required
to advanced and opportunity to the next stage.
NTO’s management has research Salesforce Connect and would like to use It to virtualize and report
on data from the EDW within Salesforce. NTO will be running thousands of reports per day across 10
to 15 external objects.
What should a data architect consider before implementing Salesforce Connect for reporting?

Accepted Answer

B

Explanation: According to the Salesforce Connect Reporting blog post, one of the considerations for using Salesforce Connect for reporting is the OData callout limits per day. The blog post states that “Salesforce Connect has a limit of 100,000 callouts per day. This limit is shared across all external data sources in your org. If you exceed this limit, you will receive an error message and no more callouts will be allowed until the next day.” Therefore, a data architect should consider this limit before implementing Salesforce Connect for reporting.

Question 15

Universal Containers has a requirement to store more than 100 million records in salesforce and
needs to create a custom big object to support this business requirement.
Which two tools should a data architect use to build custom object?

Accepted Answer

B, C

Explanation: To build a custom big object to support storing more than 100 million records in Salesforce, a data architect should use Metadata API or Big Object in setup. Metadata API is an API that allows developers to create, retrieve, update, or delete metadata components in Salesforce programmatically. Big Object in setup is a user interface that allows admins to create big objects declaratively without writing code. Both tools can be used to define custom big objects and their fields, indexes, and relationships in Salesforce. Option A is incorrect because DX (Developer Experience) is a set of tools that allows developers to create and manage applications on Salesforce Platform, but it does not support creating big objects directly. Option D is incorrect because Object Manager in setup is a user interface that allows admins to create and manage standard and custom objects in Salesforce, but it does not support creating big objects declaratively.

Free Salesforce Data-Architect Actual Exam Questions