Salesforce DATA-ARCHITECT Online Practice Questions and Exam Preparation

Salesforce DATA-ARCHITECT Online Questions & Answers

• Question 91:

  UC migrating 100,000 Accounts from an enterprise resource planning (ERP) to salesforce and is concerned about ownership skew and performance.

  Which 3 recommendations should a data architect provide to prevent ownership skew?

  Choose 3 answers:

  A. Assigned a default user as owner of accounts, and assign role in hierarchy.
  B. Keep users out of public groups that can be used as the source for sharing rules.
  C. Assign a default user as owner of account and do not assign any role to default user.
  D. Assign "view all" permission on profile to give access to account.
  E. Assign a default user as owner of accounts and assigned top most role in hierarchy.
  B. Keep users out of public groups that can be used as the source for sharing rules.
  C. Assign a default user as owner of account and do not assign any role to default user.
  E. Assign a default user as owner of accounts and assigned top most role in hierarchy.

  ---

  Explanation

  According to the Salesforce documentation1, ownership skew occurs when a large number of records (more than 10,000) are owned by a single user or queue. This can cause performance issues and lock contention when multiple users try to access or update those records. To prevent ownership skew, some of the recommended practices are: Assign a default user as the owner of the records and do not assign any role to the default user (option C). This way, the records will not be visible to other users in the role hierarchy and will not cause sharing recalculations. Keep users out of public groups that can be used as the source for sharing rules (option B). Sharing rules based on public groups can cause excessive sharing calculations and lock contention when many records are owned by a single user or queue.

  Assign a default user as the owner of the records and assign the top most role in the hierarchy to the default user (option E). This way, the records will be visible to all users in the role hierarchy, but will not cause sharing recalculations or lock contention.

  Assigning a default user as the owner of the records and assigning a role in the hierarchy (option A) is not a good practice, as it can cause sharing recalculations and lock contention when the role is updated or moved. Assigning "view all" permission on profile to give access to the records (option D) is also not a good practice, as it can bypass the security and sharing model and expose sensitive data to unauthorized users.

• Question 92:

  Universal Container (US) is replacing a home-grown CRM solution with Salesforce, UC has decided to migrate operational (Open and active) records to Salesforce, while keeping historical records in legacy system, UC would like historical records to be available in Salesforce on an as needed basis.

  Which solution should a data architect recommend to meet business requirement?

  A. Leverage real-time integration to pull records into Salesforce.
  B. Bring all data Salesforce, and delete it after a year.
  C. Leverage mashup to display historical records in Salesforce.
  D. Build a chair solution to go the legacy system and display records.
  C. Leverage mashup to display historical records in Salesforce.

  ---

  Explanation

  According to the Using Mashups article on Salesforce Developers, one of the techniques for deploying large data volumes is to use mashups to display historical records in Salesforce. The article states that "Mashups are a way to display data from an external system within a Salesforce page without copying or synchronizing the data. Mashups use a combination of Visualforce, Apex callouts, and JavaScript code that runs in the browser. Mashups are useful when you want to display large amounts of read-only data that is stored outside of Salesforce." Therefore, a data architect should recommend this solution to meet the business requirement of UC.

• Question 93:

  Universal Containers (UC) has a Salesforce org with multiple automated processes defined for group membership processing, UC also has multiple admins on staff that perform manual adjustments to the role hierarchy. The automated tasks and manual tasks overlap daily, and UC is experiencing "lock errors" consistently.

  What should a data architect recommend to mitigate these errors?

  A. Enable granular locking.
  B. Remove SOQL statements from Apex Loops.
  C. Enable sharing recalculations.
  D. Ask Salesforce support for additional CPU power.
  A. Enable granular locking.

  ---

  Explanation

  Enabling granular locking (option A) is the best recommendation to mitigate these errors, as it allows finer control over how records are locked during automated or manual processes, and reduces the chances of lock contention or deadlock.

  Removing SOQL statements from Apex Loops (option B) is a good practice for improving performance and avoiding governor limits, but it does not directly address the lock errors issue. Enabling sharing recalculations (option C) is also not relevant for this issue, as it is used to update sharing rules and recalculate access for records. Asking Salesforce support for additional CPU power (option D) is also not a viable solution, as it does not solve the root cause of the lock errors.

