Salesforce DATA-ARCHITECT Online Practice Questions and Exam Preparation

Salesforce DATA-ARCHITECT Online Questions & Answers

• Question 101:

  A customer wishes to migrate 700,000 Account records in a single migration into Salesforce.

  What is the recommended solution to migrate these records while minimizing migration time?

  A. Use Salesforce Soap API in parallel mode.
  B. Use Salesforce Bulk API in serial mode.
  C. Use Salesforce Bulk API in parallel mode.
  D. Use Salesforce Soap API in serial mode.
  C. Use Salesforce Bulk API in parallel mode.

  ---

  Explanation

  Using Salesforce Bulk API in parallel mode can reduce the migration time by processing multiple batches of records simultaneously and leveraging the server resources more efficiently. The Bulk API is designed for loading large amounts of data into Salesforce

• Question 102:

  NTO has decided that it is going to build a channel sales portal with the following requirements:

  1.External resellers are able to authenticate to the portal with a login.

  2.Lead data, opportunity data and order data are available to authenticated users.

  3.Authenticated users many need to run reports and dashboards.

  4.There is no need for more than 10 custom objects or additional file storage.

  Which community cloud license type should a data architect recommend to meet the portal requirements?

  A. Customer community.
  B. Lightning external apps starter.
  C. Customer community plus.
  D. Partner community.
  D. Partner community.

  ---

  Explanation

  Partner community license type is the best option for building a channel sales portal, as it allows external resellers to access lead, opportunity, and order data, as well as run reports and dashboards. Customer community and customer community plus license types are more suitable for customer service portals, while lightning external apps starter license type does not support reports and dashboards

• Question 103:

  Universal Containers (UC) has a very large and complex Salesforce org with hundreds of validation rules and triggers. The triggers are responsible for system updates and data manipulation as records are created or updates by users. A majority of the automation tool within UC'' org were not designed to run during a data load. UC is importing 100,000 records into Salesforce across several objects over the weekend.

  What should a data architect do to mitigate any unwanted results during the import?

  A. Ensure validation rules, triggers and other automation tools are disabled.
  B. Ensure duplication and matching rules and defined.
  C. Import the data in smaller batches over a 24-hour period.
  D. Bulkily the trigger to handle import leads.
  A. Ensure validation rules, triggers and other automation tools are disabled.

  ---

  Explanation

  Ensuring validation rules, triggers and other automation tools are disabled is the best way to mitigate any unwanted results during the import, as it prevents any errors or conflicts that may occur due to the existing logic. Ensuring duplication and matching rules are defined may not be sufficient or relevant for preventing unwanted results. Importing the data in smaller batches over a 24-hour period may not be necessary or efficient. Bulkifying the trigger to handle import leads may not be possible or desirable if the triggers were not designed to run during a data load.

• Question 104:

  Based on government regulations, a Salesforce customer plans to implement the following in Salesforce for compliance:

  1. Access to customer information based on record ownership

  2. Ability for customers to request removal of their information from Salesforce

  3. Prevent users from accessing Salesforce from outside company network (virtual private network, or VPN)

  What should a data architect recommend to address these requirements?

  A. Contact Salesforce support to restrict access only with VPN and other requirements
  B. Allow users access to Salesforce through a custom web application hosted within VPN.
  C. Implement IP restrictions, sharing settings, and custom Apex to support customer requests.
  D. Implement Salesforce shield with Event Monitoring to address the requirement.
  C. Implement IP restrictions, sharing settings, and custom Apex to support customer requests.

  ---

  Explanation

  IP restrictions can be used to prevent users from accessing Salesforce from outside the company network or VPN. According to this article, sharing settings can be used to control access to customer information based on record ownership.

  According to this article, custom Apex can be used to support customer requests for removal of their information from Salesforce.

• Question 105:

  NTO has outgrown its current salesforce org and will be migrating to new org shortly. As part of this process NTO will be migrating all of its metadata and data. NTO's data model in the source org has a complex relationship hierarchy with several master detail and lookup relationships across objects, which should be maintained in target org.

  What 3 things should a data architect do to maintain the relationship hierarchy during migration?

  Choose 3 answers:

  A. Use data loader to export the data from source org and then import or Upsert into the target org in sequential order.
  B. Create a external id field for each object in the target org and map source record ID's to this field.
  C. Redefine the master detail relationship fields to lookup relationship fields in the target org.
  D. Replace source record ID's with new record ID's from the target org in the import file.
  E. Keep the relationship fields populated with the source record ID's in the import file.
  A. Use data loader to export the data from source org and then import or Upsert into the target org in sequential order.
  B. Create a external id field for each object in the target org and map source record ID's to this field.
  D. Replace source record ID's with new record ID's from the target org in the import file.

  ---

  Explanation

  The correct answer is A, B, and D. To maintain the relationship hierarchy during migration, a data architect should use data loader to export the data from source org and then import or upsert into the target org in sequential order, create an external ID field for each object in the target org and map source record IDs to this field, and replace source record IDs with new record IDs from the target org in the import file. These steps will ensure that the records are linked correctly and the relationships are preserved. Option C is incorrect because redefining the master detail relationship fields to lookup relationship fields in the target org will change the behavior and security of the data model. Option E is incorrect because keeping the relationship fields populated with the source record IDs in the import file will cause errors and prevent the records from being imported.

