Quick answers to key questions

Short answers to the main questions from this interview. Add an example from your own project when you answer.

Flows and LWC

• What types of flows have you worked with? Screen flows, record-triggered flows, schedule-triggered flows and autolaunched flows are the common ones.
• Can we delete records using a flow? Yes. Use the Delete Records element, either with a filter on the records or with a collection of records you already found.
• What is a record-triggered flow? A flow that starts automatically when a record is created, updated or deleted. It can run before the save (fast field updates on the same record) or after the save (related records, emails, actions).
• What is an imperative method in LWC? An Apex method that you call from JavaScript at a time you choose, for example when a button is clicked. It returns a promise, so you handle the result with then and catch, or with async and await.
• How do you deploy an LWC? Through a change set (the component is a Lightning Component Bundle), or with Salesforce CLI or a DevOps tool from source control. Include any Apex classes and metadata that the component uses.
• Pagination and lazy loading. Pagination splits a large list into pages. Lazy loading loads more records only when they are needed, for example with infinite loading in lightning-datatable, so the page opens faster.

SOQL, data and core concepts

• What is SOSL? Salesforce Object Search Language searches for a text term across several objects and fields at once, for example FIND {Acme} IN ALL FIELDS RETURNING Account(Name), Contact(Name). SOQL queries one object and its relationships and filters by field values.
• External objects and external fields. They represent data that lives outside Salesforce and is accessed through Salesforce Connect. The object API name ends with __x. The data is read in real time and is not stored in Salesforce.
• Junction object. A custom object with two master-detail relationships. It creates a many-to-many relationship between two objects, for example Candidates and Jobs.
• Roll-up summary fields. A field on the master record that calculates the count, sum, minimum or maximum of related detail records in a master-detail relationship.
• Why do we need test classes? Salesforce needs at least 75% code coverage to deploy to production, but the real goal is to check that the code works for single records and in bulk, and to catch problems when the code changes later.
• OWD and sharing rules. OWD is the baseline access to records for users who do not own them, and it should be the most restrictive level needed. Sharing rules open access up beyond OWD for groups of users, based on ownership or record criteria.
• Does a deep role hierarchy affect performance? It can, because Salesforce has to recalculate access when roles or records change. To reduce the impact, keep the hierarchy as flat as the business allows, use public groups and sharing rules, and avoid having too many records owned by one user.
• Platform Events and Change Data Capture. Platform events are custom messages that you define and publish from flows, Apex or APIs for event-driven integration. Change Data Capture publishes change events automatically when records of an enabled object are created, updated, deleted or undeleted.
• What is SAQL? Salesforce Analytics Query Language, used to query data in CRM Analytics.
• What is Audit Trail? Setup Audit Trail records recent changes made in Setup, such as who changed a setting and when. It shows the last 6 months of changes.
• ContentDocument. It represents a file in Salesforce. The related objects are ContentVersion (each version of the file) and ContentDocumentLink (which links the file to records, users or libraries).