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

Question 1

An architect is designing a schema to store product information. Each product has many versions, and each version has many components. What is the most efficient way to model this relationship?

Accepted Answer

Model as three separate objects with Master-Detail relationships.. Creating a hierarchical relationship using lookup or master-detail fields on 'Product', 'Version', and 'Component' objects is the most scalable way to represent this structure. By isolating each layer, the architect ensures that reporting, security, and maintenance are simplified. This hierarchical model is cleaner than attempting to flatten the data, as it preserves parent-child integrity at every level.

Answer

Flatten everything into one giant object with 100+ custom fields.

Answer

Use a JSON field to store the hierarchy as a string.

Answer

Create a separate object for every possible component.

Question 2

An enterprise architect is evaluating data storage strategies for a telecommunications client experiencing rapid data growth of fifty million call detail records annually. Which TWO strategies should the architect implement to maintain database query performance and platform data limits? Choose 2 answers.

Accepted Answer

Utilize Salesforce Big Objects to store historical call records asynchronously and index primary lookup keys.. When dealing with massive data volumes exceeding standard transactional limits, traditional custom objects will quickly degrade platform performance and storage capacity. Offloading historical analytical data to Salesforce Big Objects or external systems via Salesforce Connect preserves core transactional limits. Additionally, implementing strict data archiving strategies prevents data skew and maintains query optimization.

Answer

Store the call detail records in standard custom objects with indexes applied to all foreign keys.

Answer

Create hierarchical custom object structures linking every call record directly to the Account master object.

Answer

Rely on standard Salesforce report archives to automatically move historical records out of reporting tables.

Question 3

Universal Containers notices severe locking issues and transaction failures when updating a parent Account object that has over 15,000 child records in a master-detail relationship. What is the fundamental architectural cause of this behavior?

Accepted Answer

Parent-level database locks occur and cascade down to evaluate child records, causing row-level contention.. Master-detail relationships enforce strict parent-level locking during record saves to maintain relational integrity and roll-up summary calculations. When a parent record is updated, the platform locks the parent and cascades lock checks across associated child records. Having thousands of children spikes the probability of database contention, leading directly to row-level locking exceptions and transaction failures.

Answer

The platform automatically generates criteria-based sharing recalculations for every child record.

Answer

Custom triggers on the child object execute recursively because of the master-detail cascading save mechanism.

Answer

Roll-up summary fields exceed maximum calculation limits when evaluating more than 10,000 records.

Question 4

An administrator wants to convert an existing custom lookup relationship on the 'Project' object pointing to the 'Client' object into a master-detail relationship. Which precondition must be satisfied before this conversion can be completed successfully?

Accepted Answer

All existing child records must have a non-null value populated in the lookup field.. Converting a lookup relationship to a master-detail relationship requires that every existing child record currently in the database possesses a populated, valid value for the lookup field. If any orphan records exist where the lookup field is blank, the database cannot establish the mandatory parent-child integrity required by master-detail semantics, causing the conversion operation to fail.

Answer

The parent object must have fewer than 10,000 child records associated with it.

Answer

The organization-wide default for the child object must be set to Public Read/Write.

Answer

All custom reporting types referencing the objects must be temporarily deleted prior to conversion.

Question 5

Universal Containers requires a many-to-many relationship between Projects and Consultants. They need to track specific attributes like 'Hourly Rate' and 'Assigned Role' on the relationship itself. Which approach should a Data Architect recommend?

Accepted Answer

Implement a custom object that serves as a junction object between Projects and Consultants.. A Junction Object is the standard Salesforce solution for many-to-many relationships. By creating a custom object between Projects and Consultants, the architect can include extra fields to store metadata about the assignment. This design ensures referential integrity, enables robust reporting across both parent objects, and allows for security modeling via Master-Detail or Lookup relationships, which is essential for complex consulting resource management.

Answer

Create a multi-select picklist on the Project object containing all available Consultants.

Answer

Add a lookup field on the Project object pointing to the Consultant object.

Answer

Use a custom metadata type to map consultants to projects.

