SF-Data-Arch Data Modeling and Database Design Practice Test 3 — 15 Questions

Question 1

A Salesforce architect is designing a custom object called Shipment__c that must relate to both a Warehouse__c record and a Carrier__c record. The business requires that each Shipment__c must always have exactly one Warehouse__c and exactly one Carrier__c, and that deleting a Warehouse__c should not delete its shipments, but deleting a Carrier__c should delete its shipments. Which two relationship configurations should the architect use? (Choose two.)

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Create a Lookup relationship from Shipment__c to Warehouse__c and mark the lookup field as required.. The warehouse side needs a mandatory parent without cascade delete, which a required lookup provides. The carrier side needs a mandatory parent with cascade delete, which is native to master-detail. Using a required lookup for Warehouse__c and a master-detail for Carrier__c satisfies both constraints. The reversed combinations either cascade delete when they should not or fail to cascade delete when they should.

Answer

Create a Master-Detail relationship from Shipment__c to Warehouse__c and a required Lookup relationship from Shipment__c to Carrier__c.

Answer

Create a Lookup relationship from Shipment__c to Carrier__c and use a validation rule to require the carrier field.

Answer

Create a Master-Detail relationship from Shipment__c to Warehouse__c and a Lookup relationship from Shipment__c to Carrier__c.

Question 2

A Salesforce org has a custom object Order__c with 120 fields. The business wants to display a related list of Order__c records on the Account page layout, showing only the Order Number, Status, and Total Amount columns. The architect is told that the related list must be sortable by Total Amount and must not degrade page performance. Which approach should the architect recommend?

Accepted Answer

Create a custom Lightning component that queries Order__c records and displays them in a sortable table on the Account record page.. The requirement is for a related list that shows specific fields and supports sorting by Total Amount without performance degradation. A custom Lightning component can query only the needed fields and implement sorting in the client, avoiding the overhead of a standard related list on a 120-field object. Standard related lists and roll-up summaries do not provide the same combination of sortable, field-specific display and performance control.

Answer

Use a List View on the Order__c object and embed it on the Account page layout as a related list.

Answer

Add the standard Order__c related list to the Account page layout and configure the related list to show only the three required columns.

Answer

Create a roll-up summary field on Account that counts Order__c records and display the count on the Account page.

Question 3

A Salesforce administrator needs to store a list of up to 10 product codes on each Opportunity record. The product codes are used only for display and reporting, and the business does not need to query individual codes or create relationships to a Product object. Which field type should the architect recommend?

Accepted Answer

A multi-select picklist field with the product codes as values.. When you need to store a fixed set of multiple values on a single record and do not require querying individual values or creating relationships, a multi-select picklist is the appropriate field type. It provides a controlled list, supports reporting, and avoids the overhead of a child object. Text areas and number fields do not enforce valid values, and a child object is overkill for display-only data.

Answer

A text area (long) field where the administrator manually enters the product codes separated by commas.

Answer

A child custom object Product_Code__c with a master-detail relationship to Opportunity.

Answer

A number field with a formula that concatenates the product codes.

Question 4

Universal Containers requires a data model where a Child object must have exactly one Parent object that is mandatory. If the Parent is deleted, the Child must be deleted. Which relationship should the Architect select?

Accepted Answer

Master-Detail relationship. A Master-Detail relationship creates a tight coupling where the child's lifecycle is strictly governed by the parent. Deleting the parent automatically triggers a cascade delete of all associated children. This is essential for maintaining referential integrity in parent-child hierarchies where the child cannot exist in isolation, ensuring the database remains clean and logically consistent without requiring custom automation for cleanup tasks.

Answer

Lookup relationship

Answer

Self-relationship

Answer

External lookup relationship

Question 5

An organization has 50 million records in a custom object. They need to report on historical snapshots weekly. What is the best strategy to manage storage while keeping data available?

Accepted Answer

Use Big Objects. Big Objects are designed for massive scale, supporting billions of records with optimized storage costs. By moving historical snapshot data to Big Objects, the organization retains accessibility for reporting via asynchronous queries or external tools without consuming standard Salesforce storage limits. This strategy preserves database performance for the active operational records while ensuring compliance and historical availability for long-term analytical business requirements.

Answer

Use standard Salesforce objects

Answer

Move data to a sandbox

Answer

Use Platform Events

Question 6

Which TWO factors should be considered when choosing between a Master-Detail and a Lookup relationship for a new custom object? (Choose two)

Accepted Answer

Security and sharing inheritance. Choosing the correct relationship involves evaluating data ownership and security requirements. Master-Detail relationships propagate security settings from the parent to the child, which is a key architectural decision. Lookup relationships offer independent sharing, which is vital when child records should have distinct visibility regardless of the parent. Architects must weigh these against the need for cascade deletes and rollup summaries to ensure the model aligns with business processes.

Answer

The number of records

Answer

The color of the object

Answer

The API name prefix

Question 7

Which field type should be used for a primary key when integrating data from an external ERP system into Salesforce?

Accepted Answer

