Salesforce DATA-ARCHITECT Online Practice Questions and Exam Preparation

Salesforce DATA-ARCHITECT Online Questions & Answers

• Question 241:

  NTO has 1 million customer records spanning 25 years. As part of its new SF project, NTO would like to create a master data management strategy to help preserve the history and relevance of its customer data.

  Which 3 activities will be required to identify a successful master data management strategy? Choose 3 answers:

  A. Identify data to be replicated
  B. Create a data archive strategy
  C. Define the systems of record for critical data
  D. Install a data warehouse
  E. Choose a Business Intelligence tool.
  A. Identify data to be replicated
  B. Create a data archive strategy
  C. Define the systems of record for critical data

  ---

  Explanation

  The three activities that will be required to identify a successful master data management strategy are: Identify data to be replicated: This activity involves determining which data elements need to be copied from one system to another, and how frequently the replication should occur. This can help ensure data consistency and availability across systems.

  Create a data archive strategy: This activity involves defining how historical data will be stored, accessed, and deleted over time. This can help optimize data storage, performance, and compliance.

  Define the systems of record for critical data: This activity involves identifying which system owns and maintains the authoritative version of each data element. This can help avoid data conflicts and duplication across systems67. Install a data warehouse is not a required activity, but rather a possible option for consolidating data from multiple sources for analytics purposes. Choose a Business Intelligence tool is not a required activity, but rather a possible option for visualizing and reporting on data from various sources.

• Question 242:

  DreamHouse Realty has a data model as shown in the image. The Project object has a private sharing model, and it has Roll-Up summary fields to calculate the number of resources assigned to the project, total hours for the project, and the number of work items associated to the project.

  There will be a large amount of time entry records to be loaded regularly from an external system into Salesforce.

  

  What should the Architect consider in this situation?

  A. Load all data after deferring sharing calculations.
  B. Calculate summary values instead of Roll-Up by using workflow.
  C. Calculate summary values instead of Roll-Up by using triggers.
  D. Load all data using external IDs to link to parent records.
  A. Load all data after deferring sharing calculations.

  ---

  Explanation

  According to the exam guide, one of the objectives is to "describe the use cases and considerations for deferring sharing calculations"1. This implies that option A is the correct way to load large amounts of data into Salesforce without affecting performance and data integrity. Deferring sharing calculations allows the data to be loaded first and then the sharing rules to be applied later2. Option B is not correct because workflows are not recommended for calculating summary values, as they can cause performance issues and data skew3. Option C is not correct because triggers are also not recommended for calculating summary values, as they can cause governor limit errors and data inconsistency. Option D is not correct because external IDs are used to link records from different systems, not to improve data loading performance.

• Question 243:

  Universal Containers (UC) has a requirement to create an Account plan object that is related to the Account object. Each Account plan needs to have an Account object, but the accessibility requirement of the Account plan is different from the Account object.

  What should an Architect recommend?

  A. Create a custom account plan object as detail with Account as mater in a master-detail relationship.
  B. Create a custom account plan object as detail with Account as master with additional sharing rules to allow access.
  C. Create an account plan object with a lookup relations to Account without any validation rules to enforce the Account association.
  D. Create an account plan object with a lookup relationship to Account with validation rules to enforce the Account association.
  D. Create an account plan object with a lookup relationship to Account with validation rules to enforce the Account association.

  ---

  Explanation

  Creating an account plan object with a lookup relationship to Account with validation rules to enforce the Account association can help UC meet their requirement. A lookup relationship allows different accessibility requirements for the account plan object and the account object, as well as different ownership and sharing settings. A validation rule can ensure that each account plan has an account associated with it.

• Question 244:

  Northern Trail Outfitters (NTO) wants to capture a list of customers that have bought a particular product. The solution architect has recommended to create a custom object for product, and to create a lookup relationship between its customers and its products.

  Products will be modeled as a custom object (NTO_ Product__ c) and customers are modeled as person accounts. Every NTO product may have millions of customers looking up a single product, resulting in a lookup skew.

  What should a data architect suggest to mitigate Issues related to lookup skew?

  A. Create multiple similar products and distribute the skew across those products.
  B. Change the lookup relationship to master-detail relationship.
  C. Create a custom object to maintain the relationship between products and customers.
  D. Select Clear the value of this field option while configuring the lookup relationship.
  A. Create multiple similar products and distribute the skew across those products.

  ---

  Explanation

  creating multiple similar products and distributing the skew across those products can be a way to mitigate issues related to lookup skew. The article explains that lookup skew happens when a very large number of records are associated with a single record in the lookup object, and this can cause record locking and performance issues. The article suggests creating multiple copies of the same product record and assigning different child records to each copy, so that the number of child records per parent record is reduced.