Question 6

A Data Architect is designing a high-volume data model where an Account has millions of Child records. Which TWO strategies should be implemented to ensure optimal performance and avoid data skew?

Accepted Answer

Ensure that the owner of the parent records is not a single user or small group.. Performance issues in Salesforce often arise from data skew, where a small number of parent records own a vast majority of child records. Implementing strategies like record ownership distribution and utilizing indexing on high-cardinality fields prevents row-level locking contention. These design patterns are critical for maintaining query performance and ensuring that API operations do not time out during large-scale data processing or complex analytical reporting cycles.

Answer

Convert all Lookup relationships to Master-Detail relationships to improve query speed.

Answer

Avoid using custom indexes on fields that have high cardinality.

Answer

Avoid creating parent-child relationships where the parent is a 'Person Account'.

Question 7

Refer to the exhibit. An architect needs to track changes to the 'Status__c' field for auditing purposes. Based on the configuration provided, what is the best way to report on the duration a record spent in each status?

Accepted Answer

Create a custom object to store status change logs with entry and exit timestamps.. Standard Field History Tracking records changes but does not store the duration between states effectively for analytics. Creating a secondary 'Audit' object that captures snapshots of status changes via a record-triggered flow is the best approach. This allows the architect to calculate intervals between timestamps using reporting tools or custom formulas, providing the necessary visibility into business process bottlenecks that native history tables cannot easily compute.

Answer

Use the built-in Field History report type.

Answer

Enable 'Custom History Tracking' in the Setup menu.

Answer

Use a formula field to calculate the duration.

Question 8

An organization wants to use 'Person Accounts' to manage B2C relationships. Which consideration is most important for a Data Architect when evaluating this change?

Accepted Answer

They fundamentally change the object model and are non-reversible.. Person Accounts merge the Account and Contact models into a single entity, which has long-term implications for the data schema. Once enabled, this change cannot be reversed, and it impacts existing integrations, custom code, and reporting. A Data Architect must ensure that all third-party systems are updated to handle the new object structure, as the standard Account-Contact hierarchy is fundamentally altered, potentially breaking legacy processes that expect distinct objects.

Answer

Person Accounts can be disabled by contacting Salesforce Support.

Answer

They replace the need for custom objects for B2C data.

Answer

They require a Business Account for every Person Account.

Question 9

When designing a custom Data Model, when should an architect choose a 'Lookup' relationship over a 'Master-Detail' relationship?

Accepted Answer

When the child record must have its own sharing settings.. Lookup relationships offer flexibility where the parent and child records are logically distinct and can exist independently. This is ideal for scenarios where sharing is decoupled or when the child records should not be deleted upon parent deletion. By understanding these nuances, an architect avoids the 'cascading' consequences of Master-Detail relationships, which is vital for designing a loosely coupled, maintainable system that satisfies complex business requirements without unnecessary record interdependencies.

Answer

When the child records must inherit the parent's security.

Answer

When the child must be deleted when the parent is deleted.

Answer

When you need to create a Roll-up Summary field.

Question 10

An architect is modeling a 'Subscription' service where Customers have multiple active subscriptions. Which approach best handles the 'Current' vs 'Historical' subscription data for reporting?

Accepted Answer

Use a single object with 'Status' and 'Date' fields.. Using a combination of a status field and a date range is the standard way to model active versus historical subscriptions. By flagging records as 'Active' and using the 'End Date' field, the architect allows the system to easily filter for current records while maintaining a full history. This design supports both operational reporting and long-term analytical tracking, which is essential for subscription-based business models.

Answer

Use two separate objects for Current and Historical subscriptions.

Answer

Delete historical records to save storage space.

Answer

Use a multi-select picklist to track history.

Question 11

Refer to the exhibit. The architect observes this error during bulk Opportunity updates. Which action resolves the issue while adhering to best practices?

Accepted Answer

Move the query outside the loop and store results in a Map.. The error indicates a SOQL query inside a loop, a common mistake in bulk operations. Moving the query outside the loop into a Map or List ensures that data is retrieved in a single call, optimizing performance and staying within governor limits. This is a crucial skill for architects to ensure that data models remain performant when processing high volumes of records in automated triggers.

