Practice Free Data-Architect Salesforce Certified Platform Data Architect Plat-Arch-201 Exam Questions Answers With Explanation

According to the Get Started with Custom Metadata Types unit on Trailhead, one of the use cases for custom metadata types is to define custom charges for an accounting app. The unit states that “Say that your org uses a standard accounting app. You can create a custom metadata type that defines custom charges, like duties and VAT rates. Then you can write some Apex code that calculates the total amount due for each invoice by using the metadata from your custom metadata type.” Therefore, a similar approach can be used to maintain the pricing criteria for a custom pricing engine in Salesforce.

Doing client-side validation of phone number and email field formats and preferring picklist form fields over free text fields, where possible, are two techniques that will help maintain a high level of data quality when designing forms that create Lead records in Salesforce using the REST API. Client-side validation can ensure that the input data is in the correct format and prevent errors or invalid values from being submitted. Picklist form fields can provide a predefined set of values for the users to choose from and avoid typos or inconsistencies in the data.

The data architect should choose to implement duplicate rules in SF (Salesforce) to validate duplicates during the account creation process. Duplicate rules are a feature in Salesforce that allow users to define criteria and actions for detecting and preventing duplicate records. By creating duplicate rules for accounts, the data architect can ensure that any leads from the website or customers from the retail stores that match existing accounts in Salesforce are flagged or blocked before they are created as new accounts. This will help avoid duplicate accounts in Salesforce and maintain data quality. Option B is incorrect because implementing a MDM (Master Data Management) solution to validate the customer information before creating accounts in SF will require additional infrastructure cost and maintenance effort. Option C is incorrect because building custom search based on fields on accounts which can be matched with customer when they visit the store will require additional development effort and may not be accurate or user-friendly. Option D is incorrect because customizing account creation process to search if customer exists before creating an account will require additional configuration effort and may not be consistent or scalable.

According to the Salesforce documentation, a hub-and-spoke model is an integration architecture pattern that allows connecting multiple Salesforce orgs using a central org (hub) and one or more secondary orgs (spokes). The hub org acts as the master data source and orchestrates the data flow between the spoke orgs. The spoke orgs act as the consumers or producers of the data and communicate with the hub org.

To orchestrate data between the hub org and spoke orgs, a data architect should use:

A middleware solution that extracts and distributes data across both the hub and spokes (option A). This means using an external service or tool that can connect to multiple Salesforce orgs using APIs or connectors, and perform data extraction, transformation, and distribution operations between the hub and spoke orgs. This can provide a scalable, flexible, and reliable way to orchestrate data across multiple orgs.

Developing custom APIs to poll the hub org for change data and push into the spoke orgs (option B) is not a good solution, as it can be complex, costly, and difficult to maintain. It may also not be able to handle large volumes of data or complex transformations efficiently. Developing custom APIs to poll the spoke orgs for change data and push into the hub org (option C) is also not a good solution, as it can have the same drawbacks as option B. It may also not be able to handle conflicts or errors effectively. Using a backup and archive solution that extracts and restores data across orgs (option D) is also not a good solution, as it can incur additional costs and dependencies. It may also not be able to handle real-time or near-real-time data orchestration requirements.

The correct answer is B, use data classification metadata fields available in field definition. Data classification metadata fields are standard fields that allow you to classify the sensitivity level of your data based on your organization’s policies. You can use these fields to indicate whether a field contains confidential, restricted, or general data. These fields are available for both standard and custom objects in Salesforce. Using app exchange products, creating a custom picklist field, or building reports would not be as effective or consistent as using data classification metadata fields.

The recommended solution for Universal Containers (UC) to implement its new Internet of Things technology is to create a new Container Reading custom object with a master-detail relationship to Container which is created when a new measure is received for a specific container. Implement an archiving process that runs every hour. This solution would allow UC to store and access current and historical temperature and humidity data for each container on Salesforce, and use reports and dashboards to analyze it. However, since UC expects a large volume of data over time, they should implement an archiving process that moves data off-platform after a certain period of time to avoid hitting the Org data storage limit and maintain optimal performance. The other options are not recommended, as they would either not store the historical data on Salesforce, or create too many custom fields on the Container object that could impact performance and usability.

Pre-processing the data means transforming and cleansing the data before loading it into Salesforce. This can reduce the errors and conflicts that might occur during the data load. Using Data Loader with SOAP API to upsert with zip compression enabled can also improve the performance and efficiency of the data load by reducing the network bandwidth and avoiding duplication

