Salesforce Plat-Dev-301 Dumps - Pass Salesforce Certified Platform Developer II in 2026

Salesforce enforces a strict restriction: Actual network callouts are prohibited during unit tests. This is to ensure that tests are deterministic, fast, and do not rely on the availability or state of external third-party systems. When the testing engine encounters a System.Http.send() or a web service call without a mock, it throws the error: 'Methods defined as TestMethod do no1t support Web servi2ce callouts.'34

To resolve this, the developer must provide a Mock Implementation. By using Test.setMock() (Option D), the developer instructs the Apex runtime to intercept any callouts and return a pre-defined response instead of attempting a real connection. The mock class5 must implement either the HttpCalloutMock interface (for REST) or the WebServiceMock interface (for SOAP).

Furthermore, the call to the mock and the callout method should be wrapped in Test.startTest() and Test.stopTest().6

Test.startTest(): Resets governor limits, providing a fresh context for the specific logic being tested.7

Test.stopTest(): Forces any asynchronous processing (often used in cal8louts, such as @future or Queueable) to complete before the next line of code executes.

In the provided code, Test.setMock must be called before CalloutUtil.sendAccountUpdate for the platform to know which mock to use. Once Test.stopTest() is reached, the mock response is processed, the checkbox is updated, and the subsequent SOQL query and assertion will correctly see the updated data. Option A is a poor practice because it skips the logic entirely, resulting in 0% code coverage for the integration logic.

To create a responsive design in Salesforce Aura components, the lightning:layout and lightning:layoutItem components utilize a 12-column grid system based on the Salesforce Lightning Design System (SLDS). The issue in the original code is that size='6' is hardcoded, which forces each item to occupy 50% of the container width regardless of the screen size. On small mobile screens, 50% width is often insufficient for text content, leading to horizontal scrolling or overlapping.

Option B resolves this by using device-specific size attributes. By setting smallDeviceSize='12', each item is instructed to take up the full width (12 out of 12 columns) on mobile devices. This causes the items to stack vertically instead of sitting side-by-side. The mediumDeviceSize='6' and largeDeviceSize='6' attributes ensure that on tablets and desktop screens, the items return to a side-by-side layout (50% width each).

For this stacking to occur, the parent lightning:layout must have the multipleRows='true' attribute enabled. This allows the layout to wrap items to a new line once the total column count in a single row exceeds 12. Without multipleRows='true', the items would try to squeeze into a single line regardless of their individual size settings, which would not solve the horizontal scrolling problem. Option B is the only choice that correctly applies the grid logic to handle multiple breakpoints effectively.

Comprehensive and Detailed

In Visualforce, partial page updates (AJAX) are achieved using the reRender attribute. This attribute allows a component to refresh only a specific part of the page identified by an ID, rather than performing a full browser reload.

(Option C) and (Option E) are standard action components. When their reRender attribute is populated, they perform an asynchronous postback.

(Option D) is an auxiliary component that adds AJAX functionality to other components that do not natively support it. For example, you can place an actionSupport inside an inputText to trigger a partial refresh on the onchange event.

Option A () is a container and does not initiate AJAX behavior itself. Option B () is used to display the status of an AJAX request (e.g., a loading spinner) but does not initiate the request.

For storing application configurations and integration settings that need to be easily modified by administrators and deployed across environments, Custom Metadata Types are the preferred solution. Unlike Custom Settings (Options A and D), records within a Custom Metadata Type are considered metadata rather than data. This is a critical distinction for the development lifecycle because these records can be included in Change Sets or deployment packages. This eliminates the manual overhead and risk associated with re-creating configuration records in production after a sandbox deployment.

In this scenario, UC needs to manage settings for two different payment processors. A Custom Metadata Type can be created with fields for API endpoints, merchant IDs, and security keys. An administrator can then create and edit the specific records for the 'Individual' and 'Corporate' processors directly in the Setup menu. Furthermore, Custom Metadata queries are efficient and do not count against standard SOQL governor limits in many contexts. While Custom Labels (Option B) are useful for translating text, they are not intended for complex, structured configuration data. Hierarchy Custom Settings are designed for user-specific overrides, which is not applicable here. Therefore, Custom Metadata provides the most robust, deployable, and administrator-friendly way to manage external service configurations.

==========

In Lightning Web Components (LWC), data flows 'down' via properties and 'up' via events. When a child component needs to communicate a change in a property or state to its parent, it must dispatch a CustomEvent. To pass specific data---such as the new value of the passthrough property---along with the event, the developer must use the detail property within the event initialization object.

Option C is the correct syntax. It creates a new CustomEvent named 'passthrough' and assigns the current value of the component's property (this.passthrough) to the detail key. The parent component can then listen for this event (using onpassthrough={handleEvent}) and access the value via event.detail. Option A is incorrect because it wraps the variable in quotes, passing the literal string 'this.passthrough' instead of the actual data. Option B creates an event but fails to include the data payload, meaning the parent would know an event occurred but wouldn't receive the new value. Option D uses incorrect syntax for event naming and variable referencing. Using the standard CustomEvent constructor with the detail property is the platform-standard way to ensure robust, typed data communication between component layers in the Shadow DOM.

==========