* Tooling API:
* The Tooling API provides programmatic access to manage tests and other metadata in the org.
* It can execute test classes or methods remotely.
* Developer Console:
* The Developer Console is a built-in Salesforce tool to execute Apex tests, debug logs, and more.
* Allows developers to execute tests interactively.
* B. Metadata API: Used for managing metadata, not for running tests.
* C. Bulk API: Used for data operations, not related to testing.
* Tooling API Overview: https://developer.salesforce.com/docs/atlas.en-us.api_tooling.meta/api_tooling/
* Testing with Developer Console: https://help.salesforce.com/s/articleView?id=sf.
code_dev_console_test.htm

* A: A Flow can guide sales reps through a set of scripted steps and call an Apex action to interact with an external REST endpoint.
* B: An Invocable method is used to make an Apex method callable from a Flow. This method can call the REST endpoint and return the data for display.
Why not other options?
* C: Future methods are asynchronous and cannot return data to the user in real time.
* D: Triggers are used for database events, not for guiding users through scripted processes or making REST calls.
References:
* Invocable Methods in Flows

* A before trigger fires when records are inserted, updated, or deleted. Using the Data Loader or Bulk API to import data updates records, which triggers the before insert or before update events.
* Not Suitable:
* Option A: Renaming or replacing picklists does not trigger a record-level operation.
* Option B: The Mass Address Update tool is not a record operation that triggers before triggers.
* Option D: Converting leads to contacts triggers lead conversion events, not directly related to Account triggers.

* Validation Rule Violations:
* Salesforce automatically throws exceptions for validation rule violations during DML operations.
* <apex:messages> is used to display these errors to the user.
* Why Not Other Options?
* A: Controller attributes alone cannot handle validation messages.
* B: A try/catch block does not address validation rule violations effectively.
* D: Database.upsert() method is not related to validation error handling.
* Apex Messages: https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages
/pages_compref_messages.htm
References:

This method allows the developer to retrieve all available record types and identify the default record type for the current user by checking the isDefaultRecordTypeMapping() attribute.
Example:
Schema.DescribeSObjectResult describeResult = Opportunity.sObjectType.getDescribe(); for (Schema.RecordTypeInfo recordType : describeResult.getRecordTypeInfos()) { if (recordType.isDefaultRecordTypeMapping()) { System.debug('Default Record Type: ' + recordType.getName());
}
}