External ID field. External IDs are critical for data integration. By marking a field as an External ID and setting it to Unique, Salesforce enables the 'Upsert' operation. This prevents duplicate records by matching the external system's primary key to the Salesforce record, ensuring data consistency across disparate platforms. This is the standard best practice for any integration involving master data management or synchronization between external systems and Salesforce.

Answer

Text field

Answer

Auto-number field

Answer

Formula field

Question 8

A company is migrating legacy data and needs to preserve the CreatedDate and CreatedById. Which feature should they enable?

Accepted Answer

Set Audit Fields permission. By default, Salesforce sets the CreatedDate and CreatedById to the time and user of the import. To preserve historical audit logs, Salesforce provides the 'Set Audit Fields' permission. This is vital for data migration projects where historical accuracy is required for compliance and reporting. Without this, the audit trail of the legacy system is lost, which can lead to significant regulatory and reporting issues.

Answer

Data Loader batch settings

Answer

Field History Tracking

Answer

Owner migration setting

Question 9

Which indexing strategy is best to improve performance for queries on a field used in multiple filters?

Accepted Answer

Create a custom index. Custom indexes are necessary when standard indexing is insufficient for complex filtering. By creating a custom index on high-cardinality fields used in 'WHERE' clauses, the optimizer can skip full table scans, drastically reducing query time. This is critical in large data volumes where even a small performance improvement in query speed can make the difference between a successful report and a timeout failure.

Answer

Use a formula field

Answer

Use a text area field

Answer

Use a standard lookup

Question 10

When designing a data model for a multi-region deployment, what is the best way to handle global picklist values?

Accepted Answer

Use Global Value Sets. Global Value Sets allow for centralized management of picklist values across multiple objects and regions. This ensures consistency in reporting and data entry, as the same set of values is used consistently. If a value needs to be updated, it only needs to be changed in one place, which reduces the risk of data inconsistency and makes the maintenance of global data models much more efficient.

Answer

Copy values to every object

Answer

Use a custom metadata type

Answer

Use a text field

Question 11

Universal Containers wants to track complex relationships between Accounts where one Account can be a subsidiary of many others, and an Account can have many parent companies. Which modeling approach should the Architect recommend?

Accepted Answer

Implement a custom junction object with two lookup fields to the Account object.. Many-to-many relationships are best handled using a junction object in Salesforce. By creating a custom object, you can link two Account records while storing additional metadata like the nature or duration of the relationship. This approach overcomes the limitations of standard lookup fields, which only support one-to-many structures, ensuring data integrity and allowing for robust reporting across complex corporate hierarchies.

Answer

Add multiple self-lookup fields on the Account object.

Answer

Create a Text field to store a comma-separated list of parent IDs.

Answer

Use a master-detail relationship between the Account and a custom object.

Question 12

Refer to the exhibit. The Data Architect is tasked with ensuring that order status options are limited based on the geographic region of the order. Which feature should be used to implement this?

Accepted Answer

Dependent Picklists.. Dependent picklists are the standard Salesforce mechanism for limiting the values of one picklist based on the selection of another. By defining a controlling field (Region) and a dependent field (Status), the architect ensures data entry accuracy and prevents invalid combinations of status and geography from being saved, which is vital for regional reporting and process consistency.

Answer

Record Types.

Answer

Validation Rules.

Answer

Custom Metadata Types.

Question 13

A Data Architect is analyzing a legacy system migration. Which THREE factors should be evaluated before deciding between a Lookup or a Master-Detail relationship?

Accepted Answer

Whether child records should be automatically deleted if the parent is deleted.. Choosing the right relationship is foundational to Salesforce architecture. Factors like data ownership, lifecycle dependency, and reporting needs drive the decision. A Master-Detail relationship implies structural dependency, while a Lookup offers flexibility. Understanding these nuances early in the migration prevents architectural debt, ensures correct security enforcement, and aligns the data model with the organization's business process requirements for record access and summarization.

Answer

The number of child records expected to be created.

Answer

The color of the record detail page header.

Question 14

An architect is building a data model for a subscription service. They need to calculate the total revenue across all related 'Invoice' records for an 'Account'. Which approach should they use?

Accepted Answer

Use a Roll-up Summary field on the Account object.. Roll-up summary fields are the native, declarative way to perform aggregate calculations across master-detail relationships. They are highly efficient, automatically updated by the platform, and require no code. This ensures the revenue data is always accurate and available for reporting, dashboards, and list views, which is essential for sales teams tracking customer lifetime value.

Answer

Write a Trigger to calculate and update the total on the Account.

Answer

Create a Flow that triggers on every Invoice insert.

Answer

Calculate the revenue dynamically using a Formula field.

Question 15

Refer to the exhibit. The query is part of a bulk apex process. What is the potential risk with this query in a large-scale data environment?

Accepted Answer

The query will hit governor limits if the result set is too large.. The primary risk is hitting the SOQL 'Too many query rows' limit or 'CPU time' limit when joining large related datasets. While the query looks standard, processing the nested collection of contacts for 50,000 accounts can consume significant memory and CPU cycles. Architects must implement batching and pagination to ensure the process remains within governor limits and provides stable performance.

Answer

The query fails because nested SOQL is not supported.

Answer

The query will cause a SOQL injection vulnerability.

Answer

The query is invalid because it misses the 'FROM' clause.