Salesforce Salesforce Certifications DATA-ARCHITECT Questions & Answers

• Question 1:

  UC is migrating individual customers (B2C) data from legacy systems to SF. There are millions of customers stored as accounts and contacts in legacy database.

  Which object model should a data architect configure within SF?

  A. Leverage person account object in Salesforce

  B. Leverage custom person account object in SF

  C. Leverage custom account and contact object in SF

  D. Leverage standard account and contact object in SF

  Correct Answer: A

  The best object model to configure within SF for migrating individual customers (B2C) data from legacy systems is to leverage person account object in Salesforce. Person accounts are a special type of accounts that store information about individual people by combining certain account and contact fields into a single record4. Person accounts are useful for B2C scenarios where there is no need to associate a company name with a contact. Person accounts also support standard Salesforce features and functionality, such as leads, campaigns, reports, dashboards, etc5. Leverage custom person account object in SF is not a good option because there is no such thing as a custom person account object. Leverage custom account and contact object in SF is not a good option because it would require creating and maintaining additional objects and fields that may not be necessary or compatible with standard Salesforce features. Leverage standard account and contact object in SF is not a good option because it would require filling in dummy values for the account name field, which is mandatory for standard accounts.

• Question 2:

  UC is implementing sales cloud for patient management and would like to encrypt sensitive patient records being stored in files.

  Which solution should a data architect recommend to solve this requirement?

  A. Implement shield platform encryption to encrypt files.

  B. Use classic encryption to encrypt files.

  C. Implement 3rd party App Exchange app to encrypt files.

  D. Store files outside of salesforce and access them to real time.

  Correct Answer: A

  Explanation: Shield platform encryption is the recommended solution for encrypting sensitive patient records stored in files, as it provides encryption at rest for files and attachments, as well as standard and custom fields. Classic encryption only supports text fields with a maximum length of 175 characters, and does not encrypt files. Third-party App Exchange apps may not provide the same level of security and compliance as shield platform encryption. Storing files outside of salesforce may introduce additional complexity and latency

• Question 3:

  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.

  Correct Answer: BC

  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 4:

  UC is building a salesforce application to track contacts and their respective conferences that they have attended with the following requirements:

  1.Contacts will be stored in the standard contact object.

  2.Conferences will be stored in a custom conference_ c object.

  3.Each contact may attend multiple conferences and each conference may be related to multiple contacts.

  How should a data architect model the relationship between the contact and conference objects?

  A. Implement a Contact Conference junction object with master detail relationship to both contact and conference_c

  B. Create a master detail relationship field on the Contact object.

  C. Create a master detail relationship field on the Conference object.

  D. Create a lookup relationship field on contact object.

  Correct Answer: A

  Explanation: Implementing a Contact Conference junction object with master detail relationship to both contact and conference_c is the correct way to model the relationship between the contact and conference objects, as it allows a many-tomany relationship between them. This means that each contact can attend multiple conferences, and each conference can be related to multiple contacts. Creating a master detail relationship field on either the contact or the conference object would create a one-to-many relationship, which does not meet the requirements. Creating a lookup relationship field on contact object would also create a one-to-many relationship, and would not enforce referential integrity.

• Question 5:

  Universal Containers (UC) is planning to move away from legacy CRM to Salesforce. As part of one-time data migration, UC will need to keep the original date when a contact was created in the legacy system. How should an Architect design the data migration solution to meet this requirement?

  A. After the data is migrated, perform an update on all records to set the original date in a standard Created Date field.

  B. Create a new field on the Contact object to capture the Created Date. Hide the standard Created Date field using Field -Level Security.

  C. Enable "Set Audit Fields" and assign the permission to the user loading the data for the duration of the migration.

  D. Write an Apex trigger on the Contact object, before insert event to set the original value in a standard Created Date field.

  Correct Answer: C

  Explanation: Enabling "Set Audit Fields" allows the user loading the data to set the value of the standard CreatedDate field to match the original date from the legacy system. This is a one-time permission that can be revoked after the migration is completed. The other options would either not work or require additional customization