• Question 106:

  Universal Containers (UC) has a multi-level master-detail relationship for opportunities, a custom opportunity line item object, and a custom discount request. UC has opportunity as master and custom line item object as detail in master-detail relationship. UC also has a custom line item object as master and a custom discount request object as detail in another master-detail relationship. UC has a requirement to show all sums of discounts across line items at an opportunity level.

  What is the recommended solution to address these requirements?

  A. Use roll-up for the line-item-level summary and a trigger for the opportunity amount summary, as only one level roll-up is allowed.
  B. Update the master-detail relationships to lookup relationships in order to allow the discount amount to roll up.
  C. Remove the master-detail relationships and rely completely on workflow/triggers to summarize the discount amount.
  D. Roll-up discount request amount at the line-item-level and line-item-level summary discount at the opportunity level.
  D. Roll-up discount request amount at the line-item-level and line-item-level summary discount at the opportunity level.

  ---

  Explanation

  The recommended solution to address the requirements of Universal Containers (UC) is to roll-up discount request amount at the line-item-level and line-item- level summary discount at the opportunity level. This solution would allow UC to show all sums of discounts across line items at an opportunity level using standard roll-up summary fields. Since UC has a multi-level master-detail relationship for opportunities, a custom opportunity line item object, and a custom discount

  request object, they can use two levels of roll-up summary fields to aggregate the discount amounts from the child objects to the parent objects. For example, they can create a roll-up summary field on the custom line item object to sum up the discount request amounts from the custom discount request object. Then, they can create another roll-up summary field on the opportunity object to sum up the line-item-level summary discounts from the custom line item object.

• Question 107:

  Ursa Major Solar's legacy system has a quarterly accounts receivable report that compiles data from the following:

  Accounts

  Contacts

  Opportunities

  Orders

  Order Line Items

  Which issue will an architect have when implemented this in Salesforce?

  A. Custom report types CANNOT contain Opportunity data.
  B. Salesforce does NOT support Orders or Order Line Items.
  C. Salesforce does NOT allow more than four objects in a single report type.
  D. A report CANNOT contain data from Accounts and Contacts.
  C. Salesforce does NOT allow more than four objects in a single report type.

  ---

  Explanation

  The issue that an architect will have when implementing the quarterly accounts receivable report in Salesforce is that Salesforce does not allow more than four objects in a single report type. A report type defines the set of records and fields available to a report based on the relationships between a primary object and up to four related objects. A report type has the following limitations: It cannot include more than four objects in a single report type, which means that the report cannot compile data from five objects (Accounts, Contacts, Opportunities, Orders, and Order Line Items) at once. It cannot include objects that are more than two relationships away from each other, which means that the report cannot access fields from Order Line Items through Opportunities and Orders.

  It cannot include objects that have a many-to-many relationship with each other, which means that the report cannot access fields from Contacts and Opportunities through the junction object Opportunity Contact Role.

• Question 108:

  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.
  A. Implement shield platform encryption to encrypt files.

  ---

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

  UC has migrated its Back-office data into an on-premise database with REST API access. UC recently implemented Sales cloud for its sales organization. But users are complaining about a lack of order data inside SF.

  UC is concerned about SF storage limits but would still like Sales cloud to have access to the data.

  Which design patterns should a data architect select to satisfy the requirement?

  A. Migrate and persist the data in SF to take advantage of native functionality.
  B. Use SF Connect to virtualize the data in SF and avoid storage limits.
  C. Develop a bidirectional integration between the on-premise system and Salesforce.
  D. Build a UI for the on-premise system and iframe it in Salesforce
  B. Use SF Connect to virtualize the data in SF and avoid storage limits.

  ---

  Explanation

  The best design pattern to satisfy the requirement of accessing order data from an on- premise database with REST API access without consuming SF storage limits is to use SF Connect to virtualize the data in SF and avoid storage limits.

  SF Connect is an integration tool that allows users to access and integrate data from external sources using external objects. External objects are similar to custom objects, except that the data resides in another system and is accessed in real time via web service callouts. SF Connect supports various adapters to connect to different types of external data sources, such as OData, cross-org, or Apex custom adapter11. Migrate and persist the data in SF to take advantage of native functionality is not a good option because it would consume SF storage limits and require data synchronization between systems. Develop a bidirectional integration between the on-premise system and Salesforce is not a good option because it would be complex and costly to implement and maintain, and it would also consume SF storage limits. Build a UI for the on-premise system and iframe it in Salesforce is not a good option because it would not provide a seamless user experience and it would not allow users to search, report, or perform actions on the external data.

• Question 110:

  Universal Containers (UC) is going thought major reorganization of their sales team. This would require changes to a large a number of group members and sharing rules. UCs administrator is concerned about long processing time and failure during the process.

  What should a Data architect implement to make changes efficiently?

  A. Log a case with salesforce to make sharing rule changes.
  B. Enable Defer Sharing Calculation prior to making sharing rule changes.
  C. Delete old sharing rules and build new sharing rules
  D. Log out all users and make changes to sharing rules.
  B. Enable Defer Sharing Calculation prior to making sharing rule changes.

  ---

  Explanation

  The correct answer is B. To make changes efficiently, a data architect should enable Defer Sharing Calculation prior to making sharing rule changes. This will allow the administrator to make multiple changes to sharing rules without recalculating them after each change, which can take a long time and cause failures. The sharing rules can be recalculated later when there are fewer users online or during off-peak hours. Option A is incorrect because logging a case with salesforce to make sharing rule changes will not speed up the process or prevent failures. Option C is incorrect because deleting old sharing rules and building new sharing rules will not reduce the processing time or failure rate. Option D is incorrect because logging out all users and making changes to sharing rules will disrupt the business operations and may not be feasible.