1. ^ and ~ in Dependencies in package.json
^ (Caret):
Allows minor version updates only.
Example: ^3.1.0 → Accepts versions like 3.2.0, 3.5.1, but not 4.0.0.
~ (Tilde):
Allows patch-level updates only.
Example: ~2.4.0 → Accepts versions like 2.4.1, 2.4.9, but not 2.5.0.
2. Should we create Remote Site Settings when Named Credential used in Salesforce?
If the callout specifies a named credential as the endpoint, you don’t need to configure remote site settings.
https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_callouts_remote_site_settings.htm
3. Can we invoke Salesforce Lightning Web Component as an action from Flow?
Yes. lightning__FlowAction target can be used to achieve this.
4. How to find the Salesforce Release version using My Domain URL?
https://{YOUR_SALESFORCE_DOMAIN}.my.salesforce.com/releaseVersion.jsp
5. Difference between Generative AI and Agentforce?
The key difference between Generative AI and Agentic AI lies in their primary function. Generative AI is focused on understanding and producing content, excelling at tasks such as writing code, generating summaries, or answering queries. In contrast, Agentic AI is designed to autonomously execute actions, enabling it to perform tasks like updating records, triggering workflows, and resolving customer issues without direct human intervention.
GenAI examples in Salesforce are Einstein Service Replies, Einstein Work Summary, Prompt Template, etc
6. What are the use cases for Salesforce Agentforce?
Agentforce Employee Agent can be used to assist the internal employees. It can help in finding similar cases, similar Opportunities, Summarizing the records, finding the top Cases/Opportunities to work, etc
Agentforce Service Agent can be used to assist the external users. It can resolve simple to complex queries by using Answer Questions with Knowledge action, schedule appointments, etc
Service Assistant to assist Service Representatives when they receive cases.
SDR Agent to work on Leads and Opportunities.
Service Agent to work on Cases created on Email-to-Case.
7. Difference between Salesforce Agentforce and Einstein BOT
Einstein BOT/Chat BOT is a computer program designed to interact with users through pre-set rules, decision trees, and scripted replies. It relies on a basic form of artificial intelligence with natural language processing (NLP) capabilities and often requires extensive training and fine-tuning to understand and respond to user inputs accurately.
An AI agent is a sophisticated assistant built to enhance human capabilities across a broad spectrum of tasks. Unlike basic chatbots, AI agents—also known as autonomous agents—can comprehend and generate natural language, analyze vast amounts of data, and support complex activities such as writing, coding, problem-solving, and creative work.
8. Explain Salesforce Einstein Requests
Requests made to Salesforce LLM gateway are Einstein Requests.
Many of Salesforce’s generative AI Services and features consume Einstein Requests.
Starter Einstein Request: Usage is calculated based on the number of calls to the LLM gateway if the gateway uses Bring Your Own Large Language Model (BYOLLM).
Standard Einstein Request: Usage is calculated based on the number of calls to the LLM gateway if the gateway uses a Salesforce LLM.
9. What is Salesforce Einstein Trust Layer?
The Einstein Trust Layer is a robust set of features and guardrails that protect the privacy and security of your data, improve the safety and accuracy of your AI results, and promote the responsible use of AI across the Salesforce ecosystem. With features like dynamic grounding, zero data retention, and toxicity detection, the Einstein Trust Layer is designed to help you unleash the power of generative AI without compromising your safety or security standards.
Example:
Masks the PII data.
Dynamic Grounding.
Secure Data Retrieval from Salesforce Data Sources(Objects).
10. What are Data Streams in Salesforce Data Cloud?
Data Streams are the pipelines that bring data from external sources into Salesforce Data Cloud. They connect to various systems like CRM platforms, ERP systems, and other third-party tools to ensure a constant flow of fresh data. This guarantees that the data available for analysis and subsequent actions is always current.
11. What is the best option to call an external service (HTTP callout) and also update a related record from Salesforce Trigger?
This can be achieved via @future or Queueable interface in Salesforce
Queueable Apex is the modern, more robust alternative to the @future method and is perfectly suited for this use case:
Asynchronous: It immediately offloads the work (callout + update) from the user’s transaction, fulfilling the requirement to avoid slowing down the user.
Allows Callouts: By implementing the Database.AllowsCallouts interface, the job can safely make the required HTTP callout.
Passes sObjects: Queueable can take sObjects as arguments. This is the main advantage over @future. You can pass the actual Opportunity record and the related record to the job, ensuring the update logic uses the most current and correct data without needing an extra SOQL query inside the asynchronous job.
Chaining and Monitoring: It provides a Job ID for monitoring, and the ability to chain another asynchronous job, providing better scalability and auditability than the simpler @future method.
Transaction Finalizers Interface:
The Transaction Finalizers feature enables you to attach actions, using the System.Finalizer interface, to asynchronous Apex jobs that use the Queueable framework.
12. Apex Cursors (Beta)
Use Apex cursors to break up the processing of a SOQL query result into pieces that can be processed within the bounds of a single transaction. Cursors provide you with the ability to work with large query result sets, while not actually returning the entire result set. You can traverse a query result in parts, with the flexibility to navigate forward and back in the result set. Package developers and advanced developers can use cursors effectively to work with high-volume and high-resource processing jobs. Cursors combined with chained queueable Apex jobs are a powerful alternative to batch Apex and address some of batch Apex’s limitations.
https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_cursors.htm
13. Can we use Salesforce SCIM REST APIs for Experience Cloud users?
Yes.
https://help.salesforce.com/s/articleView?id=xcloud.identity_scim_rest_api.htm&type=5
14. What is the default number of record types per object in Salesforce?
While Salesforce doesn’t have a technical limit that prevents you from creating an infinite number of record types per object, they strongly recommend a maximum of 200 record types.
Exceeding the 200 record type limit can lead to significant issues with performance and administrative complexity, especially when managing page layout assignments and picklist values across various profiles and permission sets.
https://help.salesforce.com/s/articleView?id=platform.recordtypes_picklists_limitations.htm&type=5
15. What is the use of Pub/Sub API
Pub/Sub API provides a single interface for publishing and subscribing to platform events, including real-time event monitoring events, and change data capture events. Based on gRPC API and HTTP/2, Pub/Sub API efficiently publishes and delivers binary event messages in the Apache Avro format.
Pub/Sub API doesn’t support legacy events, such as standard-volume platform events, PushTopic events, and generic streaming events.
https://developer.salesforce.com/docs/platform/pub-sub-api/guide/supported-event-types.html