Scheduling a weekly dashboard displaying records that are missing information to be sent to managers for review and using Workflow, Validation Rules, and Force.com code (Apex) to enforce critical business processes are two approaches that an architect should recommend to enforce the new Data Quality Plan for UC’s Salesforce data. Scheduling a weekly dashboard can provide a regular and visual way of monitoring the data quality and identifying any gaps or issues that need to be addressed by the managers or users. Using Workflow, Validation Rules, and Apex can provide various ways of enforcing data quality standards and business logic by automating actions, displaying error messages, or executing custom code when users create or edit records. The other options are not suitable or helpful for enforcing the Data Quality Plan, as they would either not provide real-time feedback, not prevent data quality issues, or not leverage the capabilities of Salesforce

Exploring external data sources in Salesforce to build a 360 degree view of the customer (option A) is the best strategy to satisfy this requirement, as it allows customer service agents to view the activities from all four systems in real time without storing or replicating the data in Salesforce. Using a customer data mart to create the 360 degree view of the customer (option B) is not a good strategy, as it may introduce additional complexity and cost, and it does not leverage the native Salesforce features. Periodically uploading summary information in Salesforce to build a 360 degree view (option C) is also not a good strategy, as it may cause data latency and inconsistency, and it does not provide real-time information. Migrating customer activities from all four systems into Salesforce (option D) is also not a good strategy, as it may cause data redundancy and conflicts, and it does not scale well with large volumes of data.

According to the official Salesforce guide1, big objects are designed to store and manage massive data volumes within Salesforce without affecting performance. They can be queried by using Async SOQL or standard SOQL, and they can be accessed by using Apex, Visualforce, Lightning components, or APIs. Big objects are ideal for storing data that is used for analytics or reporting purposes, such as the reward program data. Option A is the correct answer because it allows NTO to create a custom big object in Salesforce that can store the reward program data and make it available for consumption by Einstein Analytics and Discovery. Option B is incorrect because Einstein cannot connect directly to the point of sales system to capture the reward program data. Option C is incorrect because Einstein Analytics does not support creating big objects. Option D is incorrect because custom objects are not suitable for storing large volumes of data.

The best solution to store historical cases for 10 years for audit purpose is to use a custom Big object to store archived case data. Big objects are a type of custom object that can store massive amounts of data on the Salesforce platform without affecting performance or storage limits. They also support point-and-click tools, triggers, and Apex code. Big objects can be used for archiving historical data that needs to be retained for compliance or analytics purposes3. Archiving case data using Salesforce Archiving process is not a good option because it only supports archiving cases that are closed for more than one year, and it does not allow customizing the archival criteria or accessing the archived data via Apex or APIs4. Purchasing more data storage to support case object is expensive and may impact performance. Using a custom object to store archived case data is not scalable and may consume a lot of storage space.

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.

 Implementing a custom big object to store the data is the best recommendation to reduce the performance degradation of the platform, as it allows storing large volumes of data that do not need real-time access or reporting. Custom big objects can be defined using metadata API or developer console, and support up to 1 billion records per object. Creating a custom object or using the standard order object would consume a lot of storage space and impact the performance of queries and reports. Using a standard big object defined by salesforce would not be applicable for order records, as standard big objects are predefined for specific use cases such as audit trails or field history.

 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

 Creating a custom object related to the Invoice object with a picklist field for the Type allows the architect to categorize the attachments and report on them by Type. The standard Attachment object does not have a ContentType picklist field, and adding a custom picklist field to it would not be best practice.

A master-detail field on VTOTime__c to Project__c is the data relationship that the data architect should use to support the requirement when creating the custom VTOTime__c object. A master-detail relationship creates a parent-child relationship between two objects, where the master record controls certain behaviors of the detail record, such as security, ownership, deletion, and roll-up summary fields. By using a master-detail field on VTOTime__c to Project__c, you can ensure that the ability to view or edit the VTOTime__c object is the same as the Project__c record, and that managers can see the total hours volunteered while viewing the Project__c record using a roll-up summary field.

According to the Salesforce documentation2, duplicate leads are leads that have the same or similar information as other leads in Salesforce. Duplicate leads can cause poor customer experience, higher costs, and inaccurate reporting. To mitigate the issues caused by duplicate leads, some of the recommended practices are:

