Download Full Version PDI Salesforce Exam

 To use a custom exception, you can create an instance of the custom exception class and use the throw keyword to throw the exception. You can also optionally provide a custom error message or a chained exception cause as arguments to the custom exception constructor. The syntax for throwing a custom exception is:

throw new CustomException(optional_message, optional_cause);

Therefore, the options B and D are valid ways to fire the custom exception in Apex. The options A and C are invalid because they only create an instance of the custom exception class, but do not throw it. Also, the option C uses single quotes instead of double quotes for the error message, which is not allowed in Apex. References: You can find more information about custom exceptions in the Apex Developer Guide and the Apex Reference Guide on Salesforce’s official website. You can also read this blog post for a tutorial on creating and using custom exceptions.

The developer should select the Allow reparenting option on the master-detail relationship between Order and OrderItem. This option enables the developer to change the parent record of a child record in a master-detail relationship, which is also known as reparenting. By default, reparenting is not allowed in master-detail relationships, because the child record inherits the sharing and security settings of its parent record. However, in some cases, such as splitting an order into multiple orders, reparenting may be necessary to move some existing OrderItem records to a new Order record. The developer can use the Apex Data Manipulation Language (DML) statements, such as update or upsert, to change the parent record of the OrderItem records.

Changing the master-detail relationship to an external lookup relationship is not a valid option, because external lookup relationships are only available for external objects, which are objects that map to data stored outside Salesforce. Adding without sharing to the Apex class declaration is not a relevant option, because it only affects the sharing rules that apply to the Apex class, not the relationship between the objects. Creating a junction object between OrderItem and Order is not a suitable option, because it would create a many-to-many relationship between the objects, which is not the desired outcome.

References: Master-Detail Relationships, Reparent Records in Master-Detail Relationships, Prepare for Your Salesforce Platform Developer I Credential

 A Full Sandbox is a type of sandbox that has a complete duplicate copy of the production org, including all the data and configuration. A Full Sandbox is useful for testing and development purposes, as it allows the developer to perform any changes or operations without affecting the production org. A Full Sandbox also supports performance testing, load testing, and staging1.

The other options are not correct because:

• A Developer Pro Sandbox is a type of sandbox that has a copy of the production org’s configuration (metadata) and some data. A Developer Pro Sandbox is limited by storage space and can only hold up to 1 GB of data1.
• A Partial Copy Sandbox is a type of sandbox that has a copy of the production org’s configuration and a sample of the data. A Partial Copy Sandbox is limited by storage space and can only hold up to 5 GB of data. The data is selected based on a sandbox template that defines the objects and records to include1.
• A Production org is not a duplicate copy of itself, but the original org where the live data and processes are stored. A Production org is not meant for testing or development purposes, as any changes or operations can affect the users and the business2.

References:

• 1: Sandbox Types and Templates
• 2: Salesforce Environments

A record-triggered flow is an automation tool that allows you to run a flow when a record is created, updated, or deleted1. You can use a record-triggered flow to meet the business requirement of deleting associated opportunity records when the related account is deleted. You can configure the flow to trigger when an account is deleted, and then use the Get Records element to query the related opportunities. Then, you can use the Delete Records element to delete the queried opportunities2. This way, you can ensure that the opportunity records are proactively deleted when the account is deleted, without writing any code.

Workflow rules and process builder are also automation tools that can run when a record is created, updated, or deleted, but they cannot delete records directly. You would need to use an Apex action or a custom field update to achieve the same functionality3 . Scheduled jobs are Apex classes that run at specified intervals, such as daily or weekly. They are not suitable for the business requirement of deleting records when another record is deleted, as they are not triggered by record changes.

References:

• Record-Triggered Flows | Salesforce Help
• Delete Records with a Record-Triggered Flow | Salesforce Trailhead
• Workflow Rules | Salesforce Help
• [Process Builder | Salesforce Help]
• [Scheduled Apex | Apex Developer Guide | Salesforce Developers]