AP-202 Practice Questions

The B2B Commerce framework provides specific scoped modules to access contextual information without needing an Apex call. The @salesforce/commerce/context module is designed to provide context about the current store, including the webstoreId. This is the most direct, efficient, and standard method for an LWC to become aware of the store it's running in.

The standard pattern for testing wired Apex methods in Jest is to import the adapter itself. The testing framework provides a mock version of the wire service that includes an emit function. The test can then call .emit(mockData) to simulate the wire service pushing data to the component. This allows the developer to test how the component renders and behaves with the mocked data without making a real server call.

False. The B2B Commerce search index is not updated in real-time. After making changes to products, catalogs, or price books, an administrator must manually run a search index rebuild process from the store's administration settings. This process can take some time to complete depending on the size of the catalog.

The checkout process is controlled by a Flow. Therefore, the most appropriate place to add server-side validation is within the checkout flow itself. A developer can create a custom Apex invocable action that accepts the cart ID, performs the necessary queries to sum the quantities by category and check the Account limit, and returns a boolean result. A Decision element in the flow can then use this result to either direct the user to an error screen or allow them to proceed.

The most effective way to reduce database round-trips and improve Apex performance is to aggregate multiple queries into a single query. Using parent-child subqueries allows the retrieval of the product, its attributes, documents, and policies in one efficient database operation, minimizing query time and CPU usage. Caching would help subsequent loads but doesn't fix the initial slow load. Pagination is for handling large record sets, not for reducing multiple distinct queries. Asynchronous calls would not reduce the total server-side processing time for a single user's request.

The correct approach is to first retrieve the historical WebCart records for the user. The B2B Commerce API provides a specific B2BReorder Apex class with a reorder method designed for this purpose. This method takes the original cart ID as input and handles the creation of the new cart and its items, returning the ID of the new cart. Finally, the user should be programmatically navigated to the new cart page. Other options misuse the APIs or suggest incorrect methods.

B2B Commerce natively supports assigning different checkout flows to different buyer groups. The correct method is to build the distinct flows required in Flow Builder and then use the B2B Commerce administration settings within the store to map each flow to the appropriate buyer group. This is the most scalable and maintainable solution that leverages standard platform functionality.

The GatewayProvider interface is the correct reference implementation for integrating payment gateways. To add a custom fraud check, a developer would create a custom Apex class that implements this interface. Within the authorize method of this class, the developer would first make a callout to the external fraud service and then, if the check passes, proceed with the standard payment authorization logic.