최신Salesforce Platform Developer II - PDII무료샘플문제

A. Add Test.startTest() and Test.setMock before and Test.stopTest() after CalloutUtil.sendAccountUpdate.

B. Add Test.startTest() before and Test.stopTest() after CalloutUtil.sendAccountUpdate.

C. Add Test.startTest() before and Test.setMock and Test.stopTest() after CalloutUtil.sendAccountUpdate.

D. Add if (!Test.isRunningTest()) around CalloutUtil.sendAccountUpdate.

A. Java
MyRemoter remote = new MyRemoter();
Account a = remote.getAccount('TestAccount');
System.assertEquals( 'TestAccount', a.Name );

B. Java
MyRemoter remote = new MyRemoter('TestAccount');
Account a = remote.getAccount();
System.assertEquals( 'TestAccount' , a.Name );

C. Java
Account a = MyRemoter.getAccount('TestAccount');
System.assertEquals( 'TestAccount', a.Name );

D. Java
Account a = controller.getAccount('TestAccount');
System.assertEquals( 'TestAccount', a.Name );

A. Java
List<Opportunity> opportunities = Database.query('SELECT Id, Amount from Opportunity'); for(Opportunity opp: opportunities){
// perform operation here
}

B. Java
List<Opportunity> opportunities = [SELECT Id, Amount from Opportunity]; for(Opportunity opp: opportunities){
// perform operation here
}

C. Java
Map<Id, Opportunity> opportunities = new Map<Id, Opportunity>([SELECT Id, Amount from Opportunity]); for(Id oppId: opportunities.keySet()){
// perform operation here
}

D. Java
for(Opportunity opp: [SELECT Id, Amount from Opportunity]){
// perform operation here
}

A. Create a Hierarchical custom setting to store user preferences.5

B. Use the $User global variable to retrieve the user preferences.4

C. Use the $Label global value provider.89

D. Use the $Locale value provider to retrieve the user preferences.67

A. A Database.Schedulable and Database.Batchable class that queries the Catalog Item object and updates the Catalog Items if the Catalog CurrencyIsoCode is different.

B. An after update trigger on Catalog that updates the Catalog Items if the Catalog's CurrencyIsoCode is different.

C. An after insert trigger on Catalog Item that updates the Catalog Items if the Catalog's CurrencyIsoCode is different.

D. A Database.Schedulable and Database.Batchable class that queries the Catalog object and updates the Catalog Items if the Catalog CurrencyIsoCode is different.

A. String.valueOf

B. String.format

C. Date.parse

D. Date.format

A. Lightning-navigation

B. Lightning-layout-item

C. Lightning-layout

D. Lightning-input-location

A. System.LimitException: Too many SOQL Queries on Contact

B. System.QueryException: List has more than one row for Assignment on Account

C. System.QueryException: Too many DML Statement errors on Contact

D. System.LimitException: Too many SOQL Queries on Account

A. Create a criteria-based sharing rule on the Convention Attendee custom object to share the records with a group of Event Reviewers.

B. Create an after insert trigger on the Convention Attendee custom object, and use Apex Sharing Reasons and Apex Managed Sharing.

C. Create criteria-based sharing rules on the Convention Attendee custom object to share the records with the Event Reviewers.

D. Create a before insert trigger on the Convention Attendee custom object, and use Apex Sharing Reasons and Apex Managed Sharing.

A. The callouts will be made in an Apex trigger.

B. The callouts will be made using the REST API.

C. Over 10 callouts will be made in a single transaction.

D. The callout could take longer than 60 seconds to complete.

A. Enclose System.enqueueJob(new OrderQueueableJob()) within Test.startTest and Test.stopTest().

B. Implement seeAllData=true to ensure the Queueable job is able to run in bulk mode.2

C. Ensure the running user of the test class has, at least, the View All permission on the Order object.

D. Implement Te3st.isRunningTest() to prevent chaining jobs during test execution.

A. Apex batch job that counts the number of Opportunity records

B. SOQL for loop that counts the number of Opportunities records

C. COUNT () SOQL aggregate query on the Opportunity object

D. SUM () SOQL aggregate query on the Opportunity object

A. Page Layouts should never be deployed via Change Sets, as this causes Field-Level Security to be reset and fields to disappear.42

B. A sandbox should be created to use as a unified testing environment instead of deploying Change Sets directly to produ43ction.

C. The administrators are deploying their own Change Sets, thus deleting each other's fields from the objects in production.3839

D. The admin40istrators are deploying their own Change Sets over each othe41r, thus replacing entire Page Layouts in production.