Salesforce Data-Architect - Salesforce Certified Data Architect (SP25)

Option B is correct because data model is a key artifact that an architect should use to document the data architecture for a multi-system, enterprise Salesforce implementation1. Data model describes the structure and relationship of data entities within an organization2. Option C is correct because integration specification is another key artifact that an architect should use to document the data architecture for a multi-system, enterprise Salesforce implementation1. Integration specification defines the scope, requirements, design, testing, and deployment of integration solutions between Salesforce and other systems3. Option A is not correct because user stories are not key artifacts for documenting the data architecture, but agile development tools that capture the features and functionalities that users want from a system4. Option D is not correct because non-functional requirements are not key artifacts for documenting the data architecture, but quality attributes that specify how well a system performs its functions.

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.

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

According to the Salesforce documentation, a relationship field is a field that allows linking one object to another object in Salesforce. There are different types of relationship fields that have different characteristics and behaviors, such as master-detail, lookup, indirect lookup, external lookup, etc.

To recommend a type of relationship field for this scenario, where legacy inventory data will be stored in a custom child object called Inventory__c, inventory data should be related to the standard Account object, the Inventory__c object should inherit the same sharing rules as the Account object, and anytime an Account record is deleted in Salesforce, the related Inventory__c record(s) should be deleted as well, a data architect should recommend:

Master-detail relationship field on Inventory__c, related to Account (option B). This means creating a field on the Inventory__c object that references the Account object as its parent. A master-detail relationship field establishes a parent-child relationship between two objects, where the parent object controls certain behaviors of the child object. For example, a master-detail relationship field can:

Inherit the sharing and security settings from the parent object to the child object. This means that the users who can access and edit the parent record can also access and edit the related child records.

Cascade delete from the parent object to the child object. This means that when a parent record is deleted, all the related child records are also deleted.

Roll up summary fields from the child object to the parent object. This means that the parent object can display aggregated information from the child records, such as count, sum, min, max, or average.

Master-detail relationship field on Account, related to Inventory__c (option A) is not a good solution, as it reverses the direction of the relationship. This means creating a field on the Account object that references the Inventory__c object as its parent. This is not possible, as a standard object cannot be on the detail side of a master-detail relationship. Indirect lookup relationship field on Account, related to Inventory__c (option C) is also not a good solution, as it is a special type of relationship field that allows linking a custom object to a standard object on an external system using an indirect reference. This is not applicable for this scenario, as both objects are in Salesforce and do not need an external reference. Lookup relationship field on Inventory__c related to Account (option D) is also not a good solution, as it establishes a looser relationship between two objects than a master-detail relationship. A lookup relationship field does not inherit sharing and security settings from the parent object to the child object, does not cascade delete from the parent object to the child object, and does not roll up summary fields from the child object to the parent object.

 According to this article, big objects can store and manage massive amounts of data on the Salesforce platform. This can help UC to archive records from other objects or bring massive datasets from outside systems into a big object. According to this article, Einstein Analytics can be used to create dashboards and lenses to analyze big object data and get insights from advanced AI-driven analytics.

Option D is correct because data flows should be reviewed with the business users to determine the system of record per object or field1. The system of record is the authoritative source of data for a given entity or attribute2. It may vary depending on the business context and requirements. Option A is not correct because account and opportunity data originates in Salesforce, but it may not be the system of record for all attributes or objects if they are updated by other systems2. Option B is not correct because whatever system updates the attribute or object may not be the system of record for that field or object if there are conflicting or overlapping updates from other systems2. Option C is not correct because whatever integration data flow runs last may not determine which system is the system of record if there are different business rules or logic applied by different systems2.

 The Data Architect should consider the limitations on Org data storage and the Bulk API limitations on picklist fields when denormalizing the data model into a single Transaction object with a Branch Office picklist. The Org data storage limit is the total amount of data that can be stored in a Salesforce Org, and it depends on the edition and license type of the Org1. The Bulk API limit on picklist fields is the maximum number of values that can be imported or exported using the Bulk API, and it is 1,000 values per picklist field2. These limitations could affect the performance and scalability of the data model, and the Data Architect should plan accordingly.

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.

Salesforce Connect is a feature that allows users to access data from external sources and multiple Salesforce orgs, using either clicks or code. Salesforce Connect can provide read-only access to customer records across all NTO orgs, without replicating or storing the data in Salesforce.

The correct answer is A, global unique customer number. A global unique customer number is a data element that can uniquely identify each customer across different systems. It can be used as a key to link customer records from different sources and enable reporting across these systems. Email address, phone number, and full name are not reliable or consistent identifiers for customers, as they can change over time or be shared by multiple customers.