TCS Salesforce Developer Trainee Interview Questions and Answers

Life Cycle hooks in LWC are methods that allow you to interact with the component at specific stages of its lifecycle.

• There are four main life cycle hooks in LWC: connectedCallback, disconnectedCallback, renderedCallback, and errorCallback.

• connectedCallback is called when a component is inserted into the DOM.

• disconnectedCallback is called when a component is removed from the DOM.

• renderedCallback is called after the com...read more

There are multiple ways to communicate between components in Salesforce, including using events, public properties, and Apex methods.

• Using events to communicate between components

• Passing data through public properties

• Invoking Apex methods to share data

Yes, future methods can be called from a batch class in Salesforce.

• Future methods can be called from batch classes to perform asynchronous processing.

• This can be useful for offloading long-running tasks to future methods to avoid hitting governor limits.

• Example: Calling a future method from a batch class to update records in Salesforce asynchronously.

The @track decorator in Salesforce is used to track changes to a property in a Lightning web component.

• Used to make a property reactive and trigger re-renders when its value changes

• Not mandatory but recommended for properties that need to be reactive

• Use @track when you want changes to a property to be reflected in the UI

APEX CPU Limit Exceeded error happens when code consumes too much CPU time. Best practices include optimizing code, reducing loops, and using asynchronous processing.

• Avoid using nested loops and optimize code for better performance

• Use asynchronous processing like @future or Queueable to offload CPU intensive tasks

• Limit the use of SOQL queries inside loops to reduce CPU consumption

Mixed DML Exception occurs when DML operations are performed on setup and non-setup objects in a single transaction.

• Occurs when DML operations are performed on both setup and non-setup objects in a single transaction

• Setup objects include User, Profile, PermissionSet, etc.

• Non-setup objects include custom objects, standard objects like Account, Contact, etc.

The code will output 'undefined' because variable 'a' is hoisted within the function.

• Variable 'a' is hoisted to the top of the function scope, so when 'console.log(a)' is called, 'a' is undefined.

• To fix this, move the declaration of 'var a=2;' above the 'console.log(a);' statement.

SOQL query to fetch description field from Account and reason for inability to filter

• SOQL query: SELECT Description FROM Account

• Description field is not filterable because it is a long text field

• Long text fields cannot be filtered in SOQL queries

A trigger is a piece of code that is executed before or after a record is inserted, updated, or deleted in Salesforce.

• Triggers are written in Apex and are used to perform custom actions on records.

• Triggers can be executed before or after a record is inserted, updated, or deleted.

• Triggers can be used to enforce validation rules, update related records, or perform other custom logic.

LWC decorators are used to add metadata to class fields or methods. '@api' is used to expose a public property or method.

• LWC decorators are used to enhance the functionality of Lightning web components.

• '@api' decorator is used to expose a public property or method that can be accessed by parent components.

• Other decorators like '@track', '@wire', '@api get', '@api set' are also commonly used in LWC development.

Data is sent by callout using HTTP request methods like GET, POST, PUT, DELETE.

• Data can be sent in the request body or as query parameters

• Headers can be used to provide additional information

• Response codes indicate the status of the request

• Examples: Sending data to an external API, retrieving data from a web service

Types of flow in Salesforce include autolaunched flows, screen flows, and scheduled flows.

• Autolaunched flows are triggered by a process or record change

• Screen flows guide users through a series of screens to collect information

• Scheduled flows are executed at a specific time or on a recurring basis

Best practice for writing triggers in Salesforce

• Ensure trigger logic is bulkified to handle multiple records at once

• Use trigger handler classes to separate logic from trigger itself

• Avoid SOQL queries inside loops to prevent hitting governor limits

• Write unit tests to cover trigger logic and ensure proper functionality