Scenarios & Solutions DF3 Flashcards
(15 cards)
The system administrator of an organization has been given the task of creating a custom application in Salesforce with a number of custom objects and fields. The administrator is looking for the most efficient way to set up the data model for the application.
Schema Builder can be used to efficiently create custom objects, fields and relationships using a single user interface. It also allows viewing how the different objects are related to one another, which can be useful to understand how the data model should be set up.
A real estate company needs to store information about properties and sales deals in Salesforce.
Information about properties can be stored by creating a custom object which can be named Property. Sales deals can be stored using the standard Opportunity object.
An organization needs to relate every employee in the company to salary plans such that the salary plans of an employee are deleted when the employee leaves.
For this particular use case, a master-detail relationship field can be created on the Salary Plan object to the Employee object. Deleting an employee record would delete all the related salary plans.
A recruiting application should consist of candidates and positions such that each candidate can apply for multiple positions and each position can have multiple candidates.
A many-to-many relationship can be created for this use case using a junction object between Candidate and Position. Two master-detail relationship fields would need to be created on the junction object to the master objects.
Users of a non-profit school should be able to select a contact record on the Alumnus object that has been created to store alumni. The contact would represent the mentor of an alumnus, but the field should be optional.
For this use case, a lookup relationship to the Contact object can be created on the Alumnus object. The lookup relationship field can be made optional on the Alumnus page layout.
Each User record should allow specifying a secondary manager in cases where the primary manager of the current user is not available.
A hierarchical relationship field can be created on the User object to relate a user to another user
Each account record should be related to several child shipping records, but the child records should have distinct owners.
Lookup Relationship can be defined on the child object. Unlike a master-detail relationship, a lookup relationship does not affect the security and ownership of the child records.
Multiple interview records can be related to each candidate record, but each interview record should only be visible to the interviewer. Access to child records should be independent from access to the master record
A Lookup Relationship can be defined on the Interview object to the Candidate object. It would allow the child records to have independent access and sharing setting.
The total number of related Interview records should be summarized and displayed on each parent Candidate record. However, all the Interview records should have independent owners.
A Lookup Relationship can be utilized for this use case since the ownership of the child records should be independent. An Apex trigger or a record-triggered flow can be defined on the Interview object to calculate and update a custom field on the parent Candidate record.
It should be possible to relate multiple application records to a candidate record. All applications posted by a candidate should be deleted when the parent candidate record is deleted.
A Master-Detail Relationship can be defined on the Application object for this requirement. In a master-detail relationship, child records related to a master record are deleted when the master record is deleted.
If a recruiter can access a candidate record, then they should be able to access all the related applications submitted by the candidate. Access to applications should be determined by access to the candidate record
A Master-Detail Relationship can be used for this requirement. In a master-detail relationship, the child records inherit the security and sharing settings of the parent record, allowing users to access the child records if they can access the parent record.
An account record can be related to multiple donation records. The total number of donations made by each account should be displayed on the account record. A donation record should only be visible to a user if they can view the parent account record.
A Master-Detail Relationship can be defined for this requirement. A roll-up summary field can be defined on the Account object to summarize the related child records and display the total number of donations on each account record
Each contact record can be related to many hobby records, and each hobby can be related to many contact records
A Many-to-Many Relationship can be created between the Contact object and the Hobby object using a junction object. To define the relationship, two master-detail relationship fields can be defined on the junction object.
Each candidate record can be related to many position records and vice-versa. The total number of applications should be visible on each candidate record and each position record
A Many-to-Many Relationship can be created between the Candidate object and the Position object using a junction object and two master-detail relationships. A roll-up summary field can be defined on each master object.
A company in the real estate business needs to store the locations of their client’s properties. Then, based on that information, a virtual map needs to be generated using Apex and a frontend mapping library.
A geolocation field can be used to store the location of areal estate property. To access each coordinate, the field name plus the suffix is specified. If “Property Location” is the field name, for example, then the API names are: Property_Location__latitude__sProperty_Location__longitude__s