• Question 245:

  Universal Containers (UC) is transitioning from Classic to Lightning Experience.

  What does UC need to do to ensure users have access to its notices and attachments in Lightning Experience?

  A. Add Notes and Attachments Related List to page Layout in Lighting Experience.
  B. Manually upload Notes in Lighting Experience.
  C. Migrate Notes and Attachment to Enhanced Notes and Files a migration tool
  D. Manually upload Attachments in Lighting Experience.
  C. Migrate Notes and Attachment to Enhanced Notes and Files a migration tool

  ---

  Explanation

  The correct answer is C, migrate Notes and Attachment to Enhanced Notes and Files using a migration tool. Enhanced Notes and Files are the new features in Lightning Experience that replace the classic Notes and Attachments. They offer more functionality and security than the classic version. To access them in Lightning Experience, you need to migrate your existing Notes and Attachments using a migration tool provided by Salesforce. Adding Notes and Attachments Related List, manually uploading Notes or Attachments, or doing nothing are not valid solutions, as they will not enable you to use the enhanced features in Lightning Experience.

• Question 246:

  UC has a legacy client server app that as a relational data base that needs to be migrated to salesforce.

  What are the 3 key actions that should be done when data modeling in salesforce?

  Choose 3 answers:

  A. Identify data elements to be persisted in salesforce.
  B. Map legacy data to salesforce objects.
  C. Map legacy data to salesforce custom objects.
  D. Work with legacy application owner to analysis legacy data model.
  E. Implement legacy data model within salesforce using custom fields.
  A. Identify data elements to be persisted in salesforce.
  B. Map legacy data to salesforce objects.
  E. Implement legacy data model within salesforce using custom fields.

  ---

  Explanation

  According to the Data Modeling unit on Trailhead, some of the key actions that should be done when data modeling in Salesforce are identifying data elements, mapping legacy data, and implementing legacy data model. The unit states that "Before you start creating objects and fields in Salesforce, you need to identify the data elements that you want to store and work with. ... Next, you need to map your legacy data to Salesforce objects and fields. ... Finally, you need to implement your data model in Salesforce by creating custom objects and fields using declarative tools or Metadata API." Therefore, these are the correct actions for migrating a legacy client server app to Salesforce.

• Question 247:

  A customer is facing locking issued when importing large data volumes of order records that are children in a master-detail relationship with the Account object.

  What is the recommended way to avoid locking issues during import?

  A. Import Account records first followed by order records after sorting order by OrderID.
  B. Import Account records first followed by order records after sorting orders by AccountID.
  C. Change the relationship to Lookup and update the relationship to master-detail after import.
  D. Import Order records and Account records separately and populate AccountID in orders using batch Apex.
  B. Import Account records first followed by order records after sorting orders by AccountID.

  ---

  Explanation

  Importing Account records first followed by order records after sorting orders by AccountID is the recommended way to avoid locking issues during import. This can reduce the number of lock contention errors by minimizing the number of parent records that are concurrently processed by multiple batches. Sorting orders by AccountID can also group the child records by their parent records and avoid updating the same parent record in different batches3. Importing Account records first followed by order records after sorting order by OrderID will not help with avoiding locking issues because it does not group the child records by their parent records. Changing the relationship to Lookup and updating the relationship to master-detail after import will not work because changing a relationship from Lookup to master-detail requires that all child records have a parent record, which may not be the case after import. Importing Order records and Account records separately and populating AccountID in orders using batch Apex will not help with avoiding locking issues because it still requires updating the parent records in batches.

• Question 248:

  Cloud Kicks has the following requirements:

  Data needs to be sent from Salesforce to an external system to generate invoices from their Order Management System (OMS).

  A Salesforce administrator must be able to customize which fields will be sent to the external system without changing code.

  What are two approaches for fulfilling these requirements? (Choose two.)

  A. A set<sobjectFieldset> to determine which fields to send in an HTTP callout.
  B. An Outbound Message to determine which fields to send to the OMS.
  C. A Field Set that determines which fields to send in an HTTP callout.
  D. Enable the field -level security permissions for the fields to send.
  B. An Outbound Message to determine which fields to send to the OMS.
  C. A Field Set that determines which fields to send in an HTTP callout.

  ---

  Explanation

  An Outbound Message is a native Salesforce feature that allows sending data to an external system without code. It can be configured to include any fields from the source object3. A Field Set is a collection of fields that can be used in Visualforce pages or Apex classes to dynamically determine the fields to send in an HTTP callout. Both of these approaches meet the requirements of Cloud Kicks.

