Universal Containers decides to use exclusively declarative development to build out a new Salesforce application. Which three options should be used…

The database layer in a Salesforce application refers to the data model, which is the structure that holds the application's data. In a declarative model, this structure is built using point-and-click tools.

1. Custom objects and fields are the foundational elements, analogous to tables and columns in a traditional database.

2. Relationships (e.g., Master-Detail, Lookup) are crucial for defining how objects connect and relate to one another, forming the relational structure of the database.

3. Roll-up summaries are special fields on a master object that aggregate data from related detail records. They are a declarative part of the data model as they define a calculated value stored directly on the object.

1. Salesforce Trailhead

Module: Data Modeling: This module explicitly defines the Salesforce data model as being composed of objects

fields

and relationships. It states

"A data model is basically a collection of objects and fields in an app... But it’s also important to understand the different types of relationships you can create between objects." This directly supports options A and D.

2. Salesforce Help

Article: Roll-Up Summary Field: This documentation describes a roll-up summary field as a field that "calculates values from related records." As it is a type of field

it is an integral

declarative component of an object's definition and thus part of the database layer. This supports option C.

3. Salesforce Architects

"Well-Architected - Data-Driven": The framework discusses the data model (objects

fields

relationships) as the foundation. It separates this data layer from the logic layer

where tools like Flow and Apex Triggers operate to enforce business rules and automation. This reference clarifies the distinction between the database layer (A

C

D) and the logic layer (B

E).