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.

Explanation:

UC’s IoT solution requires storing and accessing frequent temperature and humidity updates for 10,000 (eventually 50,000) containers in Salesforce. The solution must handle high data volume, ensure scalability, and provide access to both current and historical data. A master-detail relationship with an archiving strategy is ideal to manage data growth efficiently while maintaining performance and meeting user requirements for data access.

Correct Option:

✅ D. 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 uses a Container Reading object to store frequent updates, linked via a master-detail relationship to the Container object, ensuring data integrity and scalability. The hourly archiving process manages data volume by moving older records out of active storage, maintaining performance while preserving historical data access for 50,000 containers.

Incorrect Options:

❌ A. Create new custom fields for temperature and humidity in the existing Container custom object, as well as an external ID field that is unique for each container. These custom fields are updated when a new measure is received.
Storing frequent updates (every 10 minutes) in custom fields on the Container object would overwrite historical data, preventing access to past readings. This approach is unsuitable for UC’s need to track historical trends and handle the growing data volume from 50,000 containers.

❌ B. Create a new Container Reading custom object, which is created when a new measure is received for a specific container. The Container Reading custom object has a master-detail relationship to the container object.
While a Container Reading object with a master-detail relationship is appropriate, this option lacks an archiving strategy. Without archiving, the high volume of data (every 10 minutes for 50,000 containers) could degrade performance over time, making it less effective for UC’s long-term needs.

❌ C. Create a new Lightning Component that displays last humidity and temperature data for a specific container and can also display historical trends obtaining relevant data from UC’s existing data warehouse.
A Lightning Component focuses on display, not data storage. Relying on an external data warehouse for historical data introduces complexity and latency, and doesn’t address how to store or manage frequent updates within Salesforce, failing to meet UC’s requirement for integrated data access.

Reference:
Salesforce Help: Master-Detail Relationships
Salesforce Help: Data Archiving

RecordType

CustomField

Explanation:

Data architecture focuses on how data is structured, stored, related, and governed within an organization. Therefore, the documentation must include metadata types that define the core structure and behavior of data.

Why A is Correct (RecordType):
Record Types control the business processes, page layouts, and picklist values available to a user for a specific record. They are a crucial part of data architecture as they define how different data segments are presented and managed within the same object. Documenting which Record Types exist and their criteria is essential for understanding data flow and user interaction.

Why C is Correct (CustomField):
Custom Fields are the fundamental building blocks of custom data structures in Salesforce. They define the attributes and data points (e.g., text, number, date, relationship) stored for each record. Documenting all Custom Fields, their data types, and their relationships is the very core of data architecture documentation.

Why B is Incorrect (Document):
The "Document" metadata type refers to files stored in the Documents tab, which are used for branding (like images for email templates) or other static file storage. While important for an organization, these are content files, not structural elements of the data model, and are not a primary concern for data architecture documentation.

Why D is Incorrect (SecuritySettings):
While security is intrinsically linked to data (governing who can see what), Security Settings (e.g., password policies, network access) are part of the application's security and access architecture, not its data architecture. The data architecture document would reference security in the context of field-level security or sharing rules, not these org-wide settings.

Reference:
The core of the Data Architect exam revolves around data modeling, which is defined by objects (standard and custom), fields (standard and custom), and relationships. Record Types and Custom Fields are primary components of this model.

Explanation:

Defining data quality standards for a complex Salesforce org with issues like incomplete and duplicate data requires focusing on metrics and rules that directly address data integrity, usability, and reliability. Let’s analyze each option to identify the three key factors:

✅ Option A: Define data duplication standards and rules
This is a critical factor. Duplicate data is a common issue in Salesforce orgs and directly impacts user experience, reporting accuracy, and system performance. Defining standards and rules for identifying, preventing, and resolving duplicates (e.g., using matching rules, duplicate rules, or third-party tools like Data.com Dupeblocker) is essential for maintaining data quality. This addresses one of NTO’s primary complaints.

Option B: Define key fields in staging database for data cleansing
While a staging database can be useful for data cleansing in migration or integration scenarios, it is not a core component of defining data quality standards within the Salesforce org. Staging databases are typically part of implementation processes, not ongoing data quality management. This option is less relevant to the goal of establishing standards for the existing org’s data issues.

