70+ Senior Salesforce Developer Interview Questions and Answers

Best practices for writing triggers, execution order, deployment techniques, code coverage, and Azure DevOps.

• Use trigger framework to avoid code duplication

• Bulkify triggers to handle large data sets

• Follow trigger order of execution

• Use metadata API or change sets for deployment

• Minimum code coverage is 75%

• Azure DevOps is a cloud-based tool for managing software development projects

Yes, an email message can be sent from a trigger even after logic gets into AddError method.

• Email messages are sent asynchronously and are not affected by the AddError method.

• The AddError method only prevents the record from being saved and rolls back any changes made in the transaction.

• To send an email from a trigger, use the Messaging.SingleEmailMessage class and the Messaging.sendEmail method.

To show many columns in a single page for mobile-friendly design in Lightning, use responsive design and consider using horizontal scrolling.

• Use responsive design to ensure the layout adjusts to different screen sizes

• Consider using horizontal scrolling to allow users to view more columns without taking up too much vertical space

• Prioritize the most important columns to display first

• Use filters or collapsible sections to allow users to focus on specific columns

• Test the design o...read more

Custom settings are hierarchical data that can be accessed using code, while custom metadata are metadata types that are customizable at the metadata level.

• Custom settings are hierarchical data that can be accessed using code

• Custom metadata are metadata types that are customizable at the metadata level

• Custom settings can be used to store data that needs to be accessed by code, such as application settings or user preferences

• Custom metadata can be used to define custom metadat...read more

Create a trigger on Account to prevent deletion if associated with one or more contacts

• Create an after delete trigger on Account object

• Query for related contacts using SOQL

• If contacts are found, add an error message to prevent deletion

Use batch Apex to handle bulk callouts over button click

• Implement the Database.Batchable interface to process records in batches

• Use the @future annotation to make asynchronous callouts

• Consider using a queueable Apex job to handle large volumes of data

• Use the Limits.getCallouts() method to monitor callout limits

• Handle any errors or exceptions that may occur during the callout process

I have used multiple development tools throughout my career.

• I have experience with IDEs like Eclipse and Visual Studio Code.

• I have used version control systems like Git and SVN.

• I am familiar with Salesforce development tools like Salesforce DX and Force.com IDE.

• I have worked with continuous integration and deployment tools like Jenkins and Salesforce CI/CD.

• I have used debugging tools like Salesforce Inspector and Developer Console.

Best practices in Trigger and trigger events

• Best practices include bulkifying triggers, using helper classes, and limiting logic in triggers

• Trigger events are before insert, before update, after insert, after update, etc.

• Examples of trigger events include before insert, after update, etc.

Connected App, remote site settings, and OAuth are key components in Salesforce for enabling secure external access to Salesforce data and functionality.

• Connected App is a framework that enables external applications to securely integrate with Salesforce using APIs.

• Remote Site Settings allow Salesforce to make callouts to external services over HTTPS.

• OAuth is an open standard for access delegation, commonly used in Salesforce for authentication and authorization of external a...read more

Static block is a block of code that runs only once when the class is loaded.

• Static block is enclosed in curly braces and starts with the keyword 'static'.

• It is used to initialize static variables or to perform any one-time setup for the class.

• Static block is executed before the constructor of the class.

• Example: static { System.debug('This is a static block'); }

The backend class for a Lightning Web Component (LWC) should handle data retrieval, manipulation, and communication with Salesforce.

• Create an Apex class with @AuraEnabled methods to be called from the LWC component

• Use SOQL queries to retrieve data from Salesforce database

• Implement logic for data manipulation and business processes

• Handle error messages and exceptions appropriately

• Utilize Apex triggers and classes for complex operations

RAM stands for Random Access Memory and ROM stands for Read Only Memory. RAM is a volatile memory used for temporary storage while ROM is a non-volatile memory used for permanent storage.

• RAM is used for storing data that is currently being used by the computer's CPU. It is volatile, meaning the data is lost when the power is turned off.

• ROM is used for storing data that needs to be permanently stored, such as the computer's BIOS. It is non-volatile, meaning the data is not los...read more

Future methods in Salesforce can accept primitive data types as parameters.

• Primitive data types like Integer, String, Boolean, etc. can be passed as parameters to Future methods.

• Non-primitive data types like custom objects or collections cannot be passed as parameters to Future methods.

• Example: @future public static void myFutureMethod(Integer param1, String param2) { }

Create a trigger on Contact to display the number of contacts on the related Account.

• Create an after insert, update, delete trigger on Contact object

• Query for the count of contacts related to the Account

• Update a custom field on the Account with the count of contacts

Display Accounts with related contacts in a list using LWC code

• Create a Lightning web component (LWC) to display the list

• Use Apex to query for Accounts and their related Contacts

• Iterate over the data to display Accounts and their related Contacts in the list