Standardize lead information across all channels (option B). This means using consistent formats, values, and fields for capturing lead data from different sources, such as web forms, email campaigns, or third-party vendors. This can help reduce data quality issues and make it easier to identify and prevent duplicate leads.

Implement a third-party solution to clean and enrich lead data (option D). This means using an external service or tool that can validate, correct, update, and enhance lead data before or after importing it into Salesforce. This can help improve data quality and accuracy, and reduce duplicate leads.

Implement a de-duplication strategy to prevent duplicate leads (option E). This means using Salesforce features or custom solutions that can detect and block duplicate leads from being created or imported into Salesforce. For example, using Data.com Duplicate Management3, which allows defining matching rules and duplicate rules for leads and other objects.

Building a process to manually search and merge duplicates (option A) is not a good practice, as it can be time-consuming, error-prone, and inefficient. Building a custom solution to identify and merge duplicate leads (option C) is also not a good practice, as it can be complex, costly, and difficult to maintain. It is better to use existing Salesforce features or third-party solutions that can handle duplicate leads more effectively.

 Creating a duplicate rule for account, lead, and contact, using standard matching rules for these objects, and setting the action to report and alert for both creates and edits can help UC fix the issue immediately by prompting users about a record that possibly exists in Salesforce. This can also generate a report regarding duplicate records that can be used for further analysis and resolution

Creating a custom object to store a copy of the record when changed and creating a custom object to store the previous and new field values are two possible actions that an architect can perform to meet the requirement of tracking field history on 100 Opportunity fields. A custom object can store more fields and records than the standard field history tracking feature, which has a limit of 20 fields per object and 18 or 24 months of data retention. A custom object can also be used for reporting and analysis of field history data. The other options are not feasible or effective for meeting the requirement

According to this article, inserting 1 million orders distributed across a variety of accounts with potential lock exceptions is a scenario where using the Bulk API in serial mode can help to prevent the lock contention issue that can occur in parallel mode.

The correct answer is A, enable defer sharing calculations, and suspend sharing rule calculations. Defer sharing calculations and suspend sharing rule calculations are features that allow you to temporarily disable the automatic recalculation of sharing rules when you load large volumes of data. This can improve the performance and speed of your data load process by avoiding unnecessary system calculations. Loading the data through data loader, leveraging the bulk API, or enabling granular locking are also options that can help with data load times, but they do not directly address the system calculations issue.

 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.

Contacting Salesforce to enable Defer Sharing Rules is the feature that would ensure that performance, when moving Sales Reps between regions, remains adequate while meeting existing requirements. Defer Sharing Rules allows you to defer sharing rule recalculation when you make changes to public groups or roles that are used in sharing rules. This can improve performance and avoid locking issues when you move users between groups or roles2. Implementing data archiving for old Shipment records will not help with the performance issue related to sharing rules. Contacting Salesforce to create Skinny tables on Shipment will not help with the performance issue related to sharing rules. Configuring shipment OWD to Public Read/Write will not meet the existing requirements of having a Private sharing model.

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

 Creating validation rules to check if the required attributes are entered is the best option to mandate this when customers are created in Salesforce. Validation rules allow you to specify criteria that must be met before a record can be saved. You can use validation rules to ensure that customers have a first name, last name, and email when they are created in Salesforce. This way, you can prevent incomplete or invalid data from being sent to your MDM solution.

The data classification feature allows customers to classify their data in Salesforce based on two policies:

Data sensitivity level: This policy defines how sensitive the data is and what level of protection it requires. For example, high sensitivity data may require encryption or masking.

Compliance categorization policy: This policy defines how the data is regulated by various laws and standards. For example, GDPR or PCI DSS.

Using Bulk API to export 1 million records from Salesforce is the best option. Bulk API is a RESTful API that allows you to perform asynchronous operations on large sets of data. You can use Bulk API to create, update, delete, or query millions of records in batches. Bulk API is optimized for performance and scalability, and it can handle complex data loading scenarios.

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.

 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.

According to the Salesforce documentation, SOQL is a query language that allows querying data from Salesforce objects and fields. SOQL queries have various clauses and operators that can be used to filter and sort the results. However, some clauses and operators can affect the performance of SOQL queries by increasing the cost or complexity of executing them.

To make this query more performant, a data architect should change the where clause to filter by a deterministic defined value (option D). This means using a filter condition that specifies a concrete value or range of values for a field, such as WhatId = ‘001xx000003DGg3’ or WhatId IN (‘001xx000003DGg3’, ‘001xx000003DGg4’). This can improve the performance of the query by reducing the number of records that need to be scanned and returned. A deterministic defined value can also leverage an index on the field, which can speed up the query execution.

