Salesforce Updated CRT-450 Exam Questions and Answers by livia

ISV Package Development:

The ISV is developing a managed package.

They have an Apex class BodyFat with a method calculateBodyFat().

Requirement:

Ensure calculateBodyFat() is accessible by consumers outside the package namespace.

Solution:

To allow methods in a managed package to be accessible outside the package namespace, they must be declared as global.

Option B: Declare the class and method using the global access modifier.

Correct Approach.

Explanation:

Global Classes and Methods:

In managed packages, only classes and methods declared as global are accessible outside the package namespace.

Declaration:

global class BodyFat {

global void calculateBodyFat() {

// method implementation

}

}

Important Notes:

Public classes and methods in managed packages are accessible only within the namespace.

Global is required to expose the functionality to subscribers.

To associate multiple Engineering_Support__c records to a single Opportunity and display aggregate information on the Opportunity:

Option B: Master-detail field from Engineering_Support__c to Opportunity

Explanation:

Master-Detail Relationship: Creating a master-detail relationship from Engineering_Support__c (detail) to Opportunity (master) allows multiple support records to be related to one Opportunity.

Aggregate Information: Master-detail relationships support roll-up summary fields, enabling aggregate calculations (like COUNT, SUM) on the Opportunity object based on related Engineering_Support__c records.

To prevent duplicate Order records from being created when updates come from the OMS:

Option B: Use the order number from the OMS as an external ID.

Explanation: Setting the Order Number as an External ID allows Salesforce to recognize records based on this unique identifier during upsert operations.

Option D: Ensure that the order number in the OMS is unique.

Explanation: Having a unique Order Number in the OMS ensures that each order can be accurately identified and matched in Salesforce.

Why These Actions Prevent Duplicates:

By using upsert with the External ID, the integration can update existing orders instead of creating new ones.

// Example of upsert operation using External ID

upsert orderRecord Order_Number__c;