• Question 6:

  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?

  A. Write an Apex class that makes a REST callout to the external API.

  B. Develop a process that calls an inviable web service method.

  C. Migrate the data to Heroku and register Postgres as a data source.

  D. Write a custom adapter with the Apex Connector Framework.

  Correct 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 7:

  Northern Trail Outfitters (NTO) has implemented Salesforce for its sales users. The opportunity management in Saiesforce 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 the Opportunity Amount field on opportunities on a daily basis.

  3.

  PPS is the trusted source within 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 overwriting issue?

  A. Create a custom field for Opportunity amount that PSS updates separating the field sales user updates.

  B. Change PSS integration to update only Opportunity Amount field when the value is null.

  C. Change Opportunity Amount field access to Read Only for sales users field-level security.

  D. Create a custom field for Opportunity amount that sales users update separating the field that PPS updates.

  Correct Answer: C

  Explanation: Changing Opportunity Amount field access to Read Only for sales users field-level security (option C) is the best way to address the overwriting issue, as it prevents sales users from updating the field that is controlled by PPS, and ensures data consistency and accuracy. Creating a custom field for Opportunity amount that PSS updates separating the field sales user updates (option A) or creating a custom field for Opportunity amount that sales users update separating the field that PPS updates (option D) are not good solutions, as they may create confusion and inconsistency with the Opportunity Forecast feature. Changing PSS integration to update only Opportunity Amount field when the value is null (option B) is also not a good solution, as it may cause data loss or conflicts with the sales users' inputs.

• Question 8:

  Universal Containers (UC) requires 2 years of customer related cases to be available on SF for operational reporting. Any cases older than 2 years and upto 7 years need to be available on demand to the Service agents. UC creates 5 million cases per yr.

  Which 2 data archiving strategies should a data architect recommend? Choose 2 options:

  A. Use custom objects for cases older than 2 years and use nightly batch to move them.

  B. Sync cases older than 2 years to an external database, and provide access to Service agents to the database

  C. Use Big objects for cases older than 2 years, and use nightly batch to move them.

  D. Use Heroku and external objects to display cases older than 2 years and bulk API to hard delete from Salesforce.

  Correct Answer: CD

  Explanation: The best data archiving strategies for UC are to use Big objects and Heroku with external objects. Big objects allow storing large amounts of data on the Salesforce platform without affecting performance or storage limits. They also support point-and-click tools, triggers, and Apex code. Heroku is a cloud platform that can host external databases and integrate with Salesforce using external objects. External objects enable on-demand access to external data sources via standard Salesforce APIs and user interfaces. Using bulk API to hard delete cases from Salesforce will free up storage space and improve performance.

• Question 9:

  Universal Containers (UC) has an open sharing model for its Salesforce users to allow all its Salesforce internal users to edit all contacts, regardless of who owns the contact. However, UC management wants to allow only the owner of a contact record to delete that contact. If a user does not own the contact, then the user should not be allowed to delete the record. How should the architect approach the project so that the requirements are met?

  A. Create a "before delete" trigger to check if the current user is not the owner.

  B. Set the Sharing settings as Public Read Only for the Contact object.

  C. Set the profile of the users to remove delete permission from the Contact object.

  D. Create a validation rule on the Contact object to check if the current user is not the owner.

  Correct Answer: A

  Explanation: To allow only the owner of a contact record to delete that contact, the data architect should create a "before delete" trigger to check if the current user is not the owner. The trigger can use the UserInfo.getUserId() method to get the current user's ID and compare it with the OwnerId field of the contact record. If they are not equal, the trigger can add an error to the record and prevent it from being deleted. The other options are not suitable for meeting the requirements, as they would either restrict the edit access or delete access for all users, regardless of ownership.

• Question 10:

  A large automobile manufacturer has decided to use Salesforce as its CRM. It needs to maintain the following dealer types in their CRM:

  Local dealers Regional distributor State distributor 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.

  Correct Answer: A

  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.