Salesforce DATA-ARCHITECT Online Practice Questions and Exam Preparation

Salesforce DATA-ARCHITECT Online Questions & Answers

• Question 11:

  Universal Containers is exporting 40 million Account records from Salesforce using Informatica Cloud. The ETL tool fails and the query log indicates a full table scan time-out failure.

  What is the recommended solution?

  A. Modify the export job header to specify Export-in-Parallel.
  B. Modify the export job header to specify Sforce-Enable-PKChunking.
  C. Modify the export query that includes standard index fields(s).
  D. Modify the export query with LIMIT clause with Batch size 10,000.
  B. Modify the export job header to specify Sforce-Enable-PKChunking.

  ---

  Explanation

  The Sforce-Enable-PKChunking header enables you to extract large data sets from Salesforce by using a technique called primary key (PK) chunking. PK chunking splits your query into multiple queries based on the record IDs of the queried object. This reduces the query time and avoids the query timeout issues that can occur with large data volumes

• Question 12:

  UC is having issues using Informatica Cloud Louder to export +10MOrder records. Each Order record has 10 Order Line Items. What two steps can you take to help correct this? Choose two answers.

  A. Export in multiple batches
  B. Export Bulk API in parallel mode
  C. Use PK Chunking
  D. Limit Batch to 10K records
  A. Export in multiple batches
  C. Use PK Chunking

  ---

  Explanation

  Exporting in multiple batches and using PK Chunking are two steps that can help correct the issues with exporting large volumes of Order records using Informatica Cloud Loader. Exporting in multiple batches can reduce the load on the system and avoid timeouts or errors. Using PK Chunking can split a large data set into smaller chunks based on the record IDs and enable parallel processing of each chunk.

• Question 13:

  Universal Containers has provided a web order form for its customer and has noticed invalid data coming in on orders.

  What should be used to mitigate this problem?

  A. Work Flow Rules
  B. Formatted Fields
  C. Apex Trigger
  D. Validation Rules
  D. Validation Rules

  ---

  Explanation

  Using validation rules to mitigate this problem is the best option. Validation rules can help you prevent invalid data from being entered in your web order form. You can use validation rules to check for data quality, format, range, or consistency. For example, you can use validation rules to ensure that the order quantity is positive, the product code is valid, or the shipping address is complete.

• Question 14:

  Universal Containers would like to remove data silos and connect their legacy CRM together with their ERP and with Salesforce. Most of their sales team has already migrated to Salesforce for daily use, although a few users are still on the old CRM until some functionality they require is completed.

  Which two techniques should be used for smooth interoperability now and in the future?

  A. Replicate ongoing changes in the legacy CRM to Salesforce to facilitate a smooth transition when the legacy CRM is eventually retired.
  B. Specify the legacy CRM as the system of record during transition until it is removed from operation and fully replaced by Salesforce.
  C. Work with stakeholders to establish a Master Data Management plan for the system of record for specific objects, records, and fields.
  D. Do not connect Salesforce and the legacy CRM to each other during this transition period, but do allow both to interact with the ERP.
  B. Specify the legacy CRM as the system of record during transition until it is removed from operation and fully replaced by Salesforce.
  C. Work with stakeholders to establish a Master Data Management plan for the system of record for specific objects, records, and fields.

  ---

  Explanation

  Specify the legacy CRM as the system of record during transition until it is removed from operation and fully replaced by Salesforce. This is a good technique to ensure data consistency and avoid conflicts between the two systems. Work with stakeholders to establish a Master Data Management plan for the system of record for specific objects, records, and fields. This is another good technique to define the data governance and stewardship policies and processes for managing data quality and integrity across multiple systems

• Question 15:

  Universal Containers (UC) loads bulk leads and campaigns from third-party lead aggregators on a weekly and monthly basis. The expected lead record volume is 500K records per week, and the expected campaign records volume is 10K campaigns per week. After the upload, Lead records are shared with various sales agents via sharing rules and added as Campaign members via Apex triggers on Lead creation. UC agents work on leads for 6 months, but want to keep the records in the system for at least 1 year for reference. Compliance requires them to be stored for a minimum of 3 years. After that, data can be deleted.

  What statement is true with respect to a data archiving strategy for UC?

  A. UC can store long-term lead records in custom storage objects to avoid counting against storage limits.
  B. UC can leverage the Salesforce Data Backup and Recovery feature for data archival needs.
  C. UC can leverage recycle bin capability, which guarantees record storage for 15 days after deletion.
  D. UC can leverage a "tier"-based approach to classify the record storage need.
  D. UC can leverage a "tier"-based approach to classify the record storage need.

  ---

  Explanation

  Leveraging a "tier"-based approach to classify the record storage need is a true statement with respect to a data archiving strategy for UC. This approach involves defining different tiers of data based on their usage, value, and retention policies, and then applying appropriate storage and archiving solutions for each tier.

