Pass the Salesforce Application Architect Data-Architect Questions and answers with CertsForce

Virtualizing the remaining set of data with salesforce connect and external objects is the best way to meet the requirements with minimal effort, as it allows salesforce to access data stored in Heroku Postgres without storing it in salesforce. This reduces the storage limitations and avoids data duplication. Heroku connect can bi-directionally sync data between systems, but it requires more configuration and maintenance. Making callouts to Heroku Postgres and persisting the data in salesforce may not be feasible for 1 billion records. Migrating the data to big objects may incur additional costs and require custom code to use async SOQL

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.

The recommended solution to ensure long-term performance for the customer categorization process is to implement a new picklist custom field in the Account object with Gold, Silver, and Bronze values. A picklist field is a simple and efficient way to store a predefined set of values for a record. A picklist field has the following benefits:

It allows you to easily filter, sort, and group records by their category values, which can help you analyze and segment your customers.

It does not require creating any additional objects or relationships, which can reduce the data model complexity and maintenance overhead.

It supports large data volumes and can handle millions of records without affecting performance or scalability.

single-select restricted picklist with defined choices can be a way to configure customer type. The article states that picklists are fields that allow users to select one or more predefined values from a list, and restricted picklists ensure that users can only select from the defined values. This can help to limit the choices for customer type and ensure data quality.

 Setting Customer-Reference_c as an External ID (unique) is the recommended solution to ensure that support agents using global search and reports can quickly find shipment records. This is because external ID fields are indexed and can be used as filters in reports and list views4. Making the field unique also ensures that there are no duplicate values that could confuse the search results.

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.

Whether the system of record changes for different tables and the number of systems that are integrating with each other are two factors that the architect should take into consideration when deciding whether or not to use a Master Data Management system to achieve the solution of integrating data and resolving duplicates and discrepancies between Salesforce and one or more external systems. The system of record is the authoritative source of truth for a given entity or field in a given context. If different systems have different systems of record for different tables, then a Master Data Management system can help to manage and synchronize the data across systems and ensure data quality and consistency. The number of systems that are integrating with each other is another factor that affects the complexity and scalability of the integration solution. If there are many systems that need to integrate with each other, then a Master Data Management system can provide a centralized and standardized way of integrating data and resolving duplicates and discrepancies across systems. The other factors are not relevant or important for deciding whether or not to use a Master Data Management system, as they do not affect the data quality or integration challenges that a Master Data Management system can address.

  Master data management (MDM) is a solution that helps organizations manage their master data across multiple systems and ensure consistency and quality. An MDM solution can act as the customer master, with centralized integrations to other systems, to avoid data duplication and inconsistency.

An Outbound Message is a native Salesforce feature that allows sending data to an external system without code. It can be configured to include any fields from the source object3. A Field Set is a collection of fields that can be used in Visualforce pages or Apex classes to dynamically determine the fields to send in an HTTP callout. Both of these approaches meet the requirements of Cloud Kicks.

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.