UC has been using SF for 10 years. Lately, users have noticed, that the pages load slowly when viewing Customer and Account list view.
To mitigate, UC will implement a data archive strategy to reduce the amount of data actively loaded.
Which 2 tasks are required to define the strategy? Choose 2 answers:
A. Identify the recovery point objective. B. Identify how the archive data will be accessed and used. C. Identify the recovery time objective. D. Identify the data retention requirements
B. Identify how the archive data will be accessed and used. D. Identify the data retention requirements
Explanation
The two tasks required to define the data archive strategy are to identify how the archive data will be accessed and used, and identify the data retention requirements. Data archiving is the process of moving infrequently used or historical data from active storage to a separate storage location for long-term retention. Data archiving can improve performance, reduce storage costs, and comply with legal or regulatory obligations. To define a data archive strategy, a data architect needs to consider how the archived data will be accessed and used by different users or processes in Salesforce or outside Salesforce, and how long the archived data needs to be retained based on business or legal requirements.
Question 2:
A custom pricing engine for a Salesforce customer has to be decided by factors with the following hierarchy:
State in which the customer is located
City in which the customer is located if available
Zip code in which the customer is located if available
Changes to this information should have minimum code changes What should a data architect recommend to maintain this information for the custom pricing engine that is to be built in Salesforce?
A. Create a custom object to maintain the pricing criteria. B. Assign the pricing criteria within customer pricing engine. C. Maintain require pricing criteria in custom metadata types. D. Configure the pricing criteria in price books.
C. Maintain require pricing criteria in custom metadata types.
Explanation
According to the Get Started with Custom Metadata Types unit on Trailhead, one of the use cases for custom metadata types is to define custom charges for an accounting app. The unit states that "Say that your org uses a standard accounting app. You can create a custom metadata type that defines custom charges, like duties and VAT rates. Then you can write some Apex code that calculates the total amount due for each invoice by using the metadata from your custom metadata type." Therefore, a similar approach can be used to maintain the pricing criteria for a custom pricing engine in Salesforce.
Question 3:
NTO has a loyalty program to reward repeat customers. The following conditions exists:
1.Reward levels are earned based on the amount spent during the previous 12 months.
2.The program will track every item a customer has bought and grant them points for discount.
3.The program generates 100 million records each month.
NTO customer support would like to see a summary of a customer's recent transaction and reward level(s) they have attained.
Which solution should the data architect use to provide the information within the salesforce for the customer support agents?
A. Create a custom object in salesforce to capture and store all reward program. Populate nightly from the point-of-scale system, and present on the customer record. B. Capture the reward program data in an external data store and present the 12 months trailing summary in salesforce using salesforce connect and then external object. C. Provide a button so that the agent can quickly open the point of sales system displaying the customer history. D. Create a custom big object to capture the reward program data and display it on the contact record and update nightly from the point-of-scale system.
D. Create a custom big object to capture the reward program data and display it on the contact record and update nightly from the point-of-scale system.
Explanation
According to the Get Started with Big Objects unit on Trailhead, one of the use cases for custom big objects is to store and manage loyalty program data for customers. The unit states that "From loyalty programs to transactions, order, and billing information, use a custom big object to keep track of every detail." Therefore, a custom big object can be used to capture the reward program data and display it on the contact record. Additionally, according to the Big Objects Implementation Guide, big objects can handle massive amounts of data (up to billions of records) and can be updated nightly from external systems using Bulk API or batch Apex. Therefore, a custom big object can meet the requirements of NTO's loyalty program scenario.
Question 4:
Universal Containers (UC) is implementing Salesforce Sales Cloud and Service Cloud. As part of their implementation, they are planning to create a new custom object (Shipments), which will have a lookup relationship to Opportunities.
When creating shipment records, Salesforce users need to manually input a customer reference, which is provided by customers, and will be stored in the Customer_Reference__c text custom field. Support agents will likely use this customer reference to search for Shipment records when resolving shipping issues. UC is expecting to have around 5 million shipment records created per year.
What is the recommended solution to ensure that support agents using global search and reports can quickly find shipment records?
A. Implement an archiving process for shipment records created after five years. B. Implement an archiving process for shipment records created after three years. C. Set Customer-Reference_c as an External ID (non-unique). D. Set Customer-Reference_c as an External ID (unique).
D. Set Customer-Reference_c as an External ID (unique).
Explanation
Setting Customer-Reference_c as an External ID (unique) is the recommended solution to ensure that support agents using global search and reports can quickly find shipment records. This is because external ID fields are indexed and can be used as filters in reports and list views4. Making the field unique also ensures that there are no duplicate values that could confuse the search results.
Question 5:
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?
A. Service Cloud B. Lightning platform Start C. Lightning Platform plus D. Lightning External Apps Starts
C. Lightning Platform plus
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 6:
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. 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
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.
Question 7:
Universal Container has implemented Sales Cloud to manage patient and related health records. During a recent security audit of the system, it was discovered that same standard and custom fields need to encrypted.
Which solution should a data architect recommend to encrypt existing fields?
A. Use Apex Crypto Class encrypt customer and standard fields. B. Implement classic encryption to encrypt custom and standard fields. C. Implement shield platform encryption to encrypt and standard fields D. Expert data out of Salesforce and encrypt custom and standard fields.
C. Implement shield platform encryption to encrypt and standard fields
Explanation
The correct answer is C, implement shield platform encryption to encrypt standard and custom fields. Shield platform encryption is a feature that allows you to encrypt sensitive data at rest in Salesforce without affecting its functionality. You can encrypt both standard and custom fields using shield platform encryption. Using Apex Crypto Class, implementing classic encryption, or exporting data out of Salesforce are not recommended solutions, as they will either limit your functionality, require custom code, or compromise your data security.
Question 8:
Universal Containers (UC) is launching an RFP to acquire a new accounting product available on AppExchange. UC is expecting to issue 5 million invoices per year, with each invoice containing an average of 10 line items.
What should UC's Data Architect recommend to ensure scalability?
A. Ensure invoice line items simply reference existing Opportunity line items. B. Ensure the account product vendor includes Wave Analytics in their offering. C. Ensure the account product vendor provides a sound data archiving strategy. D. Ensure the accounting product runs 100% natively on the Salesforce platform.
C. Ensure the account product vendor provides a sound data archiving strategy.
Explanation
A sound data archiving strategy is essential for ensuring scalability and performance of any application that deals with large volumes of data. You need to consider factors like data retention policies, storage limits, backup and recovery options, and data access requirements when designing a data archiving solution2. You can use tools like OwnBackup, Odaseva, or ArchiveIt to archive your data from Salesforce to external systems
Question 9:
NTO has implemented salesforce for its sales users. The opportunity management in salesforce is implemented as follows:
1.Sales users enter their opportunities in salesforce for forecasting and reporting purposes.
2.NTO has a product pricing system (PPS) that is used to update opportunity amount field on opportunities on a daily basis.
3.PPS is the trusted source within the NTO for opportunity amount.
4.NTO uses opportunity forecast for its sales planning and management.
Sales users have noticed that their updates to the opportunity amount field are overwritten when PPS updates their opportunities.
How should a data architect address this overriding issue?
A. Create a custom field for opportunity amount that sales users update separating the fields that PPS updates. B. Create a custom field for opportunity amount that PPS updates separating the field that sales user updates. C. Change opportunity amount field access to read only for sales users using field level security. D. Change PPS integration to update only opportunity amount fields when values is NULL.
C. Change opportunity amount field access to read only for sales users using field level security.
Explanation
Changing the opportunity amount field access to read only for sales users using field level security is the best way to address the overriding issue. This way, the sales users can still view the opportunity amount field but cannot edit it, and PPS can update it as the trusted source
Question 10:
The architect is planning a large data migration for Universal Containers from their legacy CRM system to Salesforce. What three things should the architect consider to optimize performance of the data migration? Choose 3 answers
A. Review the time zones of the User loading the data. B. Remove custom indexes on the data being loaded. C. Determine if the legacy system is still in use. D. Defer sharing calculations of the Salesforce Org. E. Deactivate approval processes and workflow rules.
B. Remove custom indexes on the data being loaded. D. Defer sharing calculations of the Salesforce Org. E. Deactivate approval processes and workflow rules.
Explanation
Removing custom indexes on the data being loaded will prevent unnecessary index maintenance and improve the data load speed. Deferring sharing calculations of the Salesforce Org will avoid frequent sharing rule evaluations and reduce the load time. Deactivating approval processes and workflow rules will prevent triggering any automation logic that might slow down or fail the data load.
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.