• Question 94:

  Northern Trail Outfitters is concerned because some of its data is sensitive and needs to be identified for access.

  What should be used to provide ways to filter and identify the sensitive data?

  A. Define data grouping metadata.
  B. Implement field-level security.
  C. Custom checkbox denoting sensitive data.
  D. Define data classification metadata.
  D. Define data classification metadata.

  ---

  Explanation

  According to the official Salesforce guide1, data classification metadata is a feature that allows administrators to classify data fields based on their sensitivity level, such as confidential, restricted, or general. Data classification metadata can be used to filter and identify sensitive data fields and apply appropriate security measures, such as encryption, masking, or auditing. Option D is the correct answer because it suggests using data classification metadata to provide ways to filter and identify sensitive data. Option A is incorrect because data grouping metadata is not a feature in Salesforce. Option B is incorrect because field-level security is a feature that controls the visibility and editability of fields based on user profiles or permission sets, but it does not provide ways to filter and identify sensitive data. Option C is incorrect because creating a custom checkbox denoting sensitive data is not a scalable or reliable solution, as it requires manual maintenance and does not enforce any security measures.

• Question 95:

  Universal Containers is planning out their archiving and purging plans going forward for their custom objects Topic__c and Comment__c. Several options are being considered, including analytics snapshots, offsite storage, scheduled purges, etc.

  Which three questions should be considered when designing an appropriate archiving strategy?

  A. How many fields are defined on the custom objects that need to be archived?
  B. Which profiles and users currently have access to these custom object records?
  C. If reporting is necessary, can the information be aggregated into fewer, summary records?
  D. Will the data being archived need to be reported on or accessed in any way in the future?
  E. Are there any regulatory restrictions that will influence the archiving and purging plans?
  C. If reporting is necessary, can the information be aggregated into fewer, summary records?
  D. Will the data being archived need to be reported on or accessed in any way in the future?
  E. Are there any regulatory restrictions that will influence the archiving and purging plans?

  ---

  Explanation

  The three questions that should be considered when designing an appropriate archiving strategy are: If reporting is necessary, can the information be aggregated into fewer, summary records? Will the data being archived need to be reported on or accessed in any way in the future? Are there any regulatory restrictions that will influence the archiving and purging plans? These questions are important because they help determine the scope, frequency, and method of archiving and purging data from Salesforce. For example, if reporting is necessary, then summary records or analytics snapshots can be used to store aggregated data and reduce the number of records that need to be archived1. If the data being archived needs to be accessed in the future, then offsite storage or external objects can be used to retain the data and make it available on demand2. If there are any regulatory restrictions, such as GDPR or HIPAA, then the archiving and purging plans need to comply with them and ensure data security and privacy

• Question 96:

  Ursa Major Solar has defined a new Data Quality Plan for their Salesforce data.

  Which two approaches should an Architect recommend to enforce the plan throughout the organization? (Choose two.)

  A. Ensure all data is stored in an external system and set up an integration to Salesforce for view-only access.
  B. Schedule reports that will automatically catch duplicates and merge or delete the records every week.
  C. Enforce critical business processes by using Workflow, Validation Rules, and Apex code.
  D. Schedule a weekly dashboard displaying records that are missing information to be sent to managers for review.
  C. Enforce critical business processes by using Workflow, Validation Rules, and Apex code.
  D. Schedule a weekly dashboard displaying records that are missing information to be sent to managers for review.

  ---

  Explanation

  Enforcing critical business processes by using Workflow, Validation Rules, and Apex code can help ensure data quality and consistency by applying rules and logic to the data entry and update3. Scheduling a weekly dashboard displaying records that are missing information to be sent to managers for review can help identify and fix data quality issues by providing visibility and accountability4.