• Question 16:

  An Architect needs information about who is creating, changing, or deleting certain fields within the past four months.

  How can the Architect access this information?

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

  ---

  Explanation

  Exporting the setup audit trail can provide information about who is creating, changing, or deleting certain fields within the past four months. The setup audit trail tracks the recent setup changes that administrators and other users have made to the organization. The setup audit trail history shows up to 20 most recent changes in the Setup area, but administrators can download a report (in CSV format) of up to six months of setup history.

• Question 17:

  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. Set a standard profile for Data Migration user, and assign view encrypted data

  ---

  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

• Question 18:

  Universal Containers (UC) is migrating data from legacy system to Salesforce. During data analysis it was discovered that data types of fields being migrated do not match with Salesforce data types.

  Which solution should a data architect use to ensure successful data migrations?

  A. Migrate legacy data to a staging database for mapping then leverage an ETL tool to transform the data and load into Salesforce.
  B. Export legacy data into the staging database and leverage stored procedures to transform data types before loading into Salesforce.
  C. Migrate the legacy data leveraging an ETL tool to transform data types and load data into Salesforce.
  D. Export legacy data into CSV files and leverage data loader to load data into Salesforce.
  C. Migrate the legacy data leveraging an ETL tool to transform data types and load data into Salesforce.

  ---

  Explanation

  According to this article, migrating the legacy data leveraging an ETL tool to transform data types and load data into Salesforce can be a way to ensure successful data migrations. The article states that ETL tools can help with data cleansing, mapping, transformation, and loading, and that they can handle different data types and formats. The article also provides some best practices for data migration, such as identifying the data to migrate, creating templates for the data, preparing the destination org, and validating the data.

• Question 19:

  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.
  A. Create a "before delete" trigger to check if the current user is not the owner.

  ---

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

  A large multinational B2C Salesforce customer is looking to implement their distributor management application is Salesforce. the application has the following capabilities:

  1.Distributor create sales order in salesforce

  2.Sales order are based on product prices applicable to their region

  3. Sales order are closed once they are fulfilled

  4. It is decided to maintain the order in opportunity object

  How should the data architect model this requirement?

  A. Create lookup to Custom Price object and share with distributors.
  B. Configure price Books for each region and share with distributors.
  C. Manually update Opportunities with Prices application to distributors.
  D. Add custom fields in Opportunity and use triggers to update prices.
  B. Configure price Books for each region and share with distributors.

  ---

  Explanation

  According to the Salesforce documentation, an opportunity is a standard object that represents a potential sale or deal with an account or contact. An opportunity can have products and prices associated with it using price books. A price book is a standard object that contains a list of products and their prices for different regions, currencies, segments, etc. A price book can be shared with different users or groups based on their visibility and access settings.

  To model the requirement of implementing a distributor management application in Salesforce, where distributors create sales orders based on product prices applicable to their region, and sales orders are closed once they are fulfilled, a data architect should: Configure price books for each region and share with distributors (option B). This means creating different price books for different regions with the appropriate products and prices, and sharing them with the distributors who belong to those regions. This way, distributors can create sales orders (opportunities) using the price books that are relevant to their region.

  Creating a lookup to Custom Price object and sharing with distributors (option A) is not a good solution, as it can introduce unnecessary complexity and redundancy to the data model. It is better to use standard objects and features that are designed for managing products and prices in Salesforce. Manually updating opportunities with prices applicable to distributors (option C) is also not a good solution, as it can be time-consuming, error-prone, and inefficient. It is better to use automation tools or features that can update prices based on predefined criteria or logic. Adding custom fields in opportunity and using triggers to update prices (option D) is also not a good solution, as it can be complex, costly, and difficult to maintain. It is better to use standard fields and features that can handle prices more effectively.