Removing description from the requested field set (option A) is not a good solution, as it can affect the functionality or usability of the query. The description field may contain important or relevant information that is needed for the process. Changing the query to SOSL (option B) is also not a good solution, as SOSL is a different query language that allows searching text fields across multiple objects. SOSL queries have different syntax and limitations than SOQL queries, and may not return the same results or performance. Adding limit 100 to the query (option C) is also not a good solution, as it can affect the completeness or accuracy of the query. The limit clause specifies the maximum number of records that can be returned by the query, which may not include all the records that match the filter condition.

A performance test plan is required for any Force.com application that has highly customized code or large volumes of data. You need to create and submit a performance test plan to Salesforce customer support before conducting any performance testing in your sandbox or production org2. Applications with highly customized code or large volumes of data should be performance tested to ensure they meet the expected response time and throughput

Data Loader uses external Id fields to match records in the CSV file with records in Salesforce during an upsert operation. If the CSV file contains duplicate external Id values within the same file, Data Loader will throw an error saying “Duplicate Id Specified” and will not process those records. Therefore, it is important to ensure that the CSV file does not have any duplicate external Id values before using Data Loader to upsert records.

Having each system pull the record changes from Salesforce using change data capture (option D) is the correct solution for ensuring all systems using customer data are kept up to date, as it allows the systems to subscribe to real-time events from Salesforce and receive notifications when customer records are created, updated, deleted, or undeleted. Sending customer data nightly to the system of truth in a scheduled batch job (option A) or sending customer record changes from Salesforce to each system in a nightly batch job (option B) are not good solutions, as they may cause data latency and inconsistency, and they do not provide real-time updates. Sending customer record changes from Salesforce to the system of truth in real time (option C) is also not a good solution, as it does not address how the other systems will receive the updates from the system of truth.

According to the Salesforce documentation2, extracting large amounts of data from Salesforce can be challenging and time-consuming, as it can encounter performance issues, API limits, timeouts, etc. To extract 100 million records from Salesforce for migration to an enterprise data warehouse (EDW), a data extraction strategy that can provide maximum performance is:

Utilize PK Chunking with the Bulk API (option C). This means using a feature that allows splitting a large query into smaller batches based on the record IDs (primary keys) of the queried object. This can improve performance and avoid timeouts by processing each batch asynchronously and in parallel using the Bulk API3.

Installing a third-party AppExchange tool (option A) is not a good solution, as it can incur additional costs and dependencies. It may also not be able to handle such a large volume of data efficiently. Calling the REST API in successive queries (option B) is also not a good solution, as it can encounter API limits and performance issues when querying such a large volume of data. Using the Bulk API in parallel mode (option D) is also not a good solution, as it can still cause timeouts and errors when querying such a large volume of data without chunking.

Using an AppExchange package for Data Quality is a good way to match Salesforce data against a trusted source, such as an MDM system. You can use tools like Cloudingo, DupeCatcher, or DemandTools to identify and merge duplicate records, standardize data formats, and enrich data with external sources

Enabling “Set Audit Fields” allows the user loading the data to set the value of the standard CreatedDate field to match the original date from the legacy system. This is a one-time permission that can be revoked after the migration is completed. The other options would either not work or require additional customization

According to the exam guide, one of the objectives is to "describe best practices for implementing a single-org strategy in a B2C scenario"1. This implies that option D is the best practice for loading individual consumers as contacts in Salesforce. This approach avoids creating unnecessary accounts and reduces data duplication. Option C is not correct because it creates one account per contact, which increases data volume and complexity. Options A and B are not correct because they do not leverage the standard contact object, which provides native functionality and integration with other Salesforce features.

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

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.

The two features that a data architect should recommend to share records between Salesforce orgs are:

Change Data Capture (CDC): This is a feature that publishes change events for changes in Salesforce records, such as create, update, delete, and undelete operations. Change events can be subscribed by external systems or other Salesforce orgs using various tools, such as Platform Events, Streaming API, or CometD. CDC can help keep data in sync between Salesforce orgs in near real time89.

Salesforce to Salesforce (S2S): This is a feature that allows sharing records and related data with other Salesforce orgs that you partner with. You can choose which records and fields to share, and which orgs to share with. You can also accept updates from the other orgs to keep the data consistent10.