• Question 97:

  NTO uses salesforce to manage relationships and track sales opportunities. It has 10 million customers and 100 million opportunities. The CEO has been complaining 10 minutes to run and sometimes failed to load, throwing a time out error.

  Which 3 options should help improve the dashboard performance?

  Choose 3 answers:

  A. Use selective queries to reduce the amount of data being returned.
  B. De-normalize the data by reducing the number of joins.
  C. Remove widgets from the dashboard to reduce the number of graphics loaded.
  D. Run the dashboard for CEO and send it via email.
  E. Reduce the amount of data queried by archiving unused opportunity records.
  A. Use selective queries to reduce the amount of data being returned.
  B. De-normalize the data by reducing the number of joins.
  E. Reduce the amount of data queried by archiving unused opportunity records.

  ---

  Explanation

  To improve the dashboard performance, the data architect should use selective queries to reduce the amount of data being returned, de-normalize the data by reducing the number of joins, and reduce the amount of data queried by archiving unused opportunity records. These options will help optimize the query performance, reduce the query complexity, and free up storage space. Option C is incorrect because removing widgets from the dashboard to reduce the number of graphics loaded will not affect the dashboard performance significantly, and may reduce the usability and functionality of the dashboard. Option D is incorrect because running the dashboard for CEO and sending it via email will not improve the dashboard performance, but rather shift the burden to another user.

• Question 98:

  Which two aspects of data does an Enterprise data governance program aim to improve?

  A. Data integrity
  B. Data distribution
  C. Data usability
  D. Data modeling
  A. Data integrity
  C. Data usability

  ---

  Explanation

  Data integrity and data usability are two aspects of data that an Enterprise data governance program aims to improve. Data integrity refers to the accuracy, consistency, and validity of the data across the enterprise2. Data usability refers to the ease of access, analysis, and interpretation of the data by the end users

• Question 99:

  UC has multiple SF orgs that are distributed across regional branches. Each branch stores local customer data inside its org's Account and Contact objects. This creates a scenario where UC is unable to view customers across all orgs.

  UC has an initiative to create a 360-degree view of the customer, as UC would like to see Account and Contact data from all orgs in one place.

  What should a data architect suggest to achieve this 360-degree view of the customer?

  A. Consolidate the data from each org into a centralized datastore
  B. Use Salesforce Connect's cross-org adapter.
  C. Build a bidirectional integration between all orgs.
  D. Use an ETL tool to migrate gap Accounts and Contacts into each org.
  A. Consolidate the data from each org into a centralized datastore

  ---

  Explanation

  Consolidating the data from each org into a centralized datastore is the best suggestion to achieve a 360-degree view of the customer. This way, UC can have a single source of truth for all customer data and avoid data silos and inconsistencies. The other options are not feasible because they either require complex integration, additional cost, or data duplication.

• Question 100:

  Get Cloudy Consulting monitors 15,000 servers, and these servers automatically record their status every 10 minutes. Because of company policy, these status reports must be maintained for 5 years. Managers at Get Cloudy Consulting need access to up to one week's worth of these status reports with all of their details.

  An Architect is recommending what data should be integrated into Salesforce and for how long it should be stored in Salesforce.

  Which two limits should the Architect be aware of? (Choose two.)

  A. Data storage limits
  B. Workflow rule limits
  C. API Request limits
  D. Webservice callout limits
  A. Data storage limits
  C. API Request limits

  ---

  Explanation

  Data storage limits and API request limits are two important factors that affect the data integration and storage in Salesforce. Data storage limits determine how much data can be stored in Salesforce, and API request limits determine how many API calls can be made to Salesforce in a 24-hour period. Both of these limits depend on the edition and license type of the Salesforce org. Workflow rule limits and webservice callout limits are not directly related to data integration and storage, but rather to business logic and external services.