✅ Option C: Measure data timeliness and consistency
Data timeliness (ensuring data is up-to-date) and consistency (ensuring data aligns across objects and systems) are key data quality metrics. For example, outdated records or inconsistent data between related objects (e.g., Accounts and Contacts) can lead to user dissatisfaction and errors in reporting. Measuring these factors helps NTO ensure data remains relevant and reliable, addressing user complaints about data issues.

Option D: Finalize an extract transform load (ETL) tool for data migration
While ETL tools are valuable for data migration or integration, selecting a tool is a tactical decision, not a factor in defining data quality standards. ETL tools may be used to implement data quality processes, but the question focuses on defining standards, not choosing tools.

✅ Option E: Measure data completeness and accuracy
This is another critical factor. Incomplete data (e.g., missing required fields) and inaccurate data (e.g., incorrect values) are explicitly mentioned as issues by NTO’s users. Measuring completeness (ensuring all necessary fields are populated) and accuracy (ensuring data reflects reality) is fundamental to establishing data quality standards and improving user trust in the system.

✅ Why A, C, and E are Optimal:
These three factors directly address NTO’s data quality issues (incomplete and duplicate data) and align with standard data quality frameworks. Defining duplication standards (A) tackles duplicate records, measuring timeliness and consistency (C) ensures data is current and coherent, and measuring completeness and accuracy (E) addresses missing or incorrect data. Together, these form a comprehensive approach to defining data quality standards for the Salesforce org.

References:
Salesforce Documentation: Duplicate Management
Salesforce Architect Guide: Data Quality
Salesforce Help: Data Quality Best Practices

Configure territory management feature to support opportunity assignment.

Explanation:

The requirement describes a classic hierarchical territory model with two tiers (Zip Code -> Sales Area) and a many-to-many relationship between users and territories. This is the exact purpose of Salesforce's built-in Territory Management feature.

Option D (Correct): Territory Management is a native Salesforce feature designed for complex, hierarchical sales models. It allows you to:

✔️ Define territories based on criteria (e.g., Zip Code).
✔️ Aggregate those territories into larger areas (e.g., Sales Area).
✔️ Assign multiple users to a single territory and multiple territories to a single user.
✔️ Automatically assign opportunity ownership based on territory criteria (e.g., the Zip Code field).
✔️ Report on performance by territory and sales area effortlessly.

Option B: While assignment rules can assign records based on field values, they are not designed for a hierarchical model. Managing 1,000+ rules for each zip code and maintaining the hierarchy for reporting would be an administrative nightmare and is not scalable.

Option A & C: These are entirely manual processes. They are error-prone, not scalable, and do not automate the assignment as required. They also fail to provide the built-in hierarchical reporting structure that Territory Management offers.

Reference:
Salesforce Help: Get Started with Territory Management
Trailhead: Manage Your Sales Territory

Lighting platform plus

Explanation:

The requirement is for internal users (finance team) to access a custom object and perform tasks beyond just viewing, such as reporting and adjusting records ("adjusting employee utilization"). They do not need access to standard Sales or Service objects. Platform licenses are designed for this exact scenario: building custom apps for users who don't need full CRM functionality.

Correct Option

D. 🟩 Lighting platform plus:
The Lightning Platform Plus license provides full access to custom objects and the ability to create and run custom reports. It is the minimum-cost license that provides the edit capabilities ("adjusting") required by the finance team, making it the most appropriate and cost-effective choice.

Incorrect Options

A. 🟥 Service Cloud & B. 🟥 Sales Cloud:
These are full CRM licenses. They include access to all standard Sales and Service objects (like Leads, Opportunities, Cases), which the requirement explicitly states the finance team does not need. Using these licenses would be over-provisioning and unnecessarily expensive.

C. 🟥 Light Platform Start (now Platform Starter):
The Platform Starter license is highly restricted. It is typically intended for external users (e.g., Customer Community) and has significant limitations, such as read-only access to custom objects and very limited reporting capabilities. It does not support the "adjusting" (edit) requirement.

Reference
Salesforce Help: Compare Lightning Platform Packages