Terms you need to know

1. What is a Master-Detail Relationship?

A master-detail relationship is a configuration that creates a tightly bound connection between two objects, establishing a hierarchy where one object acts as the master and the other as the detail. In this relationship, the detail record is dependent on the master record, meaning that if the master record is deleted, all associated detail records are automatically deleted as well (a concept known as a cascading delete).

2. What is the Schema Builder?

The Schema Builder is a tool accessible via the Object Manager that provides a visual map of your Salesforce data architecture. It allows administrators to see the structure and connections of both standard and custom objects at a glance and offers an interactive interface to identify existing relationships, create new custom objects and fields, and adjust object configurations using drag-and-drop functionality.

3. What is a Dynamic Form?

A Dynamic Form is a feature within the Lightning App Builder that allows administrators to make a record page dynamic by breaking up the traditional monolithic “Record Detail” block. It enables you to place individual fields and sections anywhere on the page and control their visibility based on specific conditions, ensuring users see only the information they need based on the status or context of the record,.

4. What is the Lightning App Builder?

The Lightning App Builder is a point-and-click tool that enables administrators to create and customize pages for the Lightning Experience and the Salesforce mobile app. It provides a flexible, drag-and-drop interface used to build responsive applications, including custom Home pages, App pages, and Record pages tailored to specific business needs.

5. What is a Lookup Relationship?

A lookup relationship is a connection between two objects where the records are loosely coupled, meaning they can exist independently of one another. Unlike master-detail relationships, if a parent record is deleted in a lookup relationship, the child record remains in the system, though the link to the parent is broken (unless specific deletion behaviors are configured),.

Realtime Interview Questions

1. I need to track a relationship where deleting an Account record automatically deletes all related ‘Invoice’ records. Which relationship type should I choose, and are there any specific field limitations I should be aware of?

You should configure a Master-Detail Relationship. In this relationship, the “Invoice” would be the detail (child) and the “Account” would be the master (parent). This enforces a cascading delete, meaning if the master is deleted, the detail records are also removed. Regarding limitations, the detail record must have a parent associated with it (it cannot be an orphan), and standard objects cannot be on the detail side of a custom object in a master-detail relationship.

2. We have a scenario where a single ‘Candidate’ can apply to multiple ‘Job Positions,’ and a single ‘Job Position’ can have multiple ‘Candidates.’ How do we architect this in Salesforce?

This requires a Many-to-Many Relationship. You cannot link these two objects directly with a single relationship field to achieve this. Instead, you must create a Junction Object (e.g., “Job Application”) that sits between them. This junction object will have two Master-Detail relationships: one linking to “Candidate” and the other to “Job Position.” This structure allows you to connect one record from either side to multiple records on the other.

3. If I delete a parent record in a Lookup relationship, what happens to the child records? Can I configure this behavior?

In a Lookup Relationship, the child records are not automatically deleted when the parent is deleted; they are loosely coupled. However, you can configure the behavior. Salesforce allows you to specify whether to clear the lookup field (set it to null) on the child record or to block the deletion of the parent record entirely if child records exist. This ensures data integrity based on your business needs.

4. I need to calculate the total value of all ‘Closed Won’ opportunities on an Account record without using code or Flows. How do I achieve this?

You would use a Roll-Up Summary field. This field type is available only on the master side of a Master-Detail relationship (and certain standard relationships like Account-Opportunity). You can configure it to calculate the Sum, Minimum, Maximum, or Count of related detail records. In this case, you would define a Roll-Up Summary on the Account object that sums the “Amount” field of related Opportunities, adding a filter criteria to include only those with a “Closed Won” stage.

5. What is the difference between a Formula field and a Roll-Up Summary field?

A Formula field calculates a value using data from the same record or from related parent records (via lookup/master-detail). It is read-only and updates dynamically when source fields change. A Roll-Up Summary field, on the other hand, aggregates data from related child records (e.g., sum of all child record amounts). Crucially, Roll-Up Summaries are only available in a Master-Detail relationship (or specific standard relationships), whereas Formula fields can be used on any object.

6. We accidentally deleted a custom field from the Opportunity object yesterday. Is the data lost forever?

Not immediately. When you delete a field, it goes into a “soft delete” state for 15 days. During this period, you can restore the field and its data using the Undelete button in the Deleted Fields section. However, if you click “Erase” or if the 15-day period expires, the field and its data are permanently hard-deleted and cannot be recovered.

7. We need to ensure that when a user selects ‘Honda’ as the Car Make, the Model picklist only shows ‘Civic’ or ‘Accord’, not ‘Mustang’. How do we set this up?

You need to define a Field Dependency. You will set the “Car Make” as the Controlling Field and the “Model” as the Dependent Field. In the Field Dependency matrix, you can then select which Model values (e.g., Civic, Accord) are included or excluded for each specific Make value. Note that standard picklists can be controlling fields but cannot be dependent fields.

