Developers CRT-450 Exam Questions and Answers PDF

The developer should write a class that implements the HTTPCalloutMock interface to provide test coverage for the Apex code that calls out to an external system. The HTTPCalloutMock interface enables you to inject fake responses into the callout response in a test method, so that you can isolate your Apex logic from any dependency on the external system. The interface has one method, respond, that returns a predefined HTTPResponse object when the Apex code calls the HTTPRequest.send method. By using the HTTPCalloutMock interface, you can test your Apex code without actually calling the external system, which saves time and avoids hitting callout limits. The other options are not valid ways to mock a callout in a test method. The HTTPCalloutMock interface is not a class, so it cannot be extended. The WebserviceMock interface is used to mock a SOAP web service callout, not a RESTful HTTP callout. The WebserviceMock interface is also not a class, so it cannot be extended either. References:

• Apex Developer Guide: Testing HTTP Callouts by Implementing the HttpCalloutMock Interface, pages 1-2
• Trailhead: Platform Developer I Certification Study Guide: Apex Testing, unit 6

Apex test methods should not depend on existing data in the sandbox, because they may not have access to the same data when they run in a different environment, such as production. Test methods should create their own test data, or use the @testSetup annotation to create common test data for all test methods in a class12. The Execute Anonymous tool runs the code in the context of the current user and the current data, so it may not reproduce the same behavior as the test method3. References:

• Get Started with Apex Unit Tests Unit | Salesforce Trailhead
• Using Test Setup Methods | Apex Developer Guide - Salesforce Developers
• Test Class | Apex Reference Guide | Salesforce Developers

The correct answer is option B. Use Security.stripInaccessible to remove fields inaccessible to the current user. This method takes a list of records and an access type (READ, UPDATE, CREATE, or UPSERT) and returns a new list of records with the inaccessible fields removed. This way, the Lightning web component can display the records without throwing any errors due to field-level security.

Option A is incorrect because WITH SECURITY_ENFORCED is a SOQL clause that enforces field-level security on all fields in the query. If the query returns any fields that the user does not have access to, the query will throw an exception. This is not desirable for the Lightning web component, as it will prevent the component from displaying any records at all.

Option C is incorrect because Lightning Data Service is a layer of Lightning web components that provides access to Salesforce data and metadata, cache management, and data synchronization. However, Lightning Data Service does not automatically handle field-level security for the records it retrieves. The developer still needs to use Security.stripInaccessible or another method to remove the inaccessible fields.

Option D is incorrect because Lightning Locker Service is a security feature that isolates Lightning web components from each other and from the rest of the page. It does not enforce sharing rules or field-level security for the data that the components access.

References: Security.stripInaccessible (Apex Developer Guide)), WITH SECURITY_ENFORCED (Apex Developer Guide)), Lightning Data Service Basics (Trailhead)), Lightning Locker (Lightning Web Components Developer Guide))

A developer can execute tests in an org using the Tooling API or the Developer Console. The Tooling API allows developers to run tests programmatically by making REST or SOAP calls1. The Developer Console is a web-based tool that provides a user interface for running tests, viewing test results, and debugging code2. The Bulk API and the Metadata API are not used for executing tests, but for loading and managing large sets of data and metadata respectively3 .

References:

• Apex Developer Guide - Run Unit Test Methods
• Salesforce Help - Developer Console
• Salesforce Developer - Bulk API
• Salesforce Developer - Metadata API