Salesforce Connect is not a good feature to share records between Salesforce orgs because it is intended for integrating external data sources with Salesforce using external objects. Federation Search is not a good feature to share records between Salesforce orgs because it is intended for searching across multiple Salesforce orgs without sharing data.

The correct answer is B, add custom indexes on frequently searched account and contact object fields. Custom indexes are a way to improve the performance of your queries and reports by creating indexes on specific fields that are often used in filters or joins. By adding custom indexes on frequently searched account and contact object fields, you can speed up the response time for reports and list views. Loading only the data that users are permitted to access, limiting data loading to the 2000 most recent records, or creating a skinny table are also possible solutions, but they are either not feasible, not scalable, or not supported by Salesforce.

The data architect should recommend building a batch job to move two-year-old records off platform, and delete records from Salesforce as an archiving solution. A batch job is a process that runs in the background and performs operations on large volumes of data in Salesforce. By building a batch job that moves two-year-old records off platform to an external storage system, such as Amazon S3 or Google Cloud Storage, and deletes them from Salesforce, the data architect can reduce the storage consumption and improve the performance of Salesforce org. Option A is incorrect because using a third-party backup solution to backup all data off platform will not free up any storage space in Salesforce, unless the data is also deleted from Salesforce after backup. Option B is incorrect because building a batch job to move all records off platform, and delete all records from Salesforce will result in losing all the current data in Salesforce, which may not be desirable or feasible. Option D is incorrect because building a batch job to move all restore off platform, and delete old records from Salesforce does not make sense, as restore implies restoring data back to Salesforce, not moving it off platform.

The best solution to extract 50 million records from a custom object everyday from Salesforce org without facing query timeout issues is to use an ETL tool for extraction of records. ETL stands for extract, transform, and load, and it refers to a process of moving data from one system to another. An ETL tool is a software application that can connect to various data sources, perform data transformations, and load data into a target destination. ETL tools can handle large volumes of data efficiently and reliably, and they often provide features such as scheduling, monitoring, error handling, and logging5. Using a custom auto number and formula field and use that to chunk records while extracting data is a possible workaround, but it requires creating additional fields and writing complex queries. The REST API can extract data as it automatically chunks records by 200, but it has some limitations, such as a maximum of 50 million records per query job6. Asking SF support to increase the query timeout value is not feasible because query timeout values are not configurable

The two tasks required to define the data archive strategy are to identify how the archive data will be accessed and used, and identify the data retention requirements. Data archiving is the process of moving infrequently used or historical data from active storage to a separate storage location for long-term retention. Data archiving can improve performance, reduce storage costs, and comply with legal or regulatory obligations. To define a data archive strategy, a data architect needs to consider how the archived data will be accessed and used by different users or processes in Salesforce or outside Salesforce, and how long the archived data needs to be retained based on business or legal requirements.

The Individual object is a standard object that lets you store details about data privacy and protection preferences for person accounts, contacts, users, and leads. The Individual object can be used to implement a standard communication preference management model for NTO, with relationships to the other objects.

Using an ETL tool to orchestrate the migration is the best strategy for this scenario, as it can handle the data model changes, the large volume of records, and the tight timeline. Writing a script to use the Bulk API (option C) is also possible, but it would require more coding and testing effort. Using Data Loader and Data Import Wizard (option B) is not suitable for migrating three million records, as they have limitations on the batch size and the number of records per operation. Using Salesforce CLI (option D) is also not recommended for large data migration, as it is mainly designed for development and testing purposes

Implementing a workflow rule that sends Opportunity data through Outbound Messaging is the optimal real-time approach that achieves the solution of copying Opportunity records to the ERP once they reach a Closed/Won Stage. A workflow rule can trigger an Outbound Message when an Opportunity record meets certain criteria, such as having a Closed/Won Stage. An Outbound Message can send data from Salesforce to an external system via SOAP API, without requiring any code. The external system can then process the data and create a read-only record in the ERP system. The other options are not optimal or real-time, as they would either require additional systems or tools, not provide real-time data synchronization, or not meet the frequency requirement

The three characteristics of a Skinny table that help improve report and query performance are: Skinny tables can contain frequently used fields and thereby help avoid joins. Skinny tables are kept in sync with changes to data in the source tables. Skinny tables do not include records that are available in the recycle bin. These characteristics are beneficial because they reduce the query complexity and execution time, and improve the data accuracy and freshness. For example, skinny tables can contain frequently used fields from multiple objects, such as Account and Contact, and thereby help avoid joins that can slow down queries4. Skinny tables are updated automatically when the source tables are modified, so they always reflect the latest data5. Skinny tables do not include records that are available in the recycle bin, so they only contain active records that are relevant for reports and queries.