Test private methods in trigger for updating related data of opportunity's contact and account

• Create test data for Opportunity, Contact, and Account records

• Call the private methods in the test class using System.assertEquals to verify the expected results

• Use Test.startTest and Test.stopTest to isolate the trigger execution

Connection from Mulesoft to Salesforce is done using Salesforce Connector in Mulesoft Anypoint Platform.

• Use Salesforce Connector in Mulesoft Anypoint Platform to establish connection

• Authenticate using Salesforce credentials (username, password, security token)

• Utilize Salesforce APIs to interact with Salesforce data

To pass subjects to future methods, use the @future annotation in Apex.

• Use the @future annotation before the method declaration to indicate that the method will run asynchronously in the future.

• Pass the subject parameters to the @future method as arguments when calling the method.

• Ensure that the subject parameters are serializable to be passed to future methods.

Tools for deployment include Salesforce DX, Ant Migration Tool, Change Sets, and Metadata API.

• Salesforce DX is a command-line interface for development and deployment

• Ant Migration Tool is a Java/Ant-based tool for moving metadata between environments

• Change Sets allow for moving configuration changes between orgs

• Metadata API is a web service for managing metadata

With and without sharing in Salesforce determines whether sharing rules are enforced for a class.

• With sharing keyword enforces sharing rules, restricting access to records based on the user's profile and organization-wide defaults.

• Without sharing keyword does not enforce sharing rules, allowing full access to all records regardless of the user's profile or organization-wide defaults.

Code to calculate the product of two integers passed as parameters.

• Declare a function that takes two integer parameters.

• Multiply the two integers together and store the result in a variable.

• Return the calculated product.

Future is asynchronous and runs in a separate thread, while Queueable Apex runs in the same thread but can be queued for execution.

• Future methods are used for executing code asynchronously, while Queueable Apex is used for chaining jobs and running them in a specific order.

• Future methods have a limit of 50 per transaction, while Queueable Apex has a limit of 50 jobs in the queue per transaction.

• Future methods cannot be scheduled, while Queueable Apex can be scheduled for futu...read more

Order of execution in Salesforce determines the sequence of events that occur when a record is saved.

• Triggers are executed first

• Validation rules are checked next

• Before triggers are executed

• Custom validation logic is checked

• Record is saved to the database

• After triggers are executed

• Assignment rules are executed

• Auto-response rules are executed

• Workflow rules are executed

• Escalation rules are executed

• Roll-up summary fields are updated

• Criteria-based sharing rules are evaluated

• Post-c...read more

Yes, I have experience sending emails from Salesforce API.

• I have used the Salesforce REST API to send emails programmatically.

• I have integrated email functionality into Salesforce workflows and processes.

• I have experience with setting up email templates and automating email sends using Salesforce API.

Best practices for test classes in Salesforce development.

• Test all positive and negative scenarios

• Use test data factory methods to create test data

• Avoid hardcoding IDs and use SOQL queries to retrieve data

• Use System.assert methods to validate results

• Test governor limits and bulk data scenarios

• Use @testSetup to create common test data

• Avoid using SeeAllData=true

• Test asynchronous code using Test.startTest() and Test.stopTest()

• Use Test.isRunningTest() to avoid executing unnecessa...read more

Promise is an object representing the eventual completion (or failure) of an asynchronous operation, and promiseAll is a method that takes an iterable of promises and returns a single Promise that resolves when all of the promises have resolved.

• Promise is used in JavaScript to handle asynchronous operations.

• It represents a value that may not be available yet, but will be resolved at some point in the future.

• PromiseAll is a method that takes an iterable of promises and returns...read more

There are two types of price rules in Salesforce CPQ.

• There are two types of price rules in Salesforce CPQ: Product Rules and Discount Schedule Rules.

• Product Rules are used to set pricing based on specific product configurations or attributes.

• Discount Schedule Rules are used to apply discounts based on predefined discount schedules.

Implemented a custom Lightning component for a client to streamline their lead management process.

• Created a custom Lightning component using Aura framework

• Integrated the component with Salesforce lead objects and workflows

• Implemented client-specific business logic and validation rules

• Tested the component thoroughly to ensure functionality and performance

Code to send email on update record form apex

• Create a trigger on the object you want to monitor for updates

• In the trigger, check if the record has been updated

• If it has, create an instance of the Messaging.SingleEmailMessage class

• Set the necessary properties of the email message, such as the recipient, subject, and body

• Add the email message to a list of messages

• Use the Messaging.sendEmail method to send the email

Yes, callouts can be made from triggers in Salesforce.

• Callouts can be made from triggers using @future annotation to make asynchronous callouts.

• It is recommended to use @future annotation to avoid hitting governor limits.

• Make sure to handle any potential exceptions that may occur during the callout.

Use SOQL query to fetch the second maximum amount record of opportunity

• Use ORDER BY clause to sort the records by amount in descending order

