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?
A. Use DX to create big object. B. Use Metadata API to create big object. C. Go to Big Object in setup select new to create big object. D. Go to Object Manager in setup and select new to create big object.
B. Use Metadata API to create big object. C. Go to Big Object in setup select new to create big object.
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.
Question 82:
A manager at Cloud Kicks is importing Leads into Salesforce and needs to avoid creating duplicate records.
Which two approaches should the manager take to achieve this goal? (Choose two.)
A. Acquire an AppExchange Lead de-duplication application. B. Implement Salesforce Matching and Duplicate Rules. C. Run the Salesforce Lead Mass de-duplication tool. D. Create a Workflow Rule to check for duplicate records.
A. Acquire an AppExchange Lead de-duplication application. B. Implement Salesforce Matching and Duplicate Rules.
Explanation
Acquiring an AppExchange Lead de-duplication application and implementing Salesforce Matching and Duplicate Rules are two approaches that the manager at Cloud Kicks should take to avoid creating duplicate records when importing Leads into Salesforce. An AppExchange Lead de-duplication application can provide additional features and functionality for finding and preventing duplicate Leads during import, such as fuzzy matching, custom rules, mass merge, etc.
Salesforce Matching and Duplicate Rules can allow the manager to define how Salesforce identifies duplicate Leads based on various criteria and how users can handle them during import, such as blocking, allowing, or alerting them. The other options are not feasible or effective for avoiding duplicate records, as they would either not work during import, not provide de-duplication capabilities, or require additional customization.
Question 83:
Universal Containers (UC) manages Vehicle and Service History in Salesforce. Vehicle (Vehicle__ c) and Service History (Service-History__ c) are both custom objects related through a lookup relationship.
Every week a batch synchronization process updates the Vehicle and Service History records in Salesforce. UC has two hours of migration window every week and is facing locking issues as part of the data migration process.
What should a data architect recommend to avoid locking issues without affecting performance of data migration?
A. Use Bulk API parallel mode for data migration B. Use Bulk API serial mode for data migration C. Insert the order in another custom object and use Batch Apex to move the records to Service_ Order__ c object. D. Change the lookup configuration to "Clear the value of this field" when lookup record is deleted.
B. Use Bulk API serial mode for data migration
Explanation
According to the official Salesforce guide1, using Bulk API serial mode for data migration can help avoid locking issues by processing batches in a single thread. This mode ensures that batches are processed in the order they are received and that only one batch is processed at a time. This reduces the risk of lock contention and deadlocks, especially when updating parent and child records in a lookup relationship. Option B is the correct answer because it suggests using Bulk API serial mode for data migration. Option A is incorrect because using Bulk API parallel mode for data migration can cause locking issues by processing batches in multiple threads. This mode does not guarantee the order of batch processing and can result in concurrent updates to the same records, which can lead to lock contention and deadlocks. Option C is incorrect because inserting the order in another custom object and using Batch Apex to move the records to Service_Order__c object adds unnecessary complexity and overhead to the data migration process. Option D is incorrect because changing the lookup configuration to "Clear the value of this field" when lookup record is deleted does not address the locking issues caused by data migration, but rather by record deletion.
Question 84:
A large automobile manufacturer has decided to use Salesforce as its CRM. It needs to maintain the following dealer types in their CRM:
1. Local dealers
2. Regional distributor
3. State distributor
4. Service dealer
The attributes are different for each of the customer types. The CRM users should be allowed to enter only attributes related to the customer types. The processes and business rules for each of the customer types could be different.
How should the different dealers be maintained in Salesforce?
A. Use Accounts for dealers, and create record types for each of the dealer types. B. Create dealers as Accounts, and build custom views for each of the dealer types. C. Use Accounts for dealers and custom picklist field for each of the dealer types D. Create Custom objects for each dealer types and custom fields for dealer attributes.
A. Use Accounts for dealers, and create record types for each of the dealer types.
Explanation
According to Trailhead2, record types are a feature that allows administrators to create different business processes, page layouts, and picklist values for different types of records within an object. Record types can be used to maintain different dealer types in Salesforce by creating record types for each of the dealer types and assigning them appropriate attributes, processes, and rules. Option A is the correct answer because it suggests using Accounts for dealers, and creating record types for each of the dealer types. Option B is incorrect because creating dealers as Accounts, and building custom views for each of the dealer types does not allow CRM users to enter only attributes related to the customer types, nor does it enable different processes and business rules for each of the customer types. Option C is incorrect because using Accounts for dealers and custom picklist field for each of the dealer types does not allow CRM users to enter only attributes related to the customer types, nor does it enable different processes and business rules for each of the customer types. Option D is incorrect because creating Custom objects for each dealer types and custom fields for dealer attributes can be unnecessary and complex, as it requires creating multiple objects and relationships instead of using the standard Account object.
Question 85:
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. 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
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.
Question 86:
DreamHouse Realty has a legacy system that captures Branch Offices and Transactions. DreamHouse Realty has 15 Branch Offices. Transactions can relate to any Branch Office. DreamHouse Realty has created hundreds of thousands of Transactions per year. A Data Architect needs to denormalize this data model into a single Transaction object with a Branch Office picklist.
What are two important considerations for the Data Architect in this scenario? (Choose two.)
A. Standard list view in-line editing. B. Limitations on Org data storage. C. Bulk API limitations on picklist fields. D. Limitations on master-detail relationships.
B. Limitations on Org data storage. C. Bulk API limitations on picklist fields.
Explanation
The Data Architect should consider the limitations on Org data storage and the Bulk API limitations on picklist fields when denormalizing the data model into a single Transaction object with a Branch Office picklist. The Org data storage limit is the total amount of data that can be stored in a Salesforce Org, and it depends on the edition and license type of the Org1. The Bulk API limit on picklist fields is the maximum number of values that can be imported or exported using the Bulk API, and it is 1,000 values per picklist field2. These limitations could affect the performance and scalability of the data model, and the Data Architect should plan accordingly.
Question 87:
Northern Trail Outfitters (NTO) has an external product master system that syncs product and pricing information with Salesforce. Users have been complaining that they are seeing discrepancies in product and pricing information displayed on the NTO website and Salesforce.
As a data architect, which action is recommended to avoid data sync issues?
A. Build a custom integration for two-way sync of product and pricing information between product master to Salesforce. B. Build a custom integration for one-way sync of product and pricing information from product master to Salesforce. C. Implement a manual process to update the products from an extract from the products master on a weekly basis. D. Use the Customer 360 data manager to sync product and pricing information from product master database to Salesforce.
D. Use the Customer 360 data manager to sync product and pricing information from product master database to Salesforce.
Explanation
According to Trailhead2, Customer 360 Data Manager is a feature that allows administrators to connect, reconcile, and share customer data across Salesforce orgs and external systems. Customer 360 Data Manager can sync product and pricing information from product master database to Salesforce using predefined mappings and rules, ensuring data quality and consistency. Option D is the correct answer because it suggests using Customer 360 Data Manager to sync product and pricing information from product master database to Salesforce. Option A is incorrect because building a custom integration for two-way sync of product and pricing information between product master and Salesforce can introduce data conflicts and duplication issues, as both systems can update the same data independently. Option B is incorrect because building a custom integration for one-way sync of product and pricing information from product master to Salesforce can be costly and time-consuming, as it requires custom development and maintenance. Option C is incorrect because implementing a manual process to update the products from an extract from the products master on a weekly basis can result in data latency and errors, as the products information may change more frequently than once a week.
Question 88:
In their legacy system. Universal Containers has a monthly accounts receivable report that compiles data from Accounts, Contacts, Opportunities, Orders. and Order Line Items.
What difficulty will an architect run into when implementing this in Salesforce?
A. Salesforce allows up to four objects in a single report type. B. Salesforce does not support Orders or Order Line Items. C. A report cannot contain data from Accounts and Contacts. D. Custom report types cannot contain Opportunity data.
A. Salesforce allows up to four objects in a single report type.
Explanation
Salesforce allows up to four objects in a single report type. This means that if an architect wants to create a report that compiles data from Accounts, Contacts, Opportunities, Orders, and Order Line Items, they will run into a difficulty because that would require five objects in a single report type. To overcome this limitation, the architect can either create two separate report types and join them in a joined report, or use an external reporting tool that can access data from multiple objects.
Question 89:
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. Add custom indexes on frequently searched account and contact objects fields
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.
Question 90:
NTO has multiple systems across its enterprise landscape including salesforce, with disparate version the customer records.
In salesforce, the customer is represented by the contact object.
NTO utilizes an MDM solution with these attributes:
1.The MDM solution keeps track of customer master with a master key. 2.The master key is a map to the record ID's from each external system that customer data is stored within. 3.The MDM solution provides de-duplication features, so it acts as the single source of truth.
How should a data architect implement the storage of master key within salesforce?
A. Store the master key in Heroku postgres and use Heroku connect for synchronization. B. Create a custom object to store the master key with a lookup field to contact. C. Create an external object to store the master key with a lookup field to contact. D. Store the master key on the contact object as an external ID (Field for referential imports)
D. Store the master key on the contact object as an external ID (Field for referential imports)
Explanation
The best way to implement the storage of master key within Salesforce is to store it on the contact object as an external ID field for referential imports. This way, the data architect can use the master key as a unique identifier to match records from different systems and avoid duplicates. The other options are not feasible because they either require additional storage or do not support referential imports.
Nowadays, the certification exams become more and more important and required by more and more
enterprises when applying for a job. But how to prepare for the exam effectively? How to prepare
for the exam in a short time with less efforts? How to get a ideal result and how to find the
most reliable resources? Here on Vcedump.com, you will find all the answers.
Vcedump.com provide not only Salesforce exam questions,
answers and explanations but also complete assistance on your exam preparation and certification
application. If you are confused on your DATA-ARCHITECT exam preparations
and Salesforce certification application, do not hesitate to visit our
Vcedump.com to find your solutions here.