Salesforce AP-219 Practice Exam Questions & Answers

Two reasons an admin should choose an Event over a Trigger when it comes to building out a solution are:

Events are asynchronous. This means that events are processed in the background, without blocking the main execution thread. This can improve the performance and user experience of the solution, as well as avoid governor limits and timeouts.

Events do not participate in a transaction scope. This means that events are independent of the transaction that publishes them, and they do not affect the rollback or commit behavior of the transaction. This can avoid unwanted side effects and errors in the solution, as well as decouple the logic from the data.

Verified Reference: https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_intro.htm https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_considerations.htm

Three steps that the administrator should take to implement this functionality are:

Create an External Data Sourcepointing to the external system's database. An External Data Source is a type of metadata that defines the connection and authentication information for an external system that stores data outside of Salesforce. The administrator can create an External Data Source using the Lightning Connect OData 2.0 or 4.0 adapters, which support read-only access to data in relational databases.

Create an External Object for each table of accounting data in the external system. An External Object is a type of custom object that maps to a table in an external system. The administrator can create an External Object for each table of accounting data that they want to access from Salesforce, and define its fields and relationships accordingly.

Create an Indirect Lookup field to connect to the Account. An Indirect Lookup field is a type of custom field that links a child External Object record to a parent standard or custom object record. The administrator can create an Indirect Lookup field on the External Object that references the Account object, and specify the external column name and value that match the Account ID.

Verified Reference: https://help.salesforce.com/s/articleView?id=sf.external_object_overview.htm&type=5https://help.salesforce.com/s/articleView?id=sf.external_object_relationships.htm&type=5

The reason why Fulfillment Order does not appear as an option when creating a rollup field on the Order Summary object is that the Order Summary field on the Fulfillment Order object is a Lookup. A Lookup field is a type of custom field that creates a relationship between two objects, but does not support rollup summary fields. To create a rollup summary field, the relationship between the objects must be master-detail, which means that the child record cannot exist without its parent record. Verified Reference: https://help.salesforce.com/s/articleView?id=sf.custom_field_types.htm&type=5https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm&type=5

The best way for a user to view the information exchanged between the payment platform and the external payment gateways is to navigate to Payment Gateway Logs related list on the corresponding Order Payment Summary. A Payment Gateway Log is a record that captures the request and response messages between the payment platform and the external payment gateways, such as Stripe, PayPal, etc. A PaymentGateway Log has a lookup relationship to the Order Payment Summary object, which represents a payment made for an order or part of an order. A user can use the Payment Gateway Logs related list on the Order Payment Summary page to view the details of thepayment transactions, such as the request and response payloads, status codes, timestamps, etc. Verified Reference: https://help.salesforce.com/s/articleView?id=sf.order_management_payment_gateway_log.htm&type=5https://help.salesforce.com/s/articleView?id=sf.order_management_order_payment_summary.htm&type=5

The number of Fulfillment Orders that would be created for this order is one per destination, totaling 3. A Fulfillment Order is a record that represents a group of products in an order that are fulfilled together from the same location. A Fulfillment Order has a lookup relationship to the Order Summary object, and it contains information such as the fulfillment location, delivery method, status, etc. The number of Fulfillment Orders created depends on three factors: Fulfillment Location, Delivery Method and Recipient Address. These factors determine how the Order Items are grouped and allocated to Fulfillment Orders based on routing rules and inventory availability. In this case, since the products must be shippedto three different locations, three Fulfillment Orders are created for each destination. Verified Reference:https://help.salesforce.com/s/articleView?id=sf.order_management_fulfillment_order.htm&type=5

Two ways that Order Management licenses can be assigned are:

By Permission Set. A Permission Set is a collection of settings andpermissions that give users access to various tools and functions in Salesforce. A Permission Set can be assigned to individual users or groups of users, regardless of their profile or role. An administrator can create a Permission Set that includes the Order Management User permission, which enables users to access Order Management features and data. The administrator can then assign this Permission Set to the users who need Order Management licenses.

By User. A User is a record that represents a person who can log in and access Salesforce. A User has various fields and settings that determine their access and permissions in Salesforce, such as profile, role, license type, etc. An administrator can assign an Order Management license to a user by editing theuser record and selecting Order Management User from the License Type picklist. The administrator can also enable the Order Management User permission on the user record.

Verified Reference: https://help.salesforce.com/s/articleView?id=sf.order_management_user_permission.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.users_understanding_license_types.htm&type=5