Lightning Web Components (LWCs) have access to a variety of resources in Salesforce. Below are the supported resources:
* Static Resources (A):You can use static resources to reference JavaScript libraries, images, and other files needed in an LWC.

To preserve the value of maxAttempts for the length of the Apex transaction and share its state between trigger executions:
* Static Variable:
* Static variables are initialized once per transaction and retain their value throughout the transaction.
* They can be accessed without instantiating the class.
* Private Scope:
* Declaring it as private ensures encapsulation and prevents unintended external modification.
* Helper Class:
* Using a helper class ensures the separation of concerns, keeping trigger logic clean and adhering to best practices.
Example Code:public class HelperClass {
private static Integer maxAttempts = 5; // Default value
public static Integer getMaxAttempts() {
return maxAttempts;
}
public static void setMaxAttempts(Integer attempts) {
maxAttempts = attempts;
}
}
* A: Constants (static + final) cannot be modified after initialization.
* B: Trigger member variables cannot retain values across executions within the same transaction.
* C: Declaring it as a non-static variable in a helper class would reset its value during each trigger execution.
Why Not the Other Options?

* The SOQL query assigns its result directly to a single sObject variable (Account myAccount). If the query returns more than one record, Salesforce throws a QueryException because the system cannot automatically cast multiple results to a single sObject.
* Not Suitable:
* Option A: The variable cannot be automatically cast to a list.
* Option C: The query itself does not fail but throws an exception.
* Option D: The first record is not automatically assigned.

* Why Lightning Data Service?
* Enforces Salesforce's security model, including:
* Sharing rules.
* Field-level security (FLS).
* This eliminates the need for additional manual security checks.
* Why Not Other Options?
* A: Incorrect, LDS enforces FLS.
* B: with sharing applies to Apex, not Lightning Data Service.
* D: isAccessible() is unnecessary for LDS because it already enforces FLS.
* Lightning Data Service: https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning
/data_service.htm
References:

* An External ID field is used to match data in Salesforce with data from external systems (like an on- premise SQL database). It allows for easy upserts and data integration without relying on Salesforce IDs.
Why not other options?
* A: External objects are used for real-time integration with external systems but do not address data matching directly.
* C: Formula fields are calculated fields and cannot be used for data matching.
* D: Lookup fields are used for creating relationships between objects within Salesforce, not for matching external data.