DATA-ARCHITECT Online Practice Questions and Answers

Correct Answer: CD

Explanation: Engaging with executive sponsorship to assess enterprise data strategy and goals, and engaging with business units and IT to assess current operational systems and data models are two first steps that would be appropriate for UC to initiate an assessment of data architecture. These steps will help to understand the current state of data management, the business needs and expectations, and the gaps and opportunities for improvement. Engaging with IT program managers to assess current velocity of projects in the pipeline, and engaging with database administrators to assess current database performance metrics are not relevant steps for assessing data architecture, as they are more related to project management and technical performance.

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.

Correct Answer: B

Explanation: According to the official Salesforce guide1, assigning leads to a single dummy user can cause performance issues and data skew, especially if the dummy user owns more than 10,000 records. Data skew occurs when a single user or a small number of users own a disproportionately large number of records, which can affect query performance and sharing calculations. Option B is the correct answer because it suggests creating multiple dummy users and assigning leads to them, which can distribute the load and reduce data skew. Option A is incorrect because assigning the dummy user to the last role in the role hierarchy does not affect the performance or data skew issues. Option C is incorrect because assigning the dummy user to the highest role in the role hierarchy can worsen the performance and data skew issues, as it will grant access to more users and records. Option D is incorrect because periodically deleting leads can cause data loss and does not address the root cause of the problem.

Correct Answer: D

Explanation: Evaluating a third-party AppExchange app, such as OwnBackup or Spanning, etc., for backup and archival purposes is the best approach to address the requirement of having a one-day SLA for any data loss. These apps can provide automated backups, granular restores, and compliance features that can help UC recover from any data loss or corruption scenarios.

Correct Answer: D

Explanation: According to Trailhead2, Customer 360 Data Manager is a feature that allows administrators to connect, reconcile, and share customer data across Salesforce orgs and external systems. Customer 360 Data Manager can sync product and pricing information from product master database to Salesforce using predefined mappings and rules, ensuring data quality and consistency. Option D is the correct answer because it suggests using Customer 360 Data Manager to sync product and pricing information from product master database to Salesforce. Option A is incorrect because building a custom integration for two-way sync of product and pricing information between product master and Salesforce can introduce data conflicts and duplication issues, as both systems can update the same data independently. Option B is incorrect because building a custom integration for one-way sync of product and pricing information from product master to Salesforce can be costly and time-consuming, as it requires custom development and maintenance. Option C is incorrect because implementing a manual process to update the products from an extract from the products master on a weekly basis can result in data latency and errors, as the products information may change more frequently than once a week.

Correct Answer: BCE

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.

Correct Answer: B

Explanation: Enabling granular locking (option B) is the best option to prevent the error, as it allows finer control over how records are locked during automated or manual processes, and reduces the chances of lock contention or deadlock. Reducing number of users updated concurrently (option A) is not a good option, as it may limit the productivity and efficiency of the system admins, and it does not address the root cause of the error. Analyzing Splunk query to spot offending records (option C) is also not a good option, as it may require more time and effort, and it does not provide a permanent solution for the error. Increasing CPU for the Salesforce org (option D) is also not a good option, as it may introduce additional cost and complexity, and it does not solve the root cause of the error.

Correct Answer: ACE

Explanation: Creating a unique global customer ID for each customer and storing that in all systems for referential identity (option A), investing in a data duplicate tool to de-dupe and merge duplicate records across all systems (option C), and creating a customer master database external to Salesforce as a system of truth and syncing the customer data with all systems (option E) are the three options that a data architect should perform to resolve the issues with the customer data. Option A ensures that each customer can be uniquely identified across different systems, option C eliminates duplicate records and improves data quality, and option E provides a consistent and reliable source of customer data for all systems. Using Salesforce CDC to sync customer data across all systems (option B) is not a good option, as it does not address the duplication or inconsistency issues. Duplicating customer records across the system and providing a two-way sync of data between the systems (option D) is also not a good option, as it may create more confusion and conflicts with customer data.

Correct Answer: ABC

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.

Correct Answer: BC

Explanation: Using Salesforce duplicate management and using validation rules on new record create and edit are two things that an architect should consider using to maintain data quality for managing Contacts. Salesforce duplicate management allows the architect to create matching rules and duplicate rules to identify, prevent, or allow duplicate records based on various criteria. Validation rules allow the architect to enforce data quality standards and business logic by displaying error messages when users try to save invalid data. The other options are not relevant or helpful for maintaining data quality