Answer

Increase the SOQL query limit by contacting Salesforce Support.

Answer

Add a static variable to track if the query has been executed.

Answer

Change the trigger to run in a 'without sharing' context.

Question 12

A company requires a data model to track 'Training Sessions' (which have many attendees) and 'Employees' (who attend many sessions). Which relationship is required to model this correctly?

Accepted Answer

A junction object with two Master-Detail relationships.. A many-to-many relationship is required to associate multiple Employees with multiple Training Sessions. This is implemented via a junction object. This pattern is fundamental in relational database design, as it resolves circular dependencies and allows for granular tracking of attendance, grades, or completion status per individual pairing, which cannot be achieved using simple lookups or single-parent structures on the employee or session records.

Answer

A Lookup relationship from Employee to Training Session.

Answer

A Master-Detail relationship on the Employee object.

Answer

A multi-select picklist on the Employee object.

Question 13

Which design approach is best for handling a 'Data Warehouse' requirement within Salesforce when dealing with millions of records?

Accepted Answer

Implement Big Objects for high-volume storage.. For high-volume data, architects should utilize Big Objects or External Objects to prevent hitting platform storage limits and performance degradation. Big Objects are specifically designed to store and query massive amounts of data efficiently. This strategy is vital for data management, as it keeps the core CRM performance high while still maintaining accessibility to historical archives needed for operational reporting or compliance purposes.

Answer

Use standard objects and archive periodically.

Answer

Store all data in a single custom object.

Answer

Use a custom field to store external reference IDs.

Question 14

Universal Containers maintains a custom object, Shipment__c, that has a Master-Detail relationship to Account and a Lookup to Carrier__c. A Data Architect is asked to design a new object, Shipment_Line__c, that must always belong to exactly one Shipment__c, must inherit Shipment__c's sharing rules, and must not be independently owned by a different user. Which relationship type should be used between Shipment_Line__c and Shipment__c?

Accepted Answer

Master-Detail, with Shipment__c as the master and Shipment_Line__c as the detail.. The requirement is true containment with inherited sharing and no separate ownership. A Master-Detail relationship enforces that the detail cannot exist without the master, rolls up the master's sharing and organization-wide defaults, and ties the detail's ownership to the master. A required lookup can approximate containment but leaves the child independently owned and separately shared, which violates the stated constraints.

Answer

Hierarchical relationship, using the User object to control ownership and access to Shipment_Line__c.

Answer

Lookup, with a required field to Shipment__c and a sharing rule that grants access based on the Shipment__c owner.

Answer

Self-relationship on Shipment__c, with a field pointing to the parent Shipment__c record.

Question 15

A large university is modeling academic records in Salesforce. Each Course can be taught by multiple Instructors, and each Instructor can teach multiple Courses. The university must report on the aggregate number of Courses each Instructor is teaching per semester and enforce that an Instructor cannot be assigned to the same Course twice within the same semester. Which data modeling approach should the architect implement?

Accepted Answer

Create a junction object Course_Instructor__c with two Master-Detail relationships (to Course and Instructor) plus a semester field, and configure a unique composite key across Course, Instructor, and Semester.. A junction object with two Master-Detail relationships is the standard Salesforce pattern for many-to-many relationships, and it enables roll-up summary fields on both parents. Adding a semester field and a unique composite key satisfies the duplicate-prevention rule. Reciprocal lookups, asymmetric relationships, and multi-select picklists cannot simultaneously support per-assignment attributes, aggregate reporting, and uniqueness enforcement.

Answer

Store Instructor assignments as a multi-select picklist on the Course object and use a formula field to count selections.

Answer

Create a Lookup relationship from Course to Instructor and from Instructor to Course, then build a report to deduplicate overlapping assignments.

Answer

Create a single Course_Instructor__c object with a Master-Detail to Course and a Lookup to Instructor, then use a validation rule to count existing records.