• Question 249:

  Universal Containers (UC) uses the following Salesforce products:

  Sales Cloud for customer management.

  Marketing Cloud for marketing.

  Einstein Analytics for business reporting.

  UC occasionally gets a list of prospects from third-party source as comma-separated values (CSV) files for marketing purposes. Historically, UC would load contact Lead object in Salesforce and sync to Marketing Cloud to send marketing communications. The number of records in the Lead object has grown over time and has been consuming large amounts of storage in Sales Cloud, UC is looking for recommendations to reduce the storage and advice on how to optimize the marketing Cloud to send marketing communications. The number of records in the Lead object has grown over time and has been consuming large amounts of storage in Sales Cloud, UC is looking for recommendations to reduce the storage and advice on how to optimize the marketing process.

  What should a data architect recommend to UC in order to immediately avoid storage issues in the future?

  A. Load the CSV files in Einstein Analytics and sync with Marketing Cloud prior to sending marketing communications;
  B. Load the CSV files in an external database and sync with Marketing Cloud prior to sending marketing communications.
  C. Load the contacts directly to Marketing Cloud and have a reconciliation process to track prospects that are converted to customers.
  D. Continue to use the existing process to use Lead object to sync with Marketing Cloud and delete Lead records from Sales after the sync is complete.
  C. Load the contacts directly to Marketing Cloud and have a reconciliation process to track prospects that are converted to customers.

  ---

  Explanation

  According to the Salesforce documentation4, Marketing Cloud is a platform that allows creating and managing marketing campaigns across multiple channels, such as email, mobile, social media, web, etc. Marketing Cloud can integrate with Sales Cloud and other Salesforce products to share data and insights. One of the ways to integrate Marketing Cloud with Sales Cloud is using Marketing Cloud Connect5, which allows syncing data between the two platforms using synchronized data sources. However, if UC occasionally gets a list of prospects from third-party sources as CSV files for marketing purposes, it may not be necessary or efficient to load them into Sales Cloud first and then sync them with Marketing Cloud. This can consume large amounts of storage in Sales Cloud, which has a limit based on the license type6. It can also cause data quality issues, such as duplicates or outdated information. A better option for UC is to load the contacts directly to Marketing Cloud using Import Definition, which allows importing data from external files or databases into Marketing Cloud data extensions. Data extensions are custom tables that store marketing data in Marketing Cloud.

  This way, UC can avoid storage issues in Sales Cloud and optimize the marketing process by sending marketing communications directly from Marketing Cloud. To track prospects that are converted to customers, UC can have a reconciliation process that compares the contacts in Marketing Cloud with the accounts or contacts in Sales Cloud. This can be done using SQL queries or API calls to access and compare data from both platforms. Alternatively, UC can use Marketing Cloud Connect to sync the converted contacts from Sales Cloud to Marketing Cloud using synchronized data sources. Loading the CSV files in Einstein Analytics and syncing with Marketing Cloud prior to sending marketing communications (option A) is not a good option, as it can add unnecessary complexity and latency to the process. Einstein Analytics is a platform that allows creating and analyzing data using interactive dashboards and reports. It is not designed for importing and exporting data for marketing purposes. Loading the CSV files in an external database and syncing with Marketing Cloud prior to sending marketing communications (option B) is also not a good option, as it can incur additional costs and maintenance for the external database. It can also introduce data security and privacy risks, as the data may not be encrypted or protected by Salesforce. Continuing to use the existing process to use Lead object to sync with Marketing Cloud and delete Lead records from Sales after the sync is complete (option D) is not a good option, as it can cause performance issues and data loss. Deleting Lead records from Sales can affect reporting and auditing, as well as trigger workflows and validations that may not be intended. It can also cause data inconsistency and synchronization errors between Sales Cloud and Marketing Cloud.

• Question 250:

  How can an architect find information about who is creating, changing, or deleting certain fields within the past two months?

  A. Remove "customize application" permissions from everyone else.
  B. Export the metadata and search it for the fields in question.
  C. Create a field history report for the fields in question.
  D. Export the setup audit trail and find the fields in question.
  D. Export the setup audit trail and find the fields in question.

  ---

  Explanation

  The setup audit trail tracks changes made in your org's setup area for the past 180 days1. You can export the setup audit trail and find the fields in question by filtering by action type, user, or date2.