Practice Free Plat-Arch-201 Exam Online Questions
Universal Containers (UC) management has identified a total of ten text fields on the Contact object as important to capture any changes made to these fields, such as who made the change, when they made the change, what is the old value, and what is the new value. UC needs to be able to report on these field data changes within Salesforce for the past 3 months.
What are two approaches that will meet this requirement? Choose 2 answers
- A . Create a workflow to evaluate the rule when a record is created and use field update actions to store previous values for these ten fields in ten new fields.
- B . Write an Apex trigger on Contact after insert event and after update events and store the old values in another custom object.
- C . Turn on field Contact object history tracking for these ten fields, then create reports on contact history.
- D . Create a Contact report including these ten fields and Salesforce Id, then schedule the report to run once a day and send email to the admin.
B, C
Explanation:
To capture and report on any changes made to ten text fields on the Contact object for the past 3 months, the data architect should write an Apex trigger on Contact after insert and after update events and store the old values in another custom object, or turn on field Contact object history tracking for these ten fields and create reports on contact history. An Apex trigger can capture the old and new values of the fields, as well as the user and time of the change, and store them in a custom object that can be used for reporting. Field history tracking can also track the changes to the fields and store them in a history table that can be used for reporting. However, field history tracking only retains data for up to 18 months or 24 months with an extension, so it may not be suitable for longer-term reporting needs. The other options are not feasible or effective for capturing and reporting on field data changes.
UC has a classic encryption for Custom fields and is leveraging weekly data reports for data backups.
During the data validation of exported data UC discovered that encrypted field values are still being exported as part of data exported.
What should a data architect recommend to make sure decrypted values are exported during data export?
- A . Set a standard profile for Data Migration user, and assign view encrypted data
- B . Create another field to copy data from encrypted field and use this field in export
- C . Leverage Apex class to decrypt data before exporting it.
- D . Set up a custom profile for data migration user and assign view encrypted data.
A
Explanation:
The best solution to make sure decrypted values are exported during data export is to create another field to copy data from encrypted field and use this field in export. This is because classic encryption does not support exporting decrypted values of encrypted fields. The view encrypted data permission only allows users to view decrypted values in the user interface, but not in reports or data exports. Therefore, a workaround is to create a formula field or a workflow field update that copies the value of the encrypted field to another field, and use that field for data export. However, this solution has some drawbacks, such as exposing sensitive data in plain text and consuming extra storage space. A better solution would be to use Shield Platform Encryption, which supports exporting decrypted values of encrypted fields with the Export Encrypted Data permission
Universal Containers is looking to use Salesforce to manage their sales organization. They will be migrating legacy account data from two aging systems into Salesforce.
Which two design considerations should an architect take to minimize data duplication? Choose 2 answers
- A . Use a workflow to check and prevent duplicates.
- B . Clean data before importing to Salesforce.
- C . Use Salesforce matching and duplicate rules.
- D . Import the data concurrently.
B, C
Explanation:
Cleaning data before importing to Salesforce and using Salesforce matching and duplicate rules are two design considerations that an architect should take to minimize data duplication when migrating legacy account data from two aging systems into Salesforce. Cleaning data before importing involves removing or correcting any inaccurate, incomplete, or inconsistent data from the source systems, as well as identifying and resolving any potential duplicates. This ensures that only high-quality and unique data is imported to Salesforce. Using Salesforce matching and duplicate rules allows the architect to define how Salesforce identifies duplicate records during import and how users can handle them. This prevents or reduces the creation of duplicate records in Salesforce and improves data quality. The other options are not effective or recommended for minimizing data duplication.
Northern trail Outfitters (NTO) uses Sales Cloud and service Cloud to manage sales and support processes. Some of NTOs team are complaining they see new fields on their page unsure of which values need be input. NTO is concerned about lack of governance in making changes to Salesforce.
Which governance measure should a data architect recommend to solve this issue?
- A . Add description fields to explain why the field is used, and mark the field as required.
- B . Create and manage a data dictionary and ups a governance process for changes made to common objects.
- C . Create reports to identify which users are leaving blank, and use external data sources o agreement the missing data.
- D . Create validation rules with error messages to explain why the fields is used
B
Explanation:
To solve the issue of lack of governance in making changes to Salesforce, a data architect should recommend creating and managing a data dictionary and setting up a governance process for changes made to common objects. A data dictionary is a document that defines the metadata, structure, and relationship of each object and field in Salesforce. A governance process is a set of rules and procedures that govern how changes are proposed, reviewed, approved, and deployed in Salesforce. These measures will help NTO to maintain consistency, quality, and clarity of their data model and avoid confusion and errors among users.
Option A is incorrect because adding description fields to explain why the field is used, and marking the field as required will not prevent unauthorized or unnecessary changes to Salesforce.
Option C is incorrect because creating reports to identify which users are leaving blank, and using external data sources to augment the missing data will not address the root cause of the issue, which is the lack of governance in making changes to Salesforce.
Option D is incorrect because creating validation rules with error messages to explain why the fields are used will not stop users from seeing new fields on their page that they are unsure of.
Universal Containers is creating a new B2C service offering for consumers to ship goods across continents. This is in addition to their well-established B2B offering. Their current Salesforce org uses the standard Account object to track B2B customers. They are expecting to have over 50,000,000 consumers over the next five years across their 50 business regions. B2C customers will be individuals. Household data is not required to be stored.
What is the recommended data model for consumer account data to be stored in Salesforce?
- A . Use the Account object with Person Accounts and a new B2C page layout.
- B . Use the Account object with a newly created Record Type for B2C customers.
- C . Create a new picklist value for B2C customers on the Account Type field.
- D . Use 50 umbrella Accounts for each region, with customers as associated Contacts.
A
Explanation:
The recommended data model for consumer account data to be stored in Salesforce is to use the Account object with Person Accounts and a new B2C page layout. Person Accounts are a special type of accounts that allow you to store information about individual consumers who are not associated with a business account2. Person Accounts have the following advantages3:
They allow you to use the same standard objects and features that you use for business accounts, such as contacts, opportunities, cases, etc.
They enable you to create different page layouts and record types for B2C and B2B customers, which allows you to customize the user interface and business logic for each segment.
They support large data volumes and can scale up to 50 million records or more, which meets the expected growth of consumers over the next five years.
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
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.
NTO processes orders from its website via an order management system (OMS). The OMS stores over 2 million historical records and is currently not integrated with SF. The Sales team at NTO using Sales cloud and would like visibility into related customer orders yet they do not want to persist millions of records directly in Salesforce. NTO has asked the data architect to evaluate SF connect and the concept of data verification.
Which 3 considerations are needed prior to a SF Connect implementation? Choose 3 answers:
- A . Create a 2nd system Admin user for authentication to the external source.
- B . Develop an object relationship strategy.
- C . Identify the external tables to sync into external objects
- D . Assess whether the external data source is reachable via an ODATA endpoint.
- E . Configure a middleware tool to poll external table data
B, C, D
Explanation:
The three considerations needed prior to a SF Connect implementation are to develop an object relationship strategy, identify the external tables to sync into external objects, and assess whether the external data source is reachable via an ODATA endpoint. SF Connect is a feature that allows integrating external data sources with Salesforce using external objects. External objects are similar to custom objects, but they store metadata only and not data. They enable on-demand access to external data via standard Salesforce APIs and user interfaces. To implement SF Connect, a data architect needs to consider how the external objects will relate to other objects in Salesforce, which external tables will be exposed as external objects, and whether the external data source supports ODATA protocol for data access.
NTO processes orders from its website via an order management system (OMS). The OMS stores over 2 million historical records and is currently not integrated with SF. The Sales team at NTO using Sales cloud and would like visibility into related customer orders yet they do not want to persist millions of records directly in Salesforce. NTO has asked the data architect to evaluate SF connect and the concept of data verification.
Which 3 considerations are needed prior to a SF Connect implementation? Choose 3 answers:
- A . Create a 2nd system Admin user for authentication to the external source.
- B . Develop an object relationship strategy.
- C . Identify the external tables to sync into external objects
- D . Assess whether the external data source is reachable via an ODATA endpoint.
- E . Configure a middleware tool to poll external table data
B, C, D
Explanation:
The three considerations needed prior to a SF Connect implementation are to develop an object relationship strategy, identify the external tables to sync into external objects, and assess whether the external data source is reachable via an ODATA endpoint. SF Connect is a feature that allows integrating external data sources with Salesforce using external objects. External objects are similar to custom objects, but they store metadata only and not data. They enable on-demand access to external data via standard Salesforce APIs and user interfaces. To implement SF Connect, a data architect needs to consider how the external objects will relate to other objects in Salesforce, which external tables will be exposed as external objects, and whether the external data source supports ODATA protocol for data access.
Marketing solution
What should a data architect recommend that would help upgrade uniquely identify customer across multiple systems:
- A . Store the salesforce id in all the solutions to identify the customer.
- B . Create a custom object that will serve as a cross reference for the customer id.
- C . Create a customer data base and use this id in all systems.
- D . Create a custom field as external id to maintain the customer Id from the MDM solution.
D
Explanation:
To help uniquely identify customer across multiple systems, a data architect should recommend creating a custom field as external ID to maintain the customer ID from the MDM solution. An external ID is a custom field that has the “External ID” attribute enabled, which means that it contains unique record identifiers from a system outside of Salesforce. By using the customer ID from the MDM solution as an external ID in Salesforce CRM, Contract Management system, and Marketing solution, the data architect can ensure that each customer can be easily identified and integrated across these systems.
Option A is incorrect because storing the Salesforce ID in all the solutions to identify the customer will not work if the customer records are created or updated in other systems besides Salesforce CRM.
Option B is incorrect because creating a custom object that will serve as a cross reference for the customer ID will require additional configuration effort and may not be consistent with the actual customer records in each system.
Option C is incorrect because creating a customer database and using this ID in all systems will require additional infrastructure cost and maintenance effort.
Universal Containers has deployed Salesforce for case management The company is having difficulty understanding what percentage of cases are resolved from the initial call to their support organization.
What first step is recommended to implement a reporting solution to measure the support reps case closure rates?
- A . Enable field history tracking on the Case object.
- B . Create a report on Case analytic snapshots.
- C . Install AppExchange packages for available reports.
- D . Create Contact and Opportunity Reports and Dashboards.
A
Explanation:
Enabling field history tracking on the Case object is the first step to implement a reporting solution to measure the support reps case closure rates. Field history tracking allows you to track changes to certain fields on the Case object, such as Status, Owner, or Priority. You can then create reports based on the field history data to analyze how long it took to close a case, how many times the case owner changed, or how many cases were escalated.