@palerock/exam-qa 1.0.6-patch1 → 1.0.6-patch10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/index.html +1 -1
- package/dist/static/css/app.e3a8483dfde3024c7e501c1e46ada2a8.css +2 -0
- package/dist/static/css/app.e3a8483dfde3024c7e501c1e46ada2a8.css.map +1 -0
- package/dist/static/js/app.4a28c4a16706c6bcac16.js +2 -0
- package/dist/static/js/app.4a28c4a16706c6bcac16.js.map +1 -0
- package/dist/static/js/manifest.3ad1d5771e9b13dbdad2.js.map +1 -1
- package/lib-json/Dev1/345/237/272/347/241/200/351/242/230.json +1347 -0
- package/lib-json/Dev1/346/250/241/346/213/237/345/215/267A.json +1473 -0
- package/lib-json/Dev1/346/250/241/346/213/237/345/215/267B.json +1469 -0
- package/lib-json/Dev1/346/265/201/347/250/213/350/207/252/345/212/250/345/214/226/344/270/216/351/200/273/350/276/2211.json +1519 -0
- package/lib-json/Dev1/346/265/201/347/250/213/350/207/252/345/212/250/345/214/226/344/270/216/351/200/273/350/276/2212.json +997 -0
- package/lib-json/Dev1/346/265/213/350/257/225_/350/260/203/350/257/225_/351/203/250/347/275/262.json +889 -0
- package/lib-json/Dev1/347/224/250/346/210/267/347/225/214/351/235/242.json +1191 -0
- package/lib-json/Salesforce-Admin-201-[Set-10].json +769 -0
- package/lib-json/Salesforce-Admin-201-[Set-1].json +604 -0
- package/lib-json/Salesforce-Admin-201-[Set-2].json +621 -0
- package/lib-json/Salesforce-Admin-201-[Set-3].json +650 -0
- package/lib-json/Salesforce-Admin-201-[Set-4].json +636 -0
- package/lib-json/Salesforce-Admin-201-[Set-5].json +640 -0
- package/lib-json/Salesforce-Admin-201-[Set-6].json +640 -0
- package/lib-json/Salesforce-Admin-201-[Set-7].json +592 -0
- package/lib-json/Salesforce-Admin-201-[Set-8].json +539 -0
- package/lib-json/Salesforce-Admin-201-[Set-9].json +539 -0
- package/lib-json/map.json +7 -33
- package/package.json +3 -2
- package/dist/static/css/app.d3e969a579969be885a3462a1e12e37f.css +0 -2
- package/dist/static/css/app.d3e969a579969be885a3462a1e12e37f.css.map +0 -1
- package/dist/static/js/app.53370ddfe5eba6a10565.js +0 -2
- package/dist/static/js/app.53370ddfe5eba6a10565.js.map +0 -1
@@ -0,0 +1,1347 @@
|
|
1
|
+
{
|
2
|
+
"title": "Dev1基础题",
|
3
|
+
"category": "Dev1-自由部落侠",
|
4
|
+
"questions": [
|
5
|
+
{
|
6
|
+
"describe": "A company has a custom object, Sales_Help_Request__c, that has a Lookup relationship to Opportunity. The Sales_Help_Request__c has a number field, Number_of_Hours__c, that represents the amount of time spent on the Sales_Help_Request__c.\nA developer is tasked with creating a field, Total_hours__c, on Opportunity that should be the sum of all of the Number_of_Hours__c values for the Sales_Help_Request__c records related to that Opportunity.\nWhat should the developer use to implement this?",
|
7
|
+
"answerOptions": [
|
8
|
+
{
|
9
|
+
"describe": "A trigger on the Opportunity object",
|
10
|
+
"isRight": false
|
11
|
+
},
|
12
|
+
{
|
13
|
+
"describe": "A roll-up summary field on the Opportunity object",
|
14
|
+
"isRight": false
|
15
|
+
},
|
16
|
+
{
|
17
|
+
"describe": "A record-triggered flow on the Sales_Help_Request__c object",
|
18
|
+
"isRight": true
|
19
|
+
},
|
20
|
+
{
|
21
|
+
"describe": "A roll-up summary field on the Sales_Help_Request__c object.",
|
22
|
+
"isRight": false
|
23
|
+
}
|
24
|
+
],
|
25
|
+
"hashCode": "1995171579"
|
26
|
+
},
|
27
|
+
{
|
28
|
+
"describe": "AW Computing tracks order information in custom objects called Order__c and Order_Line__c. Currently, all shipping information is stored in the Order__c object.\nThe company wants to expand its order application to support split shipments so that any number of Order_Line__c records on a single Order__c can be shipped to different locations.\nWhat should a developer add to fulfill this requirement?",
|
29
|
+
"answerOptions": [
|
30
|
+
{
|
31
|
+
"describe": "Order_Shipment_Group__c object and master-detail field on Order__c",
|
32
|
+
"isRight": false
|
33
|
+
},
|
34
|
+
{
|
35
|
+
"describe": "Order_Shipment_Group__c object and master-detail field on Order_Line__c",
|
36
|
+
"isRight": false
|
37
|
+
},
|
38
|
+
{
|
39
|
+
"describe": "Order_Shipment_Group__c object and master-detail field on Order_Shipment_Group__c",
|
40
|
+
"isRight": false
|
41
|
+
},
|
42
|
+
{
|
43
|
+
"describe": "Order_Shipment_Group__c object and master-detail field on Order__c and Order_Line__c",
|
44
|
+
"isRight": true
|
45
|
+
}
|
46
|
+
],
|
47
|
+
"hashCode": "1995171577"
|
48
|
+
},
|
49
|
+
{
|
50
|
+
"describe": "UC is developing a process for their sales teams that requires all sales reps to go through a set of scripted steps with each new customer they create.\nIn the first step of collecting information, UC's ERP system must be checked via a REST endpoint to see if the customer exists. If the customer exists, the data must be presented to the sales rep in Salesforce.\nWhich two should a developer implement to satisfy the requirements?Choose 2 answers",
|
51
|
+
"answerOptions": [
|
52
|
+
{
|
53
|
+
"describe": "Trigger",
|
54
|
+
"isRight": false
|
55
|
+
},
|
56
|
+
{
|
57
|
+
"describe": "Invocable method",
|
58
|
+
"isRight": false
|
59
|
+
},
|
60
|
+
{
|
61
|
+
"describe": "Flow",
|
62
|
+
"isRight": true
|
63
|
+
},
|
64
|
+
{
|
65
|
+
"describe": "Future method",
|
66
|
+
"isRight": true
|
67
|
+
}
|
68
|
+
],
|
69
|
+
"hashCode": "1995171576"
|
70
|
+
},
|
71
|
+
{
|
72
|
+
"describe": "A developer created these three roll-up summary fields on the custom object, Project__c:\nTotal_Timesheets__c\nTotal_Approved_Timesheets__c\nTotal_Rejected_Timesheet__c\nThe developer is asked to create a new field that shows the ratio between rejected and approved timesheets for a given project.\nWhich should the developer use to implement the business requirement in order to minimize maintenance overhead?",
|
73
|
+
"answerOptions": [
|
74
|
+
{
|
75
|
+
"describe": "Roll-up summary field",
|
76
|
+
"isRight": false
|
77
|
+
},
|
78
|
+
{
|
79
|
+
"describe": "Record-triggered flow",
|
80
|
+
"isRight": false
|
81
|
+
},
|
82
|
+
{
|
83
|
+
"describe": "Formula field",
|
84
|
+
"isRight": true
|
85
|
+
},
|
86
|
+
{
|
87
|
+
"describe": "Apex trigger",
|
88
|
+
"isRight": false
|
89
|
+
}
|
90
|
+
],
|
91
|
+
"hashCode": "1995171571"
|
92
|
+
},
|
93
|
+
{
|
94
|
+
"describe": "A business has a proprietary Order Management System (OMS) that creates orders from their website and the orders.When the order Is created in the OMS,an integration also creates an order record In Salesforce relates it to the contact as identified by the email on the order As the order goes through different stages inOMS, the integration also updates it in Salesforce.\nIt is noticed that each update from the OMS creates new order record in Salesforce.\nWhich two actions will prevent the duplicate order records from being created in Salesforce?\nChoose 2 answers",
|
95
|
+
"answerOptions": [
|
96
|
+
{
|
97
|
+
"describe": "Ensure that the order number in the OMS is unique",
|
98
|
+
"isRight": true
|
99
|
+
},
|
100
|
+
{
|
101
|
+
"describe": "Use the order number from the OMS as an external ID.",
|
102
|
+
"isRight": true
|
103
|
+
},
|
104
|
+
{
|
105
|
+
"describe": "Use the email on the contact record as an external ID.",
|
106
|
+
"isRight": false
|
107
|
+
},
|
108
|
+
{
|
109
|
+
"describe": "Write a before trigger on the order object to delete any duplicates",
|
110
|
+
"isRight": false
|
111
|
+
}
|
112
|
+
],
|
113
|
+
"hashCode": "1988674164"
|
114
|
+
},
|
115
|
+
{
|
116
|
+
"describe": "UH is using Salesforce to capture job applications. A salesforce administrator created two custom objects; Job__c acting as the master object, Job_Application__c acting as the detail.\nWithin the Job__c object, a custom multi-select picklist, Preferred_Locations__c, contains a list of approved status for the position. Each Job_Application__c record relates to a Contact within the system through a master-detail relationship.\nRecruiters have requested the ability to view whether the Contact's Mailing State value matches a value selected on the Preferred_Locations__c field, within the Job_Application__c record. Recruiters would like this value to be kept in sync, if changes occur to the Contact's Mailing State or if the Job's Preferred_Locations__c field is updated.\nWhat is the recommended tool a developer should use to meet the business requirement?",
|
117
|
+
"answerOptions": [
|
118
|
+
{
|
119
|
+
"describe": "Apex trigger",
|
120
|
+
"isRight": true
|
121
|
+
},
|
122
|
+
{
|
123
|
+
"describe": "Record-triggered flow",
|
124
|
+
"isRight": false
|
125
|
+
},
|
126
|
+
{
|
127
|
+
"describe": "Formula field",
|
128
|
+
"isRight": false
|
129
|
+
},
|
130
|
+
{
|
131
|
+
"describe": "Process Builder",
|
132
|
+
"isRight": false
|
133
|
+
}
|
134
|
+
],
|
135
|
+
"hashCode": "1988674162"
|
136
|
+
},
|
137
|
+
{
|
138
|
+
"describe": "A large corporation stores Orders and Line Items in Salesforce for different lines of business. Users are allowed see Orders across the entire organization,but,for security purposes, should only be able to see the Line Orders in their line of business.\nWhich type of relationship should be used between Line Items and Orders?",
|
139
|
+
"answerOptions": [
|
140
|
+
{
|
141
|
+
"describe": "Master-Detail",
|
142
|
+
"isRight": true
|
143
|
+
},
|
144
|
+
{
|
145
|
+
"describe": "Lookup",
|
146
|
+
"isRight": false
|
147
|
+
},
|
148
|
+
{
|
149
|
+
"describe": "Direct Lookup",
|
150
|
+
"isRight": false
|
151
|
+
},
|
152
|
+
{
|
153
|
+
"describe": "Indirect Lookup",
|
154
|
+
"isRight": false
|
155
|
+
}
|
156
|
+
],
|
157
|
+
"hashCode": "1988674161"
|
158
|
+
},
|
159
|
+
{
|
160
|
+
"describe": "What Is an example of a polymorphic lookup field in Salesforce?",
|
161
|
+
"answerOptions": [
|
162
|
+
{
|
163
|
+
"describe": "The WhatId field on the standard Event object",
|
164
|
+
"isRight": true
|
165
|
+
},
|
166
|
+
{
|
167
|
+
"describe": "A custom field,Link_c, on the standard Contact object that looks up to an Account",
|
168
|
+
"isRight": false
|
169
|
+
},
|
170
|
+
{
|
171
|
+
"describe": "The LeadId and ContactId fields on the standard Campaign Member object",
|
172
|
+
"isRight": false
|
173
|
+
},
|
174
|
+
{
|
175
|
+
"describe": "The ParentId field on the standard Account object",
|
176
|
+
"isRight": false
|
177
|
+
}
|
178
|
+
],
|
179
|
+
"hashCode": "1988674157"
|
180
|
+
},
|
181
|
+
{
|
182
|
+
"describe": "When a user edits the Postal Code on an Account,a custom Account text field named \"Tim updated based on the values in another custom object called PostalCodeToTimezone_c.\nWhat is the optimal way to implement this feature?",
|
183
|
+
"answerOptions": [
|
184
|
+
{
|
185
|
+
"describe": "Create an account approval proce",
|
186
|
+
"isRight": false
|
187
|
+
},
|
188
|
+
{
|
189
|
+
"describe": "Build a flow with Flow Builder.",
|
190
|
+
"isRight": true
|
191
|
+
},
|
192
|
+
{
|
193
|
+
"describe": "Create a formula field.",
|
194
|
+
"isRight": false
|
195
|
+
},
|
196
|
+
{
|
197
|
+
"describe": "Build an account assignment rule,",
|
198
|
+
"isRight": false
|
199
|
+
}
|
200
|
+
],
|
201
|
+
"hashCode": "1988674131"
|
202
|
+
},
|
203
|
+
{
|
204
|
+
"describe": "In terms of the MVC paradigm,what are two advantages of lmplementing the viewlayer of application using Lightning Web Component-based development over Visualforce?\nChoose 2 answers",
|
205
|
+
"answerOptions": [
|
206
|
+
{
|
207
|
+
"describe": "Built-in standard and custom set controllers",
|
208
|
+
"isRight": false
|
209
|
+
},
|
210
|
+
{
|
211
|
+
"describe": "Log capturing via the Debug Logs Setup page",
|
212
|
+
"isRight": false
|
213
|
+
},
|
214
|
+
{
|
215
|
+
"describe": "Self-contained and reusable units of an application",
|
216
|
+
"isRight": true
|
217
|
+
},
|
218
|
+
{
|
219
|
+
"describe": "Rich component ecosystem",
|
220
|
+
"isRight": true
|
221
|
+
}
|
222
|
+
],
|
223
|
+
"hashCode": "1988674130"
|
224
|
+
},
|
225
|
+
{
|
226
|
+
"describe": "UC uses a custom object called Vendor. The Vendor custom object has relationship with the standard Account object.\nBased on some internal discussions, the UC administrator tried to change the master-detail lookup relationship, but was not able to do so.\nWhat is a possible reason that this change was not permitted?",
|
227
|
+
"answerOptions": [
|
228
|
+
{
|
229
|
+
"describe": "The organization wide default for the Vendor object is Public Read/Write.",
|
230
|
+
"isRight": false
|
231
|
+
},
|
232
|
+
{
|
233
|
+
"describe": "Some of the Vendor records have null for the Account field.",
|
234
|
+
"isRight": false
|
235
|
+
},
|
236
|
+
{
|
237
|
+
"describe": "The Account object has a roll-up summary field on the Vendor object.",
|
238
|
+
"isRight": true
|
239
|
+
},
|
240
|
+
{
|
241
|
+
"describe": "The Account object does not allow changing a field type for a custom field.",
|
242
|
+
"isRight": false
|
243
|
+
}
|
244
|
+
],
|
245
|
+
"hashCode": "1988674127"
|
246
|
+
},
|
247
|
+
{
|
248
|
+
"describe": "Universal Containers has a support process that allows users to request support from its engineering team using custom object, Engineering_Support_c.\nUsers should be able to associate multiple Engineering Support_c records to a single Opportunty record.Addltionally, aggregate information about the Engineering Support _c records should be shown on the Opportunity record.\nWhat should a developer implement to support these requirements?",
|
249
|
+
"answerOptions": [
|
250
|
+
{
|
251
|
+
"describe": "Lookup field from Engineering_Support_c to Opportunity",
|
252
|
+
"isRight": false
|
253
|
+
},
|
254
|
+
{
|
255
|
+
"describe": "Master-detail field from EngineeringSupport_c to Opportunity",
|
256
|
+
"isRight": true
|
257
|
+
},
|
258
|
+
{
|
259
|
+
"describe": "Lookup field from Opportunity to Engineering Support_c",
|
260
|
+
"isRight": false
|
261
|
+
},
|
262
|
+
{
|
263
|
+
"describe": "Master-detail field from Opportunity to Engineering Support_c",
|
264
|
+
"isRight": false
|
265
|
+
}
|
266
|
+
],
|
267
|
+
"hashCode": "1988674126"
|
268
|
+
},
|
269
|
+
{
|
270
|
+
"describe": "A software company uses the following objects and relationships:\nCase: to handle customer support issues\nDefect_c: a custom object to represent known issues with the company's software\nCase_effect_c: a junction object between Case and Defect_c to represent that a defect is a cause of a customer issue\nCase and Defect_c have Private organization-wide defaults.\nWhat should be done to share a specific case_Defect_c record with a user?",
|
271
|
+
"answerOptions": [
|
272
|
+
{
|
273
|
+
"describe": "Share the parent Case and Defect_c records.",
|
274
|
+
"isRight": true
|
275
|
+
},
|
276
|
+
{
|
277
|
+
"describe": "Share the parent Case record.",
|
278
|
+
"isRight": false
|
279
|
+
},
|
280
|
+
{
|
281
|
+
"describe": "Share the case_Defect_c record.",
|
282
|
+
"isRight": false
|
283
|
+
},
|
284
|
+
{
|
285
|
+
"describe": "Share the parent Defect_c record.",
|
286
|
+
"isRight": false
|
287
|
+
}
|
288
|
+
],
|
289
|
+
"hashCode": "1988674096"
|
290
|
+
},
|
291
|
+
{
|
292
|
+
"describe": "UC has implemented an order management application. Each Order can have one or more Order Line items. The order Line object is related to the Order via a master-detail relationship. For each Order Line item, the total price is calculated by multiplying the Order Line item price with the quantity ordered.\nWhat is the best practice to get the sum of all Order Line item totals on the Order record?",
|
293
|
+
"answerOptions": [
|
294
|
+
{
|
295
|
+
"describe": "Roll-up summary field",
|
296
|
+
"isRight": true
|
297
|
+
},
|
298
|
+
{
|
299
|
+
"describe": "Quick action",
|
300
|
+
"isRight": false
|
301
|
+
},
|
302
|
+
{
|
303
|
+
"describe": "Apex trigger",
|
304
|
+
"isRight": false
|
305
|
+
},
|
306
|
+
{
|
307
|
+
"describe": "Formula field",
|
308
|
+
"isRight": false
|
309
|
+
}
|
310
|
+
],
|
311
|
+
"hashCode": "1988674071"
|
312
|
+
},
|
313
|
+
{
|
314
|
+
"describe": "Which two settings must be defined in order to update a record of a junction object?\nChoose 2 answers",
|
315
|
+
"answerOptions": [
|
316
|
+
{
|
317
|
+
"describe": "Read/write access on the primary relationship",
|
318
|
+
"isRight": true
|
319
|
+
},
|
320
|
+
{
|
321
|
+
"describe": "Read/write access on the junction object",
|
322
|
+
"isRight": false
|
323
|
+
},
|
324
|
+
{
|
325
|
+
"describe": "Read/write access on the secondary relationship",
|
326
|
+
"isRight": true
|
327
|
+
},
|
328
|
+
{
|
329
|
+
"describe": "Read access on the primary relationship",
|
330
|
+
"isRight": false
|
331
|
+
}
|
332
|
+
],
|
333
|
+
"hashCode": "1988674069"
|
334
|
+
},
|
335
|
+
{
|
336
|
+
"describe": "What can be used to override the Account's standard Edit button for Lightning Experience?",
|
337
|
+
"answerOptions": [
|
338
|
+
{
|
339
|
+
"describe": "Lightning action",
|
340
|
+
"isRight": false
|
341
|
+
},
|
342
|
+
{
|
343
|
+
"describe": "Lightning component",
|
344
|
+
"isRight": true
|
345
|
+
},
|
346
|
+
{
|
347
|
+
"describe": "Lightning page",
|
348
|
+
"isRight": false
|
349
|
+
},
|
350
|
+
{
|
351
|
+
"describe": "Lightning flow",
|
352
|
+
"isRight": false
|
353
|
+
}
|
354
|
+
],
|
355
|
+
"hashCode": "1988674068"
|
356
|
+
},
|
357
|
+
{
|
358
|
+
"describe": "Universal Containers is bullding a recruiting app with an Applicant object that stores information about an individual person and a Job object that represents a job. Each applicant may apply for more than one job.\nWhat should a developer implement to represent that an applicant has applied for a job?",
|
359
|
+
"answerOptions": [
|
360
|
+
{
|
361
|
+
"describe": "Master-detail field from Aplicant to Job",
|
362
|
+
"isRight": true
|
363
|
+
},
|
364
|
+
{
|
365
|
+
"describe": "Junction object between Applicant and Job",
|
366
|
+
"isRight": false
|
367
|
+
},
|
368
|
+
{
|
369
|
+
"describe": "Lookup field from Applicant to Job",
|
370
|
+
"isRight": false
|
371
|
+
},
|
372
|
+
{
|
373
|
+
"describe": "Formula field on Applicant that references Job",
|
374
|
+
"isRight": false
|
375
|
+
}
|
376
|
+
],
|
377
|
+
"hashCode": "1988674064"
|
378
|
+
},
|
379
|
+
{
|
380
|
+
"describe": "A developer created a custom order management app that uses an Apex class. The order is represented by an Order object and an OrderItem object that has a master-detail relationship to Order. During order processing, an order may be split into multiple orders.\nWhat should a developer do to allow their code to move some existing OrderItem records to a new Order record?",
|
381
|
+
"answerOptions": [
|
382
|
+
{
|
383
|
+
"describe": "Select the Allow reparenting option on the master-detail relationship.",
|
384
|
+
"isRight": false
|
385
|
+
},
|
386
|
+
{
|
387
|
+
"describe": "Change the master-detail relationship to an external lookup relationship.",
|
388
|
+
"isRight": false
|
389
|
+
},
|
390
|
+
{
|
391
|
+
"describe": "Add without sharing to the Apex class declaration.",
|
392
|
+
"isRight": false
|
393
|
+
},
|
394
|
+
{
|
395
|
+
"describe": "Create a junction object between OrderItem and Order.",
|
396
|
+
"isRight": true
|
397
|
+
}
|
398
|
+
],
|
399
|
+
"hashCode": "1988674041"
|
400
|
+
},
|
401
|
+
{
|
402
|
+
"describe": "A developer is integrating with a legacy on-premise SQL database.\nWhat should the developer use to ensure the data being integrated is matched to the right records in Salesforce?",
|
403
|
+
"answerOptions": [
|
404
|
+
{
|
405
|
+
"describe": "Lookup field",
|
406
|
+
"isRight": false
|
407
|
+
},
|
408
|
+
{
|
409
|
+
"describe": "External ID field",
|
410
|
+
"isRight": true
|
411
|
+
},
|
412
|
+
{
|
413
|
+
"describe": "Formula field",
|
414
|
+
"isRight": false
|
415
|
+
},
|
416
|
+
{
|
417
|
+
"describe": "External Object",
|
418
|
+
"isRight": false
|
419
|
+
}
|
420
|
+
],
|
421
|
+
"hashCode": "1988674035"
|
422
|
+
},
|
423
|
+
{
|
424
|
+
"describe": "UC uses a Master-Detail relationship and stores the availability date on each Line Item of an Order and Orders are only shipped when all of the Line Items \nare available.\nWhich method should be used to calculate the estimated ship date for an Order?",
|
425
|
+
"answerOptions": [
|
426
|
+
{
|
427
|
+
"describe": "Use a LATEST formula on each of the latest availability date fields.",
|
428
|
+
"isRight": false
|
429
|
+
},
|
430
|
+
{
|
431
|
+
"describe": "Use a CEILING formula on each of the latest availability date fields.",
|
432
|
+
"isRight": false
|
433
|
+
},
|
434
|
+
{
|
435
|
+
"describe": "Use a MAX Roll-Up Summary field on the latest availability date fields.",
|
436
|
+
"isRight": true
|
437
|
+
},
|
438
|
+
{
|
439
|
+
"describe": "Use a DAYS formula on each of the availability date fields and a COUNT Roll-Up Summary field on the Order.",
|
440
|
+
"isRight": false
|
441
|
+
}
|
442
|
+
],
|
443
|
+
"hashCode": "1988674006"
|
444
|
+
},
|
445
|
+
{
|
446
|
+
"describe": "A developer created these three roll-up summary fields on the custom object, Project__c:\nTotal_Timesheets__c\nTotal_Approved_Timesheets__c\nTotal_Rejected_Timesheet__c\nThe developer is asked to create a new field that shows the ratio between rejected and approved timesheets for a given project.\nWhat are two benefits of choosing a formula field instead of an Apex trigger to fulfill the request? Choose 2 answers",
|
447
|
+
"answerOptions": [
|
448
|
+
{
|
449
|
+
"describe": "A test class will validate the formula field during deployment.",
|
450
|
+
"isRight": false
|
451
|
+
},
|
452
|
+
{
|
453
|
+
"describe": "Using a formula field reduces maintenance overhead.",
|
454
|
+
"isRight": true
|
455
|
+
},
|
456
|
+
{
|
457
|
+
"describe": "A formula field will calculate the value retroactively for existing records.",
|
458
|
+
"isRight": true
|
459
|
+
},
|
460
|
+
{
|
461
|
+
"describe": "A formula field will trigger existing automation when delpoyed.",
|
462
|
+
"isRight": false
|
463
|
+
}
|
464
|
+
],
|
465
|
+
"hashCode": "1988673328"
|
466
|
+
},
|
467
|
+
{
|
468
|
+
"describe": "In the Lightning UI, where should a developer look to find information about a Paused Flow Interview?",
|
469
|
+
"answerOptions": [
|
470
|
+
{
|
471
|
+
"describe": "In the system debug log by filtering on Paused Flow Interview",
|
472
|
+
"isRight": false
|
473
|
+
},
|
474
|
+
{
|
475
|
+
"describe": "On the Paused Flow Interviews related list for a given record",
|
476
|
+
"isRight": false
|
477
|
+
},
|
478
|
+
{
|
479
|
+
"describe": "On the Paused Flow Interviews component on the Home page",
|
480
|
+
"isRight": true
|
481
|
+
},
|
482
|
+
{
|
483
|
+
"describe": "In the Paused Interviews section of the Apex Flex Queue",
|
484
|
+
"isRight": false
|
485
|
+
}
|
486
|
+
],
|
487
|
+
"hashCode": "1988673326"
|
488
|
+
},
|
489
|
+
{
|
490
|
+
"describe": "What are two benefits of using declarative customizations over code? Choose 2 answers",
|
491
|
+
"answerOptions": [
|
492
|
+
{
|
493
|
+
"describe": "Declarative customizations automatically update with each Salesforce release.",
|
494
|
+
"isRight": true
|
495
|
+
},
|
496
|
+
{
|
497
|
+
"describe": "Declarative customizations cannot generate run time errors.",
|
498
|
+
"isRight": false
|
499
|
+
},
|
500
|
+
{
|
501
|
+
"describe": "Declarative customizations automatically generate test classes.",
|
502
|
+
"isRight": false
|
503
|
+
},
|
504
|
+
{
|
505
|
+
"describe": "Declarative customizations generally require less maintenance.",
|
506
|
+
"isRight": true
|
507
|
+
}
|
508
|
+
],
|
509
|
+
"hashCode": "1988673323"
|
510
|
+
},
|
511
|
+
{
|
512
|
+
"describe": "The values 'High', 'Medium', and 'Low' are identified as common values for multiple picklists across different objects.\nWhat is an approach a developer can take to streamline maintenance of the picklists and their values, while also restricting \nthe values to the ones mentioned above?",
|
513
|
+
"answerOptions": [
|
514
|
+
{
|
515
|
+
"describe": "Create the Picklist on each object and use a Global Picklist Value Set containing the values.",
|
516
|
+
"isRight": true
|
517
|
+
},
|
518
|
+
{
|
519
|
+
"describe": "Create the Picklist on each object as a required field and select \"Display values alphabetically, not in the order entered\".",
|
520
|
+
"isRight": false
|
521
|
+
},
|
522
|
+
{
|
523
|
+
"describe": "Create the Picklist on each object and select \"Restrict picklist to the values defined in the value set\".",
|
524
|
+
"isRight": false
|
525
|
+
},
|
526
|
+
{
|
527
|
+
"describe": "Create the Picklist on each object and add a validation rule to ensure data integrity.",
|
528
|
+
"isRight": false
|
529
|
+
}
|
530
|
+
],
|
531
|
+
"hashCode": "1988673295"
|
532
|
+
},
|
533
|
+
{
|
534
|
+
"describe": "When importing and exporting data into Salesforce, Which two statement are true?\nChoose 2 answers",
|
535
|
+
"answerOptions": [
|
536
|
+
{
|
537
|
+
"describe": "Data import wizard is a client application provided by Salesforce.",
|
538
|
+
"isRight": false
|
539
|
+
},
|
540
|
+
{
|
541
|
+
"describe": "Developer and Developer Pro sandboxes have different storage limits.",
|
542
|
+
"isRight": true
|
543
|
+
},
|
544
|
+
{
|
545
|
+
"describe": "Bulk API can be used to import large data volumes in development environments without bypassing the storage limits.",
|
546
|
+
"isRight": true
|
547
|
+
},
|
548
|
+
{
|
549
|
+
"describe": "Bulk API can be used to bypass the storage limits when importing large data volumes in development environments.",
|
550
|
+
"isRight": false
|
551
|
+
}
|
552
|
+
],
|
553
|
+
"hashCode": "1988673294"
|
554
|
+
},
|
555
|
+
{
|
556
|
+
"describe": "A developer needs to join data received from an integration with an external system with parent records in Salesforce. The data set does not contain the Salesforce IDs of the parent records, but it does have a foreign key attribute that can be used to identify the parent.\n\nWhich action will allow the developer to relate records in the data model without knowing the salesforce ID?",
|
557
|
+
"answerOptions": [
|
558
|
+
{
|
559
|
+
"describe": "Create and populate a custom field on the parent object marked as an External ID.",
|
560
|
+
"isRight": true
|
561
|
+
},
|
562
|
+
{
|
563
|
+
"describe": "Create a custom field on the child object of type Lookup. ",
|
564
|
+
"isRight": false
|
565
|
+
},
|
566
|
+
{
|
567
|
+
"describe": "Create a custom field on the child object of type External Relationship.",
|
568
|
+
"isRight": false
|
569
|
+
},
|
570
|
+
{
|
571
|
+
"describe": "Create and populate a custom field on the parent object marked as Unique.",
|
572
|
+
"isRight": false
|
573
|
+
}
|
574
|
+
],
|
575
|
+
"hashCode": "1988673292"
|
576
|
+
},
|
577
|
+
{
|
578
|
+
"describe": "What is an example of a polymorphic lookup field in Salesforce?",
|
579
|
+
"answerOptions": [
|
580
|
+
{
|
581
|
+
"describe": "The Leadld and Contactld fields on the standard Campaign Member object",
|
582
|
+
"isRight": false
|
583
|
+
},
|
584
|
+
{
|
585
|
+
"describe": "A custom field, Link__c, on the standard Contact object that looks up to an Account or a Campaign",
|
586
|
+
"isRight": false
|
587
|
+
},
|
588
|
+
{
|
589
|
+
"describe": "The Whatld field on the standard Event object",
|
590
|
+
"isRight": true
|
591
|
+
},
|
592
|
+
{
|
593
|
+
"describe": "The Parentld field on the standard Account object",
|
594
|
+
"isRight": false
|
595
|
+
}
|
596
|
+
],
|
597
|
+
"hashCode": "1988673290"
|
598
|
+
},
|
599
|
+
{
|
600
|
+
"describe": "UC wants to assess the advantages of declarative development versus programmatic customization for specific use cases in its Salesforce implementation.\n\nWhat are two characteristics of declarative development over programmatic customization? Choose 2 answers",
|
601
|
+
"answerOptions": [
|
602
|
+
{
|
603
|
+
"describe": "Declarative development has higher design limits and query limits.",
|
604
|
+
"isRight": false
|
605
|
+
},
|
606
|
+
{
|
607
|
+
"describe": "Declarative development can be done using the Setup UI.",
|
608
|
+
"isRight": true
|
609
|
+
},
|
610
|
+
{
|
611
|
+
"describe": "Declarative development does not require maintenance.",
|
612
|
+
"isRight": true
|
613
|
+
},
|
614
|
+
{
|
615
|
+
"describe": "Declarative development does not require Apex test classes.",
|
616
|
+
"isRight": false
|
617
|
+
}
|
618
|
+
],
|
619
|
+
"hashCode": "1988673262"
|
620
|
+
},
|
621
|
+
{
|
622
|
+
"describe": "UC decides to use purely declarative development to build out a new Salesforce application.\nWhich three options can be used to build out the business logic layer for this application?Choose 3 answers",
|
623
|
+
"answerOptions": [
|
624
|
+
{
|
625
|
+
"describe": "Validation Rules",
|
626
|
+
"isRight": true
|
627
|
+
},
|
628
|
+
{
|
629
|
+
"describe": "Remote Actions",
|
630
|
+
"isRight": false
|
631
|
+
},
|
632
|
+
{
|
633
|
+
"describe": "Process Builder",
|
634
|
+
"isRight": true
|
635
|
+
},
|
636
|
+
{
|
637
|
+
"describe": "Flow Builder",
|
638
|
+
"isRight": true
|
639
|
+
},
|
640
|
+
{
|
641
|
+
"describe": "Batch Jobs",
|
642
|
+
"isRight": false
|
643
|
+
}
|
644
|
+
],
|
645
|
+
"hashCode": "1988673260"
|
646
|
+
},
|
647
|
+
{
|
648
|
+
"describe": "A PrimaryId__c custom field exists on the Candidate__c custom object. The field is used to store each candidate's id number and is marked as Unique in the schema definition.\n\nAs part of a data enrichment process, UC has a CSV file that contains updated data for all candidates in the system. The file contains each Candidate's primary id as a data point. UC wants to upload this information into Salesforce, while ensuring all data rows are correctly mapped to a candidate in the system.\n\nWhich technique should the developer implement to streamline the data upload?",
|
649
|
+
"answerOptions": [
|
650
|
+
{
|
651
|
+
"describe": "Create a before insert trigger to correctly map the records. ",
|
652
|
+
"isRight": false
|
653
|
+
},
|
654
|
+
{
|
655
|
+
"describe": "Upload the CSV into a custom object related to Candidate__c. ",
|
656
|
+
"isRight": false
|
657
|
+
},
|
658
|
+
{
|
659
|
+
"describe": "Update the Primaryld__c field definition to mark it as an External Id.",
|
660
|
+
"isRight": true
|
661
|
+
},
|
662
|
+
{
|
663
|
+
"describe": "Create a Process Builder on the Candidate__c object to map the records.",
|
664
|
+
"isRight": false
|
665
|
+
}
|
666
|
+
],
|
667
|
+
"hashCode": "1988673259"
|
668
|
+
},
|
669
|
+
{
|
670
|
+
"describe": "Which two types of process automation can be used to calculate the shipping cost for an Order when the Order is placed and apply a percentage of the shipping cost to some of the related Order Products? Choose 2 answers",
|
671
|
+
"answerOptions": [
|
672
|
+
{
|
673
|
+
"describe": "Process Builder",
|
674
|
+
"isRight": true
|
675
|
+
},
|
676
|
+
{
|
677
|
+
"describe": "Approval Process",
|
678
|
+
"isRight": false
|
679
|
+
},
|
680
|
+
{
|
681
|
+
"describe": "Workflow Rule",
|
682
|
+
"isRight": false
|
683
|
+
},
|
684
|
+
{
|
685
|
+
"describe": "Flow Builder",
|
686
|
+
"isRight": true
|
687
|
+
}
|
688
|
+
],
|
689
|
+
"hashCode": "1988673231"
|
690
|
+
},
|
691
|
+
{
|
692
|
+
"describe": "What are two characteristics related to formulas? Choose 2 answers",
|
693
|
+
"answerOptions": [
|
694
|
+
{
|
695
|
+
"describe": "Formulas can reference themselves.",
|
696
|
+
"isRight": false
|
697
|
+
},
|
698
|
+
{
|
699
|
+
"describe": "Formulas are calculated at runtime and are not stored in the database.",
|
700
|
+
"isRight": true
|
701
|
+
},
|
702
|
+
{
|
703
|
+
"describe": "Fields that are used in a formula field can be deleted or edited without editing the formula.",
|
704
|
+
"isRight": false
|
705
|
+
},
|
706
|
+
{
|
707
|
+
"describe": "Formulas can reference values in related objects.",
|
708
|
+
"isRight": true
|
709
|
+
}
|
710
|
+
],
|
711
|
+
"hashCode": "1988673228"
|
712
|
+
},
|
713
|
+
{
|
714
|
+
"describe": "What is fundamental different between a Mater-Detail relationship and a Lookup relationship?",
|
715
|
+
"answerOptions": [
|
716
|
+
{
|
717
|
+
"describe": "In a Master-Detail relationship, when a record of a master object is deleted, the detail records are not deleted.",
|
718
|
+
"isRight": false
|
719
|
+
},
|
720
|
+
{
|
721
|
+
"describe": "A Master-Detail relationship detail record inherits the sharing and security of its master record.",
|
722
|
+
"isRight": true
|
723
|
+
},
|
724
|
+
{
|
725
|
+
"describe": "In a Lookup relationship, the field value is mandatory.",
|
726
|
+
"isRight": false
|
727
|
+
},
|
728
|
+
{
|
729
|
+
"describe": "In a Lookup relationship when the parent record is deleted, the child records are always deleted.",
|
730
|
+
"isRight": false
|
731
|
+
}
|
732
|
+
],
|
733
|
+
"hashCode": "1988673204"
|
734
|
+
},
|
735
|
+
{
|
736
|
+
"describe": "Which two statements accurately represent the MVC framework implementation in Salesforce?Choose 2 answers",
|
737
|
+
"answerOptions": [
|
738
|
+
{
|
739
|
+
"describe": "Standard and Custom objects used in the app schema represent the View (V) part of the MVC framework.",
|
740
|
+
"isRight": false
|
741
|
+
},
|
742
|
+
{
|
743
|
+
"describe": "Lightning component HTML files represent the Model (M) part of the MVC framework.",
|
744
|
+
"isRight": false
|
745
|
+
},
|
746
|
+
{
|
747
|
+
"describe": "Tigger used to create records represent the Model (M) part of the MVC framework.",
|
748
|
+
"isRight": true
|
749
|
+
},
|
750
|
+
{
|
751
|
+
"describe": "Validation rules enforce business rules and represent the Controller (C) part of the MVC framework.",
|
752
|
+
"isRight": true
|
753
|
+
}
|
754
|
+
],
|
755
|
+
"hashCode": "1988673201"
|
756
|
+
},
|
757
|
+
{
|
758
|
+
"describe": "What is a benefit of developing applications in a multi-tenant environment?",
|
759
|
+
"answerOptions": [
|
760
|
+
{
|
761
|
+
"describe": "Default out-of-the-box configuration",
|
762
|
+
"isRight": true
|
763
|
+
},
|
764
|
+
{
|
765
|
+
"describe": "Access to predefined computing resources",
|
766
|
+
"isRight": false
|
767
|
+
},
|
768
|
+
{
|
769
|
+
"describe": "Unlimited processing power and memory",
|
770
|
+
"isRight": false
|
771
|
+
},
|
772
|
+
{
|
773
|
+
"describe": "Enforced best practices for development",
|
774
|
+
"isRight": false
|
775
|
+
}
|
776
|
+
],
|
777
|
+
"hashCode": "1988673199"
|
778
|
+
},
|
779
|
+
{
|
780
|
+
"describe": "A SSN__c custom field exists on the Candidate __c custom object. The field is used to store each candidate's social security number and is marked as Unique in the schema definition.\n\nAs part of a data enrichment process, Universal Containers has a CSV file that contains updated data for all candidates in the system. The file contains each Candidate's social security number as a data point. Universal Containers wants to upload this information into Salesforce, while ensuring all data rows are correctly mapped to a candidate in the system. Which technique should the developer implement to streamline the data upload?",
|
781
|
+
"answerOptions": [
|
782
|
+
{
|
783
|
+
"describe": "Upload the CSV into a custom object related to Candidate__c. ",
|
784
|
+
"isRight": false
|
785
|
+
},
|
786
|
+
{
|
787
|
+
"describe": "Update the SSN__c field definition to mark it as an External Id.",
|
788
|
+
"isRight": true
|
789
|
+
},
|
790
|
+
{
|
791
|
+
"describe": "Create a before insert trigger to correctly map the records. ",
|
792
|
+
"isRight": false
|
793
|
+
},
|
794
|
+
{
|
795
|
+
"describe": "Create a process Builder on the Candidate__c object to map the records.",
|
796
|
+
"isRight": false
|
797
|
+
}
|
798
|
+
],
|
799
|
+
"hashCode": "1988673197"
|
800
|
+
},
|
801
|
+
{
|
802
|
+
"describe": "Which three operations affect the number of times a trigger can fire? Choose 3 answers",
|
803
|
+
"answerOptions": [
|
804
|
+
{
|
805
|
+
"describe": "Email messages",
|
806
|
+
"isRight": false
|
807
|
+
},
|
808
|
+
{
|
809
|
+
"describe": "Roll-Up Summary fields",
|
810
|
+
"isRight": true
|
811
|
+
},
|
812
|
+
{
|
813
|
+
"describe": "Workflow Rules",
|
814
|
+
"isRight": true
|
815
|
+
},
|
816
|
+
{
|
817
|
+
"describe": "Criteria-based Sharing calculations",
|
818
|
+
"isRight": false
|
819
|
+
},
|
820
|
+
{
|
821
|
+
"describe": "Lightning Flows",
|
822
|
+
"isRight": true
|
823
|
+
}
|
824
|
+
],
|
825
|
+
"hashCode": "1988673166"
|
826
|
+
},
|
827
|
+
{
|
828
|
+
"describe": "When a user edits the Postal Code on an Account, a custom Account text field named \"TimeZone\" must be updated based on the values in a PostalCodeToTimeZone__c custom object.\nHow should a developer implement this feature?",
|
829
|
+
"answerOptions": [
|
830
|
+
{
|
831
|
+
"describe": "Build an Account custom trigger",
|
832
|
+
"isRight": true
|
833
|
+
},
|
834
|
+
{
|
835
|
+
"describe": "Build an Account Workflow Rule",
|
836
|
+
"isRight": false
|
837
|
+
},
|
838
|
+
{
|
839
|
+
"describe": "Build an Account Assignment Rule",
|
840
|
+
"isRight": false
|
841
|
+
},
|
842
|
+
{
|
843
|
+
"describe": "Build an Account Approval Process.",
|
844
|
+
"isRight": false
|
845
|
+
}
|
846
|
+
],
|
847
|
+
"hashCode": "1988673165"
|
848
|
+
},
|
849
|
+
{
|
850
|
+
"describe": "A developer wants to import 500 Opportunity records into a sandbox.\nWhy should the developer choose to use Data Loader instead of Data Import Wizard?",
|
851
|
+
"answerOptions": [
|
852
|
+
{
|
853
|
+
"describe": "Data Import Wizard does not support Opportunities.",
|
854
|
+
"isRight": true
|
855
|
+
},
|
856
|
+
{
|
857
|
+
"describe": "Data Import Wizard can not import all 500 records.",
|
858
|
+
"isRight": false
|
859
|
+
},
|
860
|
+
{
|
861
|
+
"describe": "Data Loader runs from the developer's browser.",
|
862
|
+
"isRight": false
|
863
|
+
},
|
864
|
+
{
|
865
|
+
"describe": "Data Loader automatically relates Opportunities to Accounts.",
|
866
|
+
"isRight": false
|
867
|
+
}
|
868
|
+
],
|
869
|
+
"hashCode": "1988673138"
|
870
|
+
},
|
871
|
+
{
|
872
|
+
"describe": "Universal Containers has an order system that uses an Order Number to indentify an order for customers and service agents. Order records will be imported into Salesforce. \nHow should the Order Number field be defined in Salesforce?",
|
873
|
+
"answerOptions": [
|
874
|
+
{
|
875
|
+
"describe": "Indirect Lookup",
|
876
|
+
"isRight": false
|
877
|
+
},
|
878
|
+
{
|
879
|
+
"describe": "Lookup",
|
880
|
+
"isRight": false
|
881
|
+
},
|
882
|
+
{
|
883
|
+
"describe": "Number with External ID",
|
884
|
+
"isRight": true
|
885
|
+
},
|
886
|
+
{
|
887
|
+
"describe": "Direct Lookup",
|
888
|
+
"isRight": false
|
889
|
+
}
|
890
|
+
],
|
891
|
+
"hashCode": "1988673111"
|
892
|
+
},
|
893
|
+
{
|
894
|
+
"describe": "UC uses a custom object called Vendor. The Vendor custom object has a Master-Detail relationship with the standard Account object.\nBased on some internal discussions, the UC administrator tried to change the Master-Detail relationship to a Lookup relationship but was not able to do so.\n\nWhat is possible reason that this change was not permitted?",
|
895
|
+
"answerOptions": [
|
896
|
+
{
|
897
|
+
"describe": "The Vendor object must use a Master-Detail field for reporting.",
|
898
|
+
"isRight": false
|
899
|
+
},
|
900
|
+
{
|
901
|
+
"describe": "The Account object is included on a workflow on the Vendor object.",
|
902
|
+
"isRight": false
|
903
|
+
},
|
904
|
+
{
|
905
|
+
"describe": "The Account records contain Vendor roll-up summary fields.",
|
906
|
+
"isRight": true
|
907
|
+
},
|
908
|
+
{
|
909
|
+
"describe": "The Vendor records has existing values in the Account object.",
|
910
|
+
"isRight": false
|
911
|
+
}
|
912
|
+
],
|
913
|
+
"hashCode": "1988673105"
|
914
|
+
},
|
915
|
+
{
|
916
|
+
"describe": "An org has an existing Flow that creates an Opportunity with an Update Records element. A developer must update the Visual Flow to also create a Contact and store the created Contact's ID on the Opportunity.\nWhich update should the developer make in the Visual Flow?",
|
917
|
+
"answerOptions": [
|
918
|
+
{
|
919
|
+
"describe": "Add a new Get Records element.",
|
920
|
+
"isRight": false
|
921
|
+
},
|
922
|
+
{
|
923
|
+
"describe": "Add a new Update Records element.",
|
924
|
+
"isRight": false
|
925
|
+
},
|
926
|
+
{
|
927
|
+
"describe": "Add a new Create Records element.",
|
928
|
+
"isRight": true
|
929
|
+
},
|
930
|
+
{
|
931
|
+
"describe": "Add a new Quick Action(of type Create) element.",
|
932
|
+
"isRight": false
|
933
|
+
}
|
934
|
+
],
|
935
|
+
"hashCode": "1988673103"
|
936
|
+
},
|
937
|
+
{
|
938
|
+
"describe": "A custom picklist field Food_Preference__c, exists an a custom object. The picklist contains the following options:\n'Vegan'. 'Kosher', 'No Preference'. The developer must ensure a value is populated every time a record is created or updated.",
|
939
|
+
"answerOptions": [
|
940
|
+
{
|
941
|
+
"describe": "Mark the field as Required on the object's page Layout.",
|
942
|
+
"isRight": false
|
943
|
+
},
|
944
|
+
{
|
945
|
+
"describe": "Mark the field as Required on the field definition.",
|
946
|
+
"isRight": true
|
947
|
+
},
|
948
|
+
{
|
949
|
+
"describe": "Set \"Use the first value in the list as default value\" as True.",
|
950
|
+
"isRight": false
|
951
|
+
},
|
952
|
+
{
|
953
|
+
"describe": "Set a validation rule to enforce a value is selected.",
|
954
|
+
"isRight": false
|
955
|
+
}
|
956
|
+
],
|
957
|
+
"hashCode": "1988673081"
|
958
|
+
},
|
959
|
+
{
|
960
|
+
"describe": "Universal Containers decides to use exclusively declarative development to build out a new Salesforce application.\nWhich three options should be used to build out the database layer for the application? Choose 3 answers",
|
961
|
+
"answerOptions": [
|
962
|
+
{
|
963
|
+
"describe": "Relationships",
|
964
|
+
"isRight": true
|
965
|
+
},
|
966
|
+
{
|
967
|
+
"describe": "Flows",
|
968
|
+
"isRight": false
|
969
|
+
},
|
970
|
+
{
|
971
|
+
"describe": "Triggers",
|
972
|
+
"isRight": false
|
973
|
+
},
|
974
|
+
{
|
975
|
+
"describe": "Custom Objects and Fields",
|
976
|
+
"isRight": true
|
977
|
+
},
|
978
|
+
{
|
979
|
+
"describe": "Roll-up Summaries",
|
980
|
+
"isRight": true
|
981
|
+
}
|
982
|
+
],
|
983
|
+
"hashCode": "1988673079"
|
984
|
+
},
|
985
|
+
{
|
986
|
+
"describe": "An org tracks customer orders on an Order object and the line items of an Order on the Line Item object. The Line Item object has a \nMaster/Detail relationship to the Order object. A developer has requirement to calculate the order amount on an Order and the line amount \non each Line Item based on quantity and price.\nWhat is the correct implementation?",
|
987
|
+
"answerOptions": [
|
988
|
+
{
|
989
|
+
"describe": "Write a process an the Line Item that calculated the item amount and order amount and updates the fields on the Line Item and the Order.",
|
990
|
+
"isRight": false
|
991
|
+
},
|
992
|
+
{
|
993
|
+
"describe": "Implement the line amount as a numeric formula field and the order amount as a roll-up summary field.",
|
994
|
+
"isRight": true
|
995
|
+
},
|
996
|
+
{
|
997
|
+
"describe": "Implement the line amount as a currency field and the order amount as SUM formula field.",
|
998
|
+
"isRight": false
|
999
|
+
},
|
1000
|
+
{
|
1001
|
+
"describe": "Write a single before trigger on the Line Item that calculates the item amount and updates the order amount on the Order.",
|
1002
|
+
"isRight": false
|
1003
|
+
}
|
1004
|
+
],
|
1005
|
+
"hashCode": "1988673045"
|
1006
|
+
},
|
1007
|
+
{
|
1008
|
+
"describe": "A developer needs to implement the functionality for a service agent to gather multiple pieces of imformation from a customer in order to \nsend a replacement credit card.\nWhich automation tool meets these requirements?",
|
1009
|
+
"answerOptions": [
|
1010
|
+
{
|
1011
|
+
"describe": "Lightning Component",
|
1012
|
+
"isRight": false
|
1013
|
+
},
|
1014
|
+
{
|
1015
|
+
"describe": "Flow Builder",
|
1016
|
+
"isRight": true
|
1017
|
+
},
|
1018
|
+
{
|
1019
|
+
"describe": "Process Builder",
|
1020
|
+
"isRight": false
|
1021
|
+
},
|
1022
|
+
{
|
1023
|
+
"describe": "Approval Process",
|
1024
|
+
"isRight": false
|
1025
|
+
}
|
1026
|
+
],
|
1027
|
+
"hashCode": "1988673043"
|
1028
|
+
},
|
1029
|
+
{
|
1030
|
+
"describe": "Universal Containers used a simple Order Management app. On the Order Lines, the order line total is calculated by multiplying the item price \nwith the quantity ordered. There is a Master-Detail relationship between the Order and the Order Lines object.\nWhat is the best practice to get the sum of all order line totals on the order header?",
|
1031
|
+
"answerOptions": [
|
1032
|
+
{
|
1033
|
+
"describe": "Apex Trigger",
|
1034
|
+
"isRight": false
|
1035
|
+
},
|
1036
|
+
{
|
1037
|
+
"describe": "Declarative Roll-Up Summary App",
|
1038
|
+
"isRight": false
|
1039
|
+
},
|
1040
|
+
{
|
1041
|
+
"describe": "Process Builder",
|
1042
|
+
"isRight": false
|
1043
|
+
},
|
1044
|
+
{
|
1045
|
+
"describe": "Roll-Up Summary Field",
|
1046
|
+
"isRight": true
|
1047
|
+
}
|
1048
|
+
],
|
1049
|
+
"hashCode": "1988673042"
|
1050
|
+
},
|
1051
|
+
{
|
1052
|
+
"describe": "Which aspect of Apex programming is limited due to multitenancy?",
|
1053
|
+
"answerOptions": [
|
1054
|
+
{
|
1055
|
+
"describe": "The number of methods in an Apex class",
|
1056
|
+
"isRight": false
|
1057
|
+
},
|
1058
|
+
{
|
1059
|
+
"describe": "The number of records returned from database queries",
|
1060
|
+
"isRight": true
|
1061
|
+
},
|
1062
|
+
{
|
1063
|
+
"describe": "The number of active Apex classes",
|
1064
|
+
"isRight": false
|
1065
|
+
},
|
1066
|
+
{
|
1067
|
+
"describe": "The number of records processed in a loop.",
|
1068
|
+
"isRight": false
|
1069
|
+
}
|
1070
|
+
],
|
1071
|
+
"hashCode": "1988673041"
|
1072
|
+
},
|
1073
|
+
{
|
1074
|
+
"describe": "Universal Containers stores Orders and Line Items in Salesforce. For security reasons, financial representatives are allowed to see information\non the Order such as order amount, but they are not allowed to see the Line Item on the Order.\nWhich type of relationship should be user?",
|
1075
|
+
"answerOptions": [
|
1076
|
+
{
|
1077
|
+
"describe": "Indirect Lookup",
|
1078
|
+
"isRight": false
|
1079
|
+
},
|
1080
|
+
{
|
1081
|
+
"describe": "Lookup",
|
1082
|
+
"isRight": true
|
1083
|
+
},
|
1084
|
+
{
|
1085
|
+
"describe": "Master-Detail",
|
1086
|
+
"isRight": false
|
1087
|
+
},
|
1088
|
+
{
|
1089
|
+
"describe": "Direct Lookup",
|
1090
|
+
"isRight": false
|
1091
|
+
}
|
1092
|
+
],
|
1093
|
+
"hashCode": "1988672368"
|
1094
|
+
},
|
1095
|
+
{
|
1096
|
+
"describe": "In terms of the MVC paradigm, what are two advantages of implementing the view layer of a Salesforce application using Aura Component-based \ndevelopment over Visualforce?Choose 2 answers",
|
1097
|
+
"answerOptions": [
|
1098
|
+
{
|
1099
|
+
"describe": "Server-side run-time debugging",
|
1100
|
+
"isRight": false
|
1101
|
+
},
|
1102
|
+
{
|
1103
|
+
"describe": "Self-contained and reusable units of an application",
|
1104
|
+
"isRight": true
|
1105
|
+
},
|
1106
|
+
{
|
1107
|
+
"describe": "Automatic code generation",
|
1108
|
+
"isRight": false
|
1109
|
+
},
|
1110
|
+
{
|
1111
|
+
"describe": "Rich component ecosystem",
|
1112
|
+
"isRight": true
|
1113
|
+
}
|
1114
|
+
],
|
1115
|
+
"hashCode": "1988672367"
|
1116
|
+
},
|
1117
|
+
{
|
1118
|
+
"describe": "Universal Containers wants to back up all of the data and attachments in Salesforce org once a month.\nWhich approach should a developer use to meet this requirement?",
|
1119
|
+
"answerOptions": [
|
1120
|
+
{
|
1121
|
+
"describe": "Schedule a report",
|
1122
|
+
"isRight": false
|
1123
|
+
},
|
1124
|
+
{
|
1125
|
+
"describe": "Create a Schedulable Apex Class",
|
1126
|
+
"isRight": false
|
1127
|
+
},
|
1128
|
+
{
|
1129
|
+
"describe": "Define a Data Export scheduled job.",
|
1130
|
+
"isRight": true
|
1131
|
+
},
|
1132
|
+
{
|
1133
|
+
"describe": "Use the data loader command line.",
|
1134
|
+
"isRight": false
|
1135
|
+
}
|
1136
|
+
],
|
1137
|
+
"hashCode": "1988672365"
|
1138
|
+
},
|
1139
|
+
{
|
1140
|
+
"describe": "A developer must build an application that tracks which Accounts have purchaesd specific pieces of equipment that are represented as \nProducts Each Account could purchse many pieces of equipment.\nHow should the developer track that an Account has purchased a piece of equipment?",
|
1141
|
+
"answerOptions": [
|
1142
|
+
{
|
1143
|
+
"describe": "Use a Lookup on Account to Product",
|
1144
|
+
"isRight": false
|
1145
|
+
},
|
1146
|
+
{
|
1147
|
+
"describe": "Use the Asset object",
|
1148
|
+
"isRight": true
|
1149
|
+
},
|
1150
|
+
{
|
1151
|
+
"describe": "Use a Master-Detail on Product to Account",
|
1152
|
+
"isRight": false
|
1153
|
+
},
|
1154
|
+
{
|
1155
|
+
"describe": "Use a Custom object",
|
1156
|
+
"isRight": false
|
1157
|
+
}
|
1158
|
+
],
|
1159
|
+
"hashCode": "1988672337"
|
1160
|
+
},
|
1161
|
+
{
|
1162
|
+
"describe": "UC wants to lower its shipping cost while making the shipping process more efficient. The Distribution Officer advises UC to implement global addresses to allow multiple Accounts to share a default pickup address. The developer is tasked to create the supporting object and relationship for this business requirement and uses the Setup Menu to create a custom object called \"Global Address\".\n\nWhich field should the developer add to create the most efficient model that supports the business need?",
|
1163
|
+
"answerOptions": [
|
1164
|
+
{
|
1165
|
+
"describe": "Add a Master-Detail field on the Global Address object to the Account object.",
|
1166
|
+
"isRight": false
|
1167
|
+
},
|
1168
|
+
{
|
1169
|
+
"describe": "Add a Lookup field on the Account object to the Global Address object.",
|
1170
|
+
"isRight": true
|
1171
|
+
},
|
1172
|
+
{
|
1173
|
+
"describe": "Add a Master-Detail field on the Account object to the Global Address object.",
|
1174
|
+
"isRight": false
|
1175
|
+
},
|
1176
|
+
{
|
1177
|
+
"describe": "Add a Lookup field on the Global Address object to the Account object.",
|
1178
|
+
"isRight": false
|
1179
|
+
}
|
1180
|
+
],
|
1181
|
+
"hashCode": "1988672335"
|
1182
|
+
},
|
1183
|
+
{
|
1184
|
+
"describe": "A developer has a requirement to create an Order when an Opportunity reaches a 'Closed-Won' status.\nWhich tool should be used to implement this requirement?",
|
1185
|
+
"answerOptions": [
|
1186
|
+
{
|
1187
|
+
"describe": "Lightning Flow",
|
1188
|
+
"isRight": false
|
1189
|
+
},
|
1190
|
+
{
|
1191
|
+
"describe": "Process Builder",
|
1192
|
+
"isRight": true
|
1193
|
+
},
|
1194
|
+
{
|
1195
|
+
"describe": "Apex Trigger",
|
1196
|
+
"isRight": false
|
1197
|
+
},
|
1198
|
+
{
|
1199
|
+
"describe": "Lightning Component",
|
1200
|
+
"isRight": false
|
1201
|
+
}
|
1202
|
+
],
|
1203
|
+
"hashCode": "1988672361"
|
1204
|
+
},
|
1205
|
+
{
|
1206
|
+
"describe": "A Licensed_Professional __c custom object exists in the system with two Master-Detail fields for the following objects: Certification__c and Contact.\n\nUsers with the \"Certification Representative\" role can access the Certification records they own and view the related Licensed Professionals records, however users with the \"Sales Representative\" role report they cannot view any Licensed Professional records even though they own the associated Contact record.\n\nWhat are two likely causes of users in the \"Sales Representative\" role not being able to access the Licensed Professional records?Choose 2 answers",
|
1207
|
+
"answerOptions": [
|
1208
|
+
{
|
1209
|
+
"describe": "The organization has a private sharing model for Certification__c, and Contact is the primary relationship in the Licensed_Professinal__c object.",
|
1210
|
+
"isRight": false
|
1211
|
+
},
|
1212
|
+
{
|
1213
|
+
"describe": "The organization has a private sharing model for Certification__c, and Certification__c is the primary relationship in the Licensed_Professinal__c object. ",
|
1214
|
+
"isRight": true
|
1215
|
+
},
|
1216
|
+
{
|
1217
|
+
"describe": "The organization recently modified the Sales Representative role to restrict Read/Write access to Licensed_Professinal__c. ",
|
1218
|
+
"isRight": false
|
1219
|
+
},
|
1220
|
+
{
|
1221
|
+
"describe": "The organization recently modified the Sales Representative role to restrict Read access to Licensed_Professinal__c. ",
|
1222
|
+
"isRight": true
|
1223
|
+
}
|
1224
|
+
],
|
1225
|
+
"hashCode": "1988672332"
|
1226
|
+
},
|
1227
|
+
{
|
1228
|
+
"describe": "Which three process automations can immediately send an email notification to the owner of an Opportunity \nwhen its Amount is changed to be greater than $10.000? Choose 3 answers",
|
1229
|
+
"answerOptions": [
|
1230
|
+
{
|
1231
|
+
"describe": "Escalation Rule",
|
1232
|
+
"isRight": false
|
1233
|
+
},
|
1234
|
+
{
|
1235
|
+
"describe": "Workflow Rule",
|
1236
|
+
"isRight": true
|
1237
|
+
},
|
1238
|
+
{
|
1239
|
+
"describe": "Process Builder",
|
1240
|
+
"isRight": true
|
1241
|
+
},
|
1242
|
+
{
|
1243
|
+
"describe": "Flow Builder",
|
1244
|
+
"isRight": true
|
1245
|
+
},
|
1246
|
+
{
|
1247
|
+
"describe": "Approval Process",
|
1248
|
+
"isRight": false
|
1249
|
+
}
|
1250
|
+
],
|
1251
|
+
"hashCode": "1988672330"
|
1252
|
+
},
|
1253
|
+
{
|
1254
|
+
"describe": "Which process automation should be used to send an outbound message without using Apex code?",
|
1255
|
+
"answerOptions": [
|
1256
|
+
{
|
1257
|
+
"describe": "Flow Builder",
|
1258
|
+
"isRight": false
|
1259
|
+
},
|
1260
|
+
{
|
1261
|
+
"describe": "Process Builder",
|
1262
|
+
"isRight": false
|
1263
|
+
},
|
1264
|
+
{
|
1265
|
+
"describe": "Approval Process",
|
1266
|
+
"isRight": false
|
1267
|
+
},
|
1268
|
+
{
|
1269
|
+
"describe": "Workflow Rule",
|
1270
|
+
"isRight": true
|
1271
|
+
}
|
1272
|
+
],
|
1273
|
+
"hashCode": "1988672329"
|
1274
|
+
},
|
1275
|
+
{
|
1276
|
+
"describe": "A developer at Universal Containers is tasked with implementing a new Salesforce application that must built by their company's Salesforce administrator.\nWhich three options should be considered for building out the business logic layer of the application? Choose 3 answers",
|
1277
|
+
"answerOptions": [
|
1278
|
+
{
|
1279
|
+
"describe": "Scheduled Jobs",
|
1280
|
+
"isRight": false
|
1281
|
+
},
|
1282
|
+
{
|
1283
|
+
"describe": "Validation Rules",
|
1284
|
+
"isRight": true
|
1285
|
+
},
|
1286
|
+
{
|
1287
|
+
"describe": "Invocable Actions",
|
1288
|
+
"isRight": false
|
1289
|
+
},
|
1290
|
+
{
|
1291
|
+
"describe": "Workflows",
|
1292
|
+
"isRight": true
|
1293
|
+
},
|
1294
|
+
{
|
1295
|
+
"describe": "Process Builder",
|
1296
|
+
"isRight": true
|
1297
|
+
}
|
1298
|
+
],
|
1299
|
+
"hashCode": "1988672328"
|
1300
|
+
},
|
1301
|
+
{
|
1302
|
+
"describe": "A developer has the following requirements:\n1. Calculate the total amount on an Order.\n2. Calculate the line amount for each Line Item based on quantity selected and price.\n3. Move Line Items to a different Order if a Line Item is not in stock.\nWhich relationship implementation supports these requirements?",
|
1303
|
+
"answerOptions": [
|
1304
|
+
{
|
1305
|
+
"describe": "Line Item has a Master-Detail field to Order and the Master can be re-parented.",
|
1306
|
+
"isRight": true
|
1307
|
+
},
|
1308
|
+
{
|
1309
|
+
"describe": "Order has a Lookup field to Line Item and there can be many Line Item per Order.",
|
1310
|
+
"isRight": false
|
1311
|
+
},
|
1312
|
+
{
|
1313
|
+
"describe": "Line Item has a Lookup field to Order and there can be many Line Item per Order.",
|
1314
|
+
"isRight": false
|
1315
|
+
},
|
1316
|
+
{
|
1317
|
+
"describe": "Order has a Master-Detail field to Line Item and there can be many Line Item per Order.",
|
1318
|
+
"isRight": false
|
1319
|
+
}
|
1320
|
+
],
|
1321
|
+
"hashCode": "1988672306"
|
1322
|
+
},
|
1323
|
+
{
|
1324
|
+
"describe": "UC uses a custom object called Vendor. The Vendor custom object has a Master-Detail relationship with the standard Account object.\nBased on some internal discussions, the UC administrator tried to change the Master-Detail relationship to a Lookup relationship but was not able to do so.\nWhat is possible reason that this change was not permitted?",
|
1325
|
+
"answerOptions": [
|
1326
|
+
{
|
1327
|
+
"describe": "The Vendor object must use a Master-Detail field for reporting.",
|
1328
|
+
"isRight": false
|
1329
|
+
},
|
1330
|
+
{
|
1331
|
+
"describe": "The Account object is included on a workflow on the Vendor object.",
|
1332
|
+
"isRight": false
|
1333
|
+
},
|
1334
|
+
{
|
1335
|
+
"describe": "The Account records contain Vendor roll-up summary fields.",
|
1336
|
+
"isRight": true
|
1337
|
+
},
|
1338
|
+
{
|
1339
|
+
"describe": "The Vendor records has existing values in the Account object.",
|
1340
|
+
"isRight": false
|
1341
|
+
}
|
1342
|
+
],
|
1343
|
+
"hashCode": "1988672274"
|
1344
|
+
}
|
1345
|
+
],
|
1346
|
+
"hashCode": "-123844663"
|
1347
|
+
}
|