Setting up a Validation Rule to prevent blank values and marking the field required in setup at the field level are two approaches that the Architect should take to ensure that the field always contains data coming from the source system. A Validation Rule can display an error message when a record is created or edited with a blank value for the field, and prevent it from being saved. Marking the field required in setup at the field level can enforce the requirement for all records, regardless of the page layout or the source system. The other options are not effective or recommended for ensuring data quality, as they would either not prevent blank values, not apply to all records, or not address the root cause of the problem

The best solution to assign opportunities based on zip code and sales area is to configure territory management feature to support opportunity assignment. Territory management is a feature that allows you to organize your sales team into territories based on criteria such as geography, industry, product line, or customer segment. You can assign accounts and opportunities to territories using assignment rules or manual sharing. You can also define forecast managers and roll up forecasts by territory45. Assign opportunities using list views using zip code is not a good solution because it is inefficient and does not support reporting by sales area. Add custom fields in opportunities for zip code and use assignment rules is not a good solution because it requires creating additional fields and does not support reporting by sales area. Allow sales users to manually assign opportunity ownership based on zip code is not a good solution because it is prone to errors and does not support reporting by sales area.

To provide the sales team with the required functionality, a data architect should use a mashup page that will present the billing system records within Salesforce. A mashup page is a web page that combines data from multiple sources into a single integrated view. A mashup page can be created using Visualforce or Lightning Web Components, and can use Salesforce Connect or custom integrations to access external data from the on-premise web-based billing and invoice system. This will allow the sales team to pull a customer record and view their account status, invoice history, and opportunities without navigating outside of Salesforce. Option A is incorrect because creating a custom object and migrating the last 12 months of invoice data into Salesforce so it can be displayed on the account layout will consume a lot of storage space and may not reflect the latest data from the billing system. Option B is incorrect because writing an Apex callout and populating a related list to display on the account record will require additional development effort and may not be scalable or performant for large volumes of data. Option D is incorrect because creating a visual force tab with the billing system encapsulated within an iframe will not allow the sales team to view the billing system records within the customer record, but rather in a separate tab.

 Event Monitoring is a feature that allows you to track user actions, such as logins, logouts, downloads, etc., in your Salesforce org. You can use Event Monitoring to monitor performance, usage, security, and compliance

PK Chunking can resolve query timeout when running a bulk query on an object with more than 10 million records. PK Chunking is a feature of the Bulk API that splits a query into multiple batches based on the record IDs (primary keys) of the queried object. This can improve the query performance and avoid timeouts by reducing the number of records processed in each batch.

Enabling field history tracking on the Case object is the first step to implement a reporting solution to measure the support reps case closure rates. Field history tracking allows you to track changes to certain fields on the Case object, such as Status, Owner, or Priority. You can then create reports based on the field history data to analyze how long it took to close a case, how many times the case owner changed, or how many cases were escalated.

 According to the How to avoid row lock or race condition in Apex blog post, one of the ways to prevent race condition in Apex is to use the FOR UPDATE keyword in SOQL statements. The blog post states that “We need to lock the records on which we are working such that other batches or threads will not be having any effect on them. How can we lock a record, then? We need to make use of FOR UPDATE keyword in the SOQL query.” Therefore, a data architect should recommend this solution to guarantee that records are not being updated at the same time by different processes.

According to the Salesforce documentation1, reporting performance can be affected by various factors, such as the volume and complexity of data, the design and configuration of reports and dashboards, the number and type of users accessing the reports, etc. To improve reporting performance, some of the recommended solutions are:

Move data off of the platform and run reporting outside Salesforce, and give access to reports (option C). This means using an external service or tool that can extract, transform, and load (ETL) data from Salesforce to another system or database, such as a data warehouse or a business intelligence platform. This can improve reporting performance by reducing the load and latency on Salesforce, and enabling faster and more flexible reporting and analysis on the external system. Users can access the reports from the external system using a link or an embedded component in Salesforce.

Contact Salesforce support to enable skinny table for cases (option B). This means requesting Salesforce to create a custom table that contains a subset of fields from the Case object that are frequently used or queried. A skinny table can improve reporting performance by avoiding joins between standard and custom fields, omitting soft-deleted records, and leveraging indexes on the fields2.

