Salesforce CRT-450 Actual Questions

The sfdx commands that can be used to add testing data to a Developer sandbox are forced: data:bulk:upsert and forced: data:tree:upsert. The forced: data:bulk:upsert command uses Bulk API 2.0 to upsert records from a CSV file into an org1. The forced: data:tree:upsert command uses the SObject Tree Save API to import records from a JSON file that describes objects and relationships2. The forced: data:object:upsert command is not valid, and the forced: data:async:upsert command does not exist.

References:

• Salesforce CLI Command Reference - force:data:bulk:upsert
• Salesforce CLI Command Reference - force:data:tree:upsert

The code snippet above is not bulkified, meaning it does not handle multiple records efficiently. It performs a SOQL query inside a for loop, which can quickly hit the governor limit of 100 SOQL queries per transaction. The best technique to avoid reaching the governor limit is to refactor the code above to perform only one SOQL query, filtering by the Set of opportunityIds. This way, the code will retrieve all the OpportunityLineItems related to the given opportunityIds in one query, and avoid unnecessary iterations and queries.

References:

• Apex Developer Guide on Bulkifying Code (1)
• Apex Developer Guide on SOQL For Loops (2)
• Apex Developer Guide on System.Limits Class (3)

Change sets are the native way to move metadata customizations between sandboxes and your production environment1. They have the following characteristics:

• Change sets can only be used between related organizations, such as those that are linked by a deployment connection2. You cannot use change sets to deploy metadata to unrelated organizations, such as those belonging to different customers.
• Change sets can only deploy metadata, not data. You cannot use change sets to transfer records, such as accounts, contacts, or custom objects records, from one organization to another2. To move data between organizations, you need to use a data loader tool or an API.
• Sending a change set between two orgs requires a deployment connection to be established between the source and the target org2. The deployment connection allows the source org to upload outbound change sets and the target org to receive inbound change sets. The target org can then deploy the change set to apply the metadata changes.
• Change sets can deploy custom settings data only if the custom settings are defined as hierarchy and not list. Also, the custom settings data can only be deployed to other sandboxes, not to production3.
• Deployment is done in a one-way, single transaction. The source org sends the change set to the target org, but the target org does not send any confirmation or feedback to the source org. The deployment is either successful or fails as a whole, and it cannot be undone2. References:
• Everything You Need to Know About Salesforce Change Sets
• Deployments by using change sets - Salesforce Tutorial
• Using Change Sets To Deploy Apex - Salesforce Developers

In Salesforce, the sharing context is determined by the definition of the class where a method is defined, not where it is invoked or instantiated. Since there’s no “with sharing” or “without sharing” keyword in the class definition in the provided example, it operates in system context. In system context, Apex code has access to all objects and fields— object permissions, field-level security, sharing rules aren’t applied for the current user. References: Apex Developer Guide