• Use LIMIT 2 to fetch the top 2 records

• Use OFFSET 1 to skip the first record and fetch the second maximum amount record

Flow and automation types are tools in Salesforce used to automate business processes and streamline workflows.

• Flows are declarative automation tools that allow users to design and automate business processes by creating visual workflows.

• Automation types include Process Builder, Workflow Rules, and Approval Processes, which automate repetitive tasks and streamline processes.

• Examples of automation types include automatically sending an email when a new lead is created, updatin...read more

Some new features of Salesforce include Lightning Web Components, Einstein Voice, and Salesforce Blockchain.

• Lightning Web Components allow developers to build custom components using modern web standards.

• Einstein Voice enables users to interact with Salesforce using natural language processing.

• Salesforce Blockchain helps organizations securely share data and processes across multiple parties.

Rollup summary triggers are used to calculate and display aggregated data from child records on a parent record in Salesforce.

• Create a trigger on the child object (Contact) to calculate the sum of a field (e.g. Amount) and update a field on the parent object (Account)

• Use SOQL queries to retrieve the related child records and calculate the sum

• Handle bulk operations to ensure trigger efficiency and avoid governor limits

Process builder has some limitations and drawbacks.

• Process builder can slow down the system performance.

• It has a limit of 10,000 records per hour.

• It can be complex to use and maintain.

• It cannot handle bulk updates efficiently.

• It does not support all types of actions and criteria.

• It can cause recursion and infinite loops if not configured properly.

To subscribe for a platform event, use the CometD library or the EMP Connector

• Use the CometD library to subscribe to platform events

• Use the EMP Connector (Enterprise Messaging Platform) to subscribe to platform events

• Specify the event channel to subscribe to in the code

Rollup summary field is a field in Salesforce that calculates values from related records and displays the result on a parent record.

• Rollup summary fields are used to perform calculations on child records and display the result on a parent record.

• They can be used to calculate the sum, count, minimum, or maximum of a field in related records.

• For example, a rollup summary field can be used to calculate the total amount of all opportunities related to an account.

• Rollup summary f...read more

Before triggers are executed before the record is saved to the database, while after triggers are executed after the record is saved.

• Before triggers are used to validate or modify record values before they are saved.

• After triggers are used to perform additional actions after the record is saved.

• Before triggers can be used to prevent the record from being saved by throwing an exception.

• After triggers can be used to update related records or perform asynchronous operations.

LDT stands for Long Data Type and has restrictions on its usage in Salesforce.

• LDT is a custom field type in Salesforce used for storing large amounts of text data.

• It has a limit of 131,072 characters per record.

• LDT fields cannot be used in formula fields or workflow rules.

• LDT fields are not searchable in Salesforce reports.

Communication between independent components in LWC can be achieved using events, pubsub, and properties.

• Use events to communicate between components in a parent-child relationship

• Implement pubsub pattern using custom events to communicate between unrelated components

• Pass data between components using properties

Salesforce governor limits are limits enforced by Salesforce to ensure efficient use of resources and prevent abuse.

• Governor limits are enforced to prevent long-running or resource-intensive operations.

• Examples of governor limits include limits on the number of SOQL queries, CPU time, and DML statements.

• Exceeding governor limits can result in exceptions being thrown by Salesforce.

• Developers need to be aware of governor limits and design their code to work within these constra...read more

LWC decorators are used to define metadata for Lightning web components. SOQL is used to query records in Salesforce, while SOSL is used to search for records.

• LWC decorators are used to add metadata to Lightning web components, such as @api to expose a property or method

• SOQL (Salesforce Object Query Language) is used to query records in Salesforce based on specific criteria

• SOSL (Salesforce Object Search Language) is used to search for records in Salesforce using a search quer...read more

Lazy loading in LWC delays the loading of resources until they are actually needed.

• Lazy loading helps improve performance by only loading resources when necessary

• This approach is commonly used for loading images, scripts, or components on demand

• Example: Lazy loading images in a gallery component to improve page load speed

Child to parent communication in LWC involves using events to pass data from child components to parent components.

• Use custom events to communicate from child to parent components

• Dispatch the custom event in the child component and handle it in the parent component

• Pass data along with the custom event to send information from child to parent

OWDs in SF refer to Organization-Wide Defaults which control the default level of access users have to records in Salesforce.

• OWDs determine the baseline level of access for all records in an organization

• They can be set to Public Read/Write, Public Read Only, Private, or Controlled by Parent

• OWDs can be further refined using sharing rules and manual sharing

DML mixed error occurs when a single DML operation tries to insert, update, or delete multiple records of different types in a single transaction.

• Occurs when trying to perform DML operations on multiple types of records in a single transaction

• Can happen when inserting, updating, or deleting records of different objects in one operation

• Results in a mixed DML error and requires workaround like using @future annotation for asynchronous processing