8. I need to generate a unique ID for every support ticket formatted like ‘TKT-0001’, ‘TKT-0002’, etc. Users should not be able to edit this.

You should use the Auto Number field type. This system-generated field automatically assigns a sequential number to each new record based on a display format you define (e.g., TKT-{0000}). It creates a unique identifier without requiring user input and is inherently read-only, ensuring consistency across your records.

9. We want to track the history of changes made to the ‘Amount’ and ‘Stage’ fields on Opportunities. Where do I configure this?

You use the Set History Tracking button on the Object Manager. After enabling history tracking for the object, you can select up to 20 specific fields (like Amount and Stage) to track. Once configured, you must add the Field History related list to the object’s page layout so users can view the audit trail of who changed what, when, and the old/new values.

10. Can I make a standard field like ‘Industry’ on the Account object a dependent picklist?

You can use a standard picklist as a Controlling Field, but a standard picklist cannot be a Dependent Field. If you need “Industry” to depend on another value, that is not possible with standard functionality. However, you could use “Industry” to control the values available in a custom picklist field.

11. Our Sales team and Renewal team work on the same Opportunity object but need different sales stages and different fields visible. How do I handle this?

You should implement Record Types combined with Sales Processes. First, create two Record Types (e.g., “New Business” and “Renewal”). Create separate Sales Processes to define the specific picklist values (Stages) available for each. Then, create two distinct Page Layouts, customizing the fields visible for each team. Finally, assign the appropriate Page Layout and Sales Process to each Record Type and assign the Record Types to the respective user Profiles.

12. I want to make the ‘Social Security Number’ field read-only on the Contact page layout, but I don’t want to change the user’s profile permissions. How can I do this quickly?

You can set the field to Read-Only directly within the Enhanced Page Layout Editor. By clicking the wrench icon (properties) next to the field on the layout, you can check the “Read-Only” box. This enforces the setting at the page layout level without altering the field-level security in the user’s profile, although Field-Level Security (FLS) is generally the more secure, restrictive method.

13. We have a custom button that generates a PDF. How do I add this to the Salesforce mobile app action bar?

In the Enhanced Page Layout Editor, you must navigate to the Mobile & Lightning Actions section. From there, drag your custom button (if it’s a quick action or compatible button) into the “Salesforce Mobile and Lightning Experience Actions” section of the layout. Actions in this specific section determine what appears in the mobile app and the Lightning header.

14. I want to display a list of related ‘Cases’ on the Account page, but I want to customize which columns appear in that list. Where is that setting?

You configure this in the Related Lists section of the Enhanced Page Layout Editor. Click the wrench icon on the specific related list (e.g., Cases). This opens a properties window where you can select and order the Selected Fields (columns) that display. You can also configure which buttons are available on that related list.

15. How can I group fields into collapsible sections on a record page to make it easier for users to navigate?

In the Enhanced Page Layout Editor, you can drag a Section element from the palette onto the layout. You can then name the section, determine if it displays the header on the Detail or Edit page, and choose a 1-Column or 2-Column layout. You can then drag related fields into this section, allowing users to expand or collapse it as needed.

16. What is the difference between a Page Layout and a Lightning Record Page?

A Page Layout controls the organization of fields, related lists, and buttons. A Lightning Record Page is a wrapper that houses the page layout (often via the Record Detail component) but adds significant flexibility. With Lightning Record Pages, you can use the Lightning App Builder to add standard and custom components (like Report Charts, Twitter feeds, or Flows), organize them into tabs or columns, and control component visibility dynamically.

17. We want to show a warning message on the Opportunity page, but ONLY if the ‘Amount’ is greater than $1 million. How can we do this without code?

You can use Component Visibility filters in the Lightning App Builder. You would add a Rich Text component containing your warning message to the page. Then, in the component’s properties, set a Visibility Rule where the filter criteria is “Amount > 1,000,000”. The component will effectively be hidden unless that criteria is met on the record.

18. What is ‘Dynamic Forms’ and why would I use it over a standard Page Layout?

Dynamic Forms allows you to break up the monolithic “Record Detail” block into individual fields and sections directly within the Lightning App Builder. This gives you granular control, allowing you to place fields anywhere on the page and, more importantly, set visibility rules on individual fields or sections. This eliminates the need to create multiple page layouts just to show/hide a few fields for different scenarios.

19. I’ve built a new Lightning Home Page for our Sales users. How do I ensure only they see it?

When you activate the page in the Lightning App Builder, you should choose the App and Profile activation option. This allows you to assign the specific Home Page to the “Sales App” and specifically to the “Sales User” profile. This ensures that Service users or others accessing the system see their own relevant home pages, while Sales users see the custom one you built.

20. Can I display a visual report chart directly on an Account record page?

Yes, using the Lightning App Builder. You can drag the Report Chart standard component onto the canvas. You can then select a source report and filter it by the record ID (so it only shows data relevant to the specific Account you are viewing). This provides embedded analytics directly on the record detail page.