Create a custom object to store aggregate data and run reports (option A). This means creating a custom object that contains summary or calculated data from the Case object, such as counts, sums, averages, etc. A custom object can improve reporting performance by reducing the number of records and fields that need to be queried and displayed.

Build reports using custom Lightning components (option D). This means creating custom components that use Lightning Web Components or Aura Components frameworks to display report data in Salesforce. A custom component can improve reporting performance by using client-side caching, pagination, lazy loading, or other techniques to optimize data rendering and interaction.

To capture and report on any changes made to ten text fields on the Contact object for the past 3 months, the data architect should write an Apex trigger on Contact after insert and after update events and store the old values in another custom object, or turn on field Contact object history tracking for these ten fields and create reports on contact history. An Apex trigger can capture the old and new values of the fields, as well as the user and time of the change, and store them in a custom object that can be used for reporting. Field history tracking can also track the changes to the fields and store them in a history table that can be used for reporting. However, field history tracking only retains data for up to 18 months or 24 months with an extension, so it may not be suitable for longer-term reporting needs. The other options are not feasible or effective for capturing and reporting on field data changes.

  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.

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.

The best solution to resolve the error of “Unable to lock a row” during the account load is to perform batch job in serial mode and reduce batch size. This is because roll-up summary fields are calculated synchronously when the parent record is updated, and asynchronously when the child record is updated. Therefore, updating many child records at once can cause locking issues on the parent record. To avoid this, it is recommended to use serial mode and smaller batch sizes when loading data using tools like Data Loader or Bulk API12. Leverage data loader platform API to load data is not a good option because it does not specify the mode or batch size. Perform batch job in parallel mode and reduce batch size is not a good option because parallel mode can still cause locking issues even with smaller batches. Defer roll-up summary fields calculation during data migration is not a good option because it is not possible to defer or disable roll-up summary fields calculation

Option A is correct because RecordType is a valid metadata type that should be included in documenting the data architecture of a Salesforce organization1. RecordType defines different business processes, picklist values, and page layouts for different users2. Option C is correct because CustomField is another valid metadata type that should be included in documenting the data architecture of a Salesforce organization1. CustomField defines custom attributes for standard or custom objects3. Option B is not correct because Document is not a valid metadata type, but a standard object that stores documents in folders4. Option D is not correct because SecuritySettings is not a valid metadata type, but a setup menu that allows administrators to configure various security features such as password policies, network access, session settings, etc.

Changing Opportunity Amount field access to Read Only for sales users field-level security (option C) is the best way to address the overwriting issue, as it prevents sales users from updating the field that is controlled by PPS, and ensures data consistency and accuracy. Creating a custom field for Opportunity amount that PSS updates separating the field sales user updates (option A) or creating a custom field for Opportunity amount that sales users update separating the field that PPS updates (option D) are not good solutions, as they may create confusion and inconsistency with the Opportunity Forecast feature. Changing PSS integration to update only Opportunity Amount field when the value is null (option B) is also not a good solution, as it may cause data loss or conflicts with the sales users’ inputs.

A correct technique UC should use to solve the data inconsistency is to define a data taxonomy for product data and apply the taxonomy to the product data in the data warehouse. A data taxonomy is a hierarchical classification of data entities and attributes that defines their meaning, format, and relationships. A data taxonomy can help ensure consistency, accuracy, and completeness of product data across different systems and channels

Implementing duplicate rules (option D) is the best solution to remediate the duplication issue, as it allows the data architect to identify and merge duplicate accounts in Salesforce using native features and tools. Developing an ETL process that utilizes the merge API to merge the duplicate records (option A) is not a good solution, as it may require more coding and testing effort, and it does not prevent duplicates from being created in Salesforce. Utilizing a data warehouse as the system of truth (option B) is also not a good solution, as it may introduce additional complexity and cost, and it does not address the duplication issue in Salesforce. Extracting the data using data loader and using excel to merge the duplicate records (option C) is also not a good solution, as it may be time-consuming and error-prone, and it does not prevent duplicates from being created in Salesforce.

Cleaning data before importing to Salesforce and using Salesforce matching and duplicate rules are two design considerations that an architect should take to minimize data duplication when migrating legacy account data from two aging systems into Salesforce. Cleaning data before importing involves removing or correcting any inaccurate, incomplete, or inconsistent data from the source systems, as well as identifying and resolving any potential duplicates. This ensures that only high-quality and unique data is imported to Salesforce. Using Salesforce matching and duplicate rules allows the architect to define how Salesforce identifies duplicate records during import and how users can handle them. This prevents or reduces the creation of duplicate records in Salesforce and improves data quality. The other options are not effective or recommended for minimizing data duplication.

