As part of new feature development, a developer Is asked to build a responsive application capable of responding to touch events, that will be executed on stateful clients.
Which two technologies are built on a framework that fully supports the business requirement?
Choose 2 answers
To build a responsive application capable of responding to touch events and executed on stateful clients, the developer should use technologies that support modern web standards, responsive design, and touch interactions. The two technologies that meet these requirements are Aura Components and Lightning Web Components.
Option A: Aura Components
Option C: Lightning Web Components
'Lightning web components are custom HTML elements built using HTML and modern JavaScript.'
Why Other Options Are Incorrect:
Option B: Visualforce Pages
Visualforce is a server-side framework that doesn't fully support responsive design or touch events natively. While you can make Visualforce pages responsive using custom code, it doesn't provide built-in support for touch events as effectively as Aura Components or LWC.
Option D: Visualforce Components
Visualforce Components are custom components within the Visualforce framework. They inherit the same limitations as Visualforce Pages regarding responsiveness and touch support.
A developer creates a Lightning web component that imports a method within an Apex class. When a Validate button is pressed, the method runs to execute complex validations.
In this implementation scenario, which two options are part of the Controller according to the MVC architecture?
Choose 2 answers
In the Model-View-Controller (MVC) architecture applied to a Lightning Web Component (LWC) that imports an Apex method:
Controller refers to the logic that handles input and interactions.
In this scenario, when a button is pressed, the method runs to execute complex validations.
Option C: Apex class
Part of Controller.
The Apex class contains the method that performs the complex validations.
It acts as the server-side controller logic.
The JavaScript file of the LWC handles the client-side logic.
It invokes the Apex method when the button is pressed.
The HTML file defines the component's template (View), not the Controller.
Option B: XML file
Configuration File.
The XML file (configuration file) defines metadata about the component, such as where it's available, but it's not part of the Controller.
Conclusion:
The Controller parts in this scenario are the Apex class and the JavaScript file, which are Options C and D.
Option D: JavaScript file
Part of Controller.
Incorrect Options:
Option A: HTML file
View Layer.
A developer created a new after insert trigger on the Lead object that creates Task records for each Lead.
After deploying to production, an existing outside integration that inserts Lead records in batches to Salesforce is occasionally reporting total batch failures being caused by the Task insert statement. This causes the integration process in the outside system to stop, requiring a manual restart.
Which change should the developer make to allow the integration to continue when some records in a batch cause failure due to the Task insert statement, so that manual restarts are not needed?
Using Database.insert with allOrNone=false allows partial success in DML operations.
Option D: Use the Database method with allOrNone set to false.
Records that cause errors are not inserted.
Successful records are committed.
Prevents the entire batch from failing.
Why Not Other Options:
Option A: Deactivating the trigger is not practical.
Option B: Removing the class from the profile may cause other issues.
Option C: A try-catch block won't prevent the batch from failing.
Database Methods:
Universal Containers recently transitioned from Classic to Lightning Experience.
One of its business processes requires certain values from the Opportunity cbject to be sent via an HTTP REST callout to its external order management system when the user presses a custom button
on the Opportunity detail page. Example values are as follows:
* Name
* Amount
* Account
Which two methods should the developer implement to fulfill the business requirement?
Choose 2 answers
To send Opportunity values via an HTTP REST callout when a user presses a custom button in Lightning Experience:
Option B: Create a custom Visualforce quick action
A Visualforce page with a custom controller can perform the callout.
The Visualforce page can be added as a quick action on the Opportunity page.
A Lightning component can perform the callout when invoked.
The component can be added to the Opportunity page as a quick action.
'You can use Visualforce to create custom quick actions.' --- Salesforce Help: Quick Actions
Option C: Create a Lightning component quick action
Why Other Options Are Incorrect:
Option A:
Remote Actions are used in Visualforce for client-side calls and are not applicable here.
Performing the callout whenever the Opportunity is updated does not meet the requirement of initiating the action via a button click.
Option D:
An after-update trigger would execute on every update, not just when the user presses a button.
Using @future methods may not execute immediately and can't be invoked directly by the user action.
How can a developer check the test coverage of autolaunched Flows before deploying them in a change set?
As of Winter '20 (API version 47.0), Salesforce introduced the ability to test Autolaunched Flows with test coverage.
However, as of the current knowledge cutoff (2023-09), there is no direct way within the Salesforce UI to check the test coverage of autolaunched flows before deploying them via change sets.
To check the test coverage of flows, developers can use the Tooling API to query for test coverage.
Option A: Use SOQL and the Tooling API.
Correct Answer.
Developers can use the Tooling API to query for Flow test coverage information.
By executing a SOQL query on FlowTestCoverage and FlowVersionView objects via the Tooling API, developers can retrieve coverage data.
This allows checking flow test coverage programmatically before deployment.
The Flow Properties page does not provide test coverage information.
It allows configuring flow settings but not checking test coverage.
Option C: Use the Code Coverage Setup page.
Incorrect.
The Code Coverage page in Setup pertains to Apex code coverage, not Flow coverage.
Option D: Use the ApexTestResult class.
Incorrect.
The ApexTestResult class is used for Apex test results.
It does not provide information on Flow test coverage.
Conclusion:
To check the test coverage of autolaunched Flows before deploying them in a change set, a developer should use SOQL and the Tooling API, which is Option A.
Flow Test Coverage with Tooling API
Use Tooling API to Check Flow Coverage
Incorrect Options:
Option B: Use the Flow Properties page.
Incorrect.