According to the official Salesforce guide1, using Bulk API serial mode for data migration can help avoid locking issues by processing batches in a single thread. This mode ensures that batches are processed in the order they are received and that only one batch is processed at a time. This reduces the risk of lock contention and deadlocks, especially when updating parent and child records in a lookup relationship. Option B is the correct answer because it suggests using Bulk API serial mode for data migration. Option A is incorrect because using Bulk API parallel mode for data migration can cause locking issues by processing batches in multiple threads. This mode does not guarantee the order of batch processing and can result in concurrent updates to the same records, which can lead to lock contention and deadlocks. Option C is incorrect because inserting the order in another custom object and using Batch Apex to move the records to Service_Order__c object adds unnecessary complexity and overhead to the data migration process. Option D is incorrect because changing the lookup configuration to “Clear the value of this field” when lookup record is deleted does not address the locking issues caused by data migration, but rather by record deletion.

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.

Enabling Account de-duplication by creating matching rules in Salesforce, which will mass merge duplicate Accounts, is what UC should do to ensure proper data quality for their Account records. Matching rules allow UC to define how Salesforce identifies duplicate Accounts based on various criteria, such as name, address, phone number, etc. Mass merge allows UC to merge up to 200 duplicate Accounts at a time, based on the matching rules. This simplifies and automates the process of de-duplicating Accounts and improves data quality. The other options are either more time-consuming, costly, or error-prone for ensuring proper data quality.

The correct answer is A. To provide additional guidance for users when they enter information in a standard field, a data architect should provide custom help text under field properties. This will display a help icon next to the field label that users can hover over to see the help text. Option B is incorrect because creating a custom page with help text for user guidance will require additional development effort and may not be easily accessible by users. Option C is incorrect because adding custom help text in default value for the field will overwrite the actual default value of the field and may confuse users. Option D is incorrect because adding a label field with help text adjacent to the custom field will clutter the page layout and may not be visible to users.

Lightning Platform Plus is the license type that best fits UC’s requirements, as it allows up to 50 custom objects and 40,000 API calls per user per 24-hour period4. Service Cloud does not provide enough custom objects or API calls. Lightning Platform Start only allows up to 10 custom objects and 5,000 API calls per user per 24-hour period. Lightning External Apps Start is for external users and does not provide enough API calls.

Analytics/BI Owners and Data Domain Stewards are appropriate roles as members of a team that makes decisions on enterprise-wide data governance. Analytics/BI Owners are responsible for defining the business requirements and metrics for data analysis and reporting, and Data Domain Stewards are responsible for defining and enforcing the data quality standards and rules for specific data domains. Salesforce Administrators and Operational Data Users are not suitable roles for this team, as they are more focused on the operational aspects of data management, such as configuration, maintenance, and usage.

According to the Salesforce documentation1, the query plan tool is a tool that can be enabled and used in the developer console to analyze the performance of a SOQL query. The query plan tool shows the cost, cardinality, sObject type, and relative cost of each query plan that Salesforce considers for a query. The relative cost indicates how expensive a query plan is compared to the Force.com query optimizer threshold. A query plan with a relative cost above 1.0 is likely to cause a time-out error.

To identify why the query is taking too long, a data architect should use the query plan tool in the developer console (option B). This way, the data architect can see which query plan is chosen by Salesforce and how it affects the performance of the query. The data architect can also use the query plan tool to optimize the query by adding indexes, filters, or limits to reduce the cost and improve the efficiency of the query.

Using Splunk to query the system logs looking for transaction time and CPU usage (option A) is not a good solution, as it can be complex, costly, and difficult to integrate with Salesforce. It may also not provide enough information or insights to identify and optimize the query performance. Using Salesforce’s query optimizer to analyze the query in the developer console (option C) is also not a good solution, as it is not a separate tool that can be used in the developer console. The query optimizer is a feature that runs automatically when a SOQL query is executed and chooses the best query plan based on various factors2. Opening a ticket with Salesforce support to retrieve transaction logs to be analyzed for processing time (option D) is also not a good solution, as it can be time-consuming, dependent, and inefficient. It may also not provide enough information or insights to identify and optimize the query performance.