@palerock/exam-qa 1.0.6-patch2 → 1.0.6-patch20
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.4293d3540537974d843eca825dcda382.css +2 -0
- package/dist/static/css/app.4293d3540537974d843eca825dcda382.css.map +1 -0
- package/dist/static/js/app.e278f9557d317b4606b0.js +2 -0
- package/dist/static/js/app.e278f9557d317b4606b0.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 +1407 -0
- package/lib-json/Dev1/346/250/241/346/213/237/345/215/267A.json +1538 -0
- package/lib-json/Dev1/346/250/241/346/213/237/345/215/267B.json +1534 -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 +1587 -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 +1042 -0
- package/lib-json/Dev1/346/265/213/350/257/225_/350/260/203/350/257/225_/351/203/250/347/275/262.json +928 -0
- package/lib-json/Dev1/347/224/250/346/210/267/347/225/214/351/235/242.json +1243 -0
- package/lib-json/[DEV2]Salesforce/345/237/272/347/241/200.json +375 -0
- package/lib-json/[DEV2]/346/200/247/350/203/275.json +728 -0
- package/lib-json/[DEV2]/346/250/241/346/213/237/345/215/267A.json +1403 -0
- package/lib-json/[DEV2]/346/250/241/346/213/237/345/215/267B.json +1387 -0
- package/lib-json/[DEV2]/346/265/213/350/257/225/344/270/216/351/203/250/347/275/262.json +828 -0
- package/lib-json/[DEV2]/347/224/250/346/210/267/347/225/214/351/235/2421.json +977 -0
- package/lib-json/[DEV2]/347/224/250/346/210/267/347/225/214/351/235/2422.json +667 -0
- package/lib-json/[DEV2]/351/200/273/350/276/221/343/200/201/346/265/201/347/250/213/350/207/252/345/212/250/345/214/226/345/222/214/351/233/206/346/210/2201.json +1387 -0
- package/lib-json/[DEV2]/351/200/273/350/276/221/343/200/201/346/265/201/347/250/213/350/207/252/345/212/250/345/214/226/345/222/214/351/233/206/346/210/2202.json +260 -0
- package/lib-json/[JS]/347/254/254/344/270/200/347/253/240 /345/217/230/351/207/217-/347/261/273/345/236/213-/351/233/206/345/220/210.json" +1048 -0
- package/lib-json/[JS]/347/254/254/344/270/203/347/253/240 /346/265/213/350/257/225.json" +356 -0
- package/lib-json/[JS]/347/254/254/344/270/211/347/253/240 /346/265/217/350/247/210/345/231/250/345/222/214/344/272/213/344/273/266.json" +851 -0
- package/lib-json/[JS]/347/254/254/344/272/214/347/253/240 /345/257/271/350/261/241-/345/207/275/346/225/260-/347/261/273.json" +1787 -0
- package/lib-json/[JS]/347/254/254/344/272/224/347/253/240 /345/274/202/346/255/245/347/274/226/347/250/213.json" +547 -0
- package/lib-json/[JS]/347/254/254/345/205/255/347/253/240 /346/234/215/345/212/241/345/231/250/347/253/257JavaScript.json" +613 -0
- package/lib-json/[JS]/347/254/254/345/233/233/347/253/240 /350/260/203/350/257/225/345/222/214/351/224/231/350/257/257/345/244/204/347/220/206.json" +525 -0
- package/lib-json/[/345/222/270/351/261/274]AppBuilder-1.json +977 -0
- package/lib-json/[/345/222/270/351/261/274]AppBuilder-2.json +941 -0
- package/lib-json/[/345/222/270/351/261/274]AppBuilder-3.json +973 -0
- package/lib-json/[/345/222/270/351/261/274]AppBuilder-4.json +981 -0
- package/lib-json/[/345/222/270/351/261/274]AppBuilder-5.json +771 -0
- package/lib-json/map.json +28 -43
- package/package.json +4 -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
- package/lib-json/Salesforce-Admin(302)-[Set-10].json +0 -321
- package/lib-json/Salesforce-Admin(302)-[Set-1].json +0 -301
- package/lib-json/Salesforce-Admin(302)-[Set-2].json +0 -325
- package/lib-json/Salesforce-Admin(302)-[Set-3].json +0 -305
- package/lib-json/Salesforce-Admin(302)-[Set-4].json +0 -325
- package/lib-json/Salesforce-Admin(302)-[Set-5].json +0 -329
- package/lib-json/Salesforce-Admin(302)-[Set-6].json +0 -322
- package/lib-json/Salesforce-Admin(302)-[Set-7].json +0 -321
- package/lib-json/Salesforce-Admin(302)-[Set-8].json +0 -321
- package/lib-json/Salesforce-Admin(302)-[Set-9].json +0 -325
- package/lib-json/Salesforce-Admin-201-[Set-10].json +0 -158
- package/lib-json/Salesforce-Admin-201-[Set-1].json +0 -604
- package/lib-json/Salesforce-Admin-201-[Set-2].json +0 -621
- package/lib-json/Salesforce-Admin-201-[Set-3].json +0 -650
- package/lib-json/Salesforce-Admin-201-[Set-4].json +0 -636
- package/lib-json/Salesforce-Admin-201-[Set-5].json +0 -640
- package/lib-json/Salesforce-Admin-201-[Set-6].json +0 -126
- package/lib-json/Salesforce-Admin-201-[Set-7].json +0 -126
- package/lib-json/Salesforce-Admin-201-[Set-8].json +0 -126
- package/lib-json/Salesforce-Admin-201-[Set-9].json +0 -126
- package/lib-json/Salesforce-Certified-Platform-Developer-1-[Set-1].json +0 -321
- package/lib-json/Salesforce-Certified-Platform-Developer-1-[Set-2].json +0 -325
- package/lib-json/Salesforce-Certified-Platform-Developer-1-[Set-3].json +0 -321
- package/lib-json/Salesforce-Certified-Platform-Developer-1-[Set-4].json +0 -337
- package/lib-json/Salesforce-Certified-Platform-Developer-1-[Set-5].json +0 -329
- package/lib-json/Salesforce-Certified-Platform-Developer-1-[Set-6].json +0 -325
- package/lib-json/Salesforce-Certified-Platform-Developer-1-[Set-7].json +0 -480
- package/lib-json/Salesforce-Sales-Cloud-Certification(81)-[Set-1].json +0 -305
- package/lib-json/Salesforce-Sales-Cloud-Certification(81)-[Set-2].json +0 -297
- package/lib-json/Salesforce-Sales-Cloud-Certification(81)-[Set-3].json +0 -269
- package/lib-json/Salesforce-Sales-Cloud-Certification(81)-[Set-4].json +0 -309
- package/lib-json/Salesforce-Sales-Cloud-Certification(81)-[Set-5].json +0 -515
- package/lib-json/app-builder-01.json +0 -1
- package/lib-json/app-builder-02.json +0 -1
- package/lib-json/app-builder-03.json +0 -1
- package/lib-json/app-builder-04.json +0 -1
- package/lib-json/app-builder-05.json +0 -1
- package/lib-json/app-builder-06.json +0 -1
- package/lib-json/app-builder-07.json +0 -1
- package/lib-json/app-builder-08.json +0 -1
- package/lib-json/app-builder-09.json +0 -1
- package/lib-json/app-builder-10.json +0 -1
- package/lib-json/app-builder-11.json +0 -311
@@ -0,0 +1,771 @@
|
|
1
|
+
{
|
2
|
+
"title": "[咸鱼]AppBuilder-5",
|
3
|
+
"category": "[咸鱼]AppBuilder",
|
4
|
+
"questions": [
|
5
|
+
{
|
6
|
+
"describe": "Ursa Major Solar is ramping up the sales team to meet increased demand. As part of the short ramp up for these new reps, the manager wants to provide a help guide to enable reps to easily get help where needed during the different sales processes.\nWhich solution should an app builder recommend?",
|
7
|
+
"answerOptions": [
|
8
|
+
{
|
9
|
+
"describe": "Flow",
|
10
|
+
"isRight": false
|
11
|
+
},
|
12
|
+
{
|
13
|
+
"describe": "Journey Builder",
|
14
|
+
"isRight": false
|
15
|
+
},
|
16
|
+
{
|
17
|
+
"describe": "Chatter Publisher",
|
18
|
+
"isRight": false
|
19
|
+
},
|
20
|
+
{
|
21
|
+
"describe": "Path",
|
22
|
+
"isRight": true
|
23
|
+
}
|
24
|
+
],
|
25
|
+
"hashCode": 150280054
|
26
|
+
},
|
27
|
+
{
|
28
|
+
"describe": "The DreamHouse Realty (DR) service manager has asked for some improvements in case management to enforce process compliance so that cases are unable to be reverted to an earlier\n4\ncase status, and to ensure that certain fields are required when specific case criteria are met. What solution should an app builder implement to meet these requirements?\nA Workflow Rules\nB Process Builder\nC",
|
29
|
+
"answerOptions": [
|
30
|
+
{
|
31
|
+
"describe": "Validation Rules\nD Activities Component",
|
32
|
+
"isRight": false
|
33
|
+
}
|
34
|
+
],
|
35
|
+
"hashCode": -1209833042
|
36
|
+
},
|
37
|
+
{
|
38
|
+
"describe": "DreamHouse Realty is rethinking its sandbox utilization strategy after acquiring Cloud Kicks. The Salesforce COE already utilizes a partial and a full sandbox, which it refreshes on their own regular schedules. Teams are expanding and have to begin each of their small projects in a sandbox before committing to the larger pool for collaborative testing while still keeping costs down.\nWhat type of sandbox should each team member use?",
|
39
|
+
"answerOptions": [
|
40
|
+
{
|
41
|
+
"describe": "Full sandbox",
|
42
|
+
"isRight": false
|
43
|
+
},
|
44
|
+
{
|
45
|
+
"describe": "Developer sandbox",
|
46
|
+
"isRight": true
|
47
|
+
},
|
48
|
+
{
|
49
|
+
"describe": "Developer pro sandbox",
|
50
|
+
"isRight": false
|
51
|
+
},
|
52
|
+
{
|
53
|
+
"describe": "Partial sandbox",
|
54
|
+
"isRight": false
|
55
|
+
}
|
56
|
+
],
|
57
|
+
"hashCode": 1533792315
|
58
|
+
},
|
59
|
+
{
|
60
|
+
"describe": "Northern Trail Outfitters wants the field sales team to only see the accounts that they own Separate North American and European marketing teams should only see accounts m their respective regions. The inside sales team needs to see all accounts in Salesforce.\nMow can this be accomplished?",
|
61
|
+
"answerOptions": [
|
62
|
+
{
|
63
|
+
"describe": "Set the Organization-Wide Default to Public for accounts. Create criteria- based sharing rules for each marketing team, and create an Inside Sales Team permission set with the \"View Air setting for accounts,",
|
64
|
+
"isRight": false
|
65
|
+
},
|
66
|
+
{
|
67
|
+
"describe": "Set the Organization-Wide Default to Public for accounts. Create profiles for each marketing team, and create an Inside Sales Team role that is at the top of the Role Hteran",
|
68
|
+
"isRight": false
|
69
|
+
},
|
70
|
+
{
|
71
|
+
"describe": "Set the Organization-Wide Default to Private for accounts. Create criteria- based sharing rules for each marketing team, and create an Inside Sales Team profile with the \"View All\" setting for accounts.",
|
72
|
+
"isRight": true
|
73
|
+
},
|
74
|
+
{
|
75
|
+
"describe": "Set the Organization-Wide Default to Private for accounts. Create permission sets for each marketing team, and create an Inside Sales Team profile with the \"View All\" setting for accounts.",
|
76
|
+
"isRight": false
|
77
|
+
}
|
78
|
+
],
|
79
|
+
"hashCode": -827259613
|
80
|
+
},
|
81
|
+
{
|
82
|
+
"describe": "Ursa Major Solar wants to see the Type field from the parent object Galaxy listed on the child record Star. The app builder is receiving an error stating \"Picklist values are only supported in\n4\ncertain functions\".\nWhat formula should an app builder use to achieve the desired result?",
|
83
|
+
"answerOptions": [
|
84
|
+
{
|
85
|
+
"describe": "ISPICKVAL(Galaxy__r.Type__c)",
|
86
|
+
"isRight": false
|
87
|
+
},
|
88
|
+
{
|
89
|
+
"describe": "VALUE(Galaxy_r.Type__c)",
|
90
|
+
"isRight": false
|
91
|
+
},
|
92
|
+
{
|
93
|
+
"describe": "TEXT(Galaxy_r.Type_c)",
|
94
|
+
"isRight": true
|
95
|
+
},
|
96
|
+
{
|
97
|
+
"describe": "FIND(Galaxy__r.Type__c)",
|
98
|
+
"isRight": false
|
99
|
+
}
|
100
|
+
],
|
101
|
+
"hashCode": -981742329
|
102
|
+
},
|
103
|
+
{
|
104
|
+
"describe": "An app builder has modified a Lightning record page for a case and has added an email button item to the page layout; however, users are unable to see the new item on the layout. What are two potential reasons why users are unable to view the item on the Case Lightning record page?\nChoose 2 answers",
|
105
|
+
"answerOptions": [
|
106
|
+
{
|
107
|
+
"describe": "The page layout includes the case feed component.",
|
108
|
+
"isRight": false
|
109
|
+
},
|
110
|
+
{
|
111
|
+
"describe": "The email button contains JavaScript.",
|
112
|
+
"isRight": true
|
113
|
+
},
|
114
|
+
{
|
115
|
+
"describe": "The case page layout also contains custom buttons.",
|
116
|
+
"isRight": false
|
117
|
+
},
|
118
|
+
{
|
119
|
+
"describe": "The page layout excludes the case feed component.",
|
120
|
+
"isRight": true
|
121
|
+
}
|
122
|
+
],
|
123
|
+
"hashCode": -588522680
|
124
|
+
},
|
125
|
+
{
|
126
|
+
"describe": "Accounts at Universal Containers are currently readable by all users but editable only by their owners.\nManagement wants to designate some Accounts as VIP Accounts. Only Account owners should have read access to these VIP accounts.\nWhich two actions should an app builder take to meet the requirements?\nChoose 2 answers",
|
127
|
+
"answerOptions": [
|
128
|
+
{
|
129
|
+
"describe": "Implement a sharing rule.",
|
130
|
+
"isRight": true
|
131
|
+
},
|
132
|
+
{
|
133
|
+
"describe": "Configure a permission set.",
|
134
|
+
"isRight": false
|
135
|
+
},
|
136
|
+
{
|
137
|
+
"describe": "Set up an Account Team.",
|
138
|
+
"isRight": true
|
139
|
+
},
|
140
|
+
{
|
141
|
+
"describe": "Change organization-wide defaults.",
|
142
|
+
"isRight": false
|
143
|
+
}
|
144
|
+
],
|
145
|
+
"hashCode": 321447349
|
146
|
+
},
|
147
|
+
{
|
148
|
+
"describe": "Universal Containers utilizes opportunities and a custom object called Detaited.Sales__c. The company would like to roll sales metrics up to an opportunity for only Detailed.Sales__c records that have their picklist status set to Active.\nWhat is the recommended method for the app bunder to achieve this request?",
|
149
|
+
"answerOptions": [
|
150
|
+
{
|
151
|
+
"describe": "Utilize the AppExchange to download a third-party application that can roH up the sales dollars with the appropriate filter.",
|
152
|
+
"isRight": false
|
153
|
+
},
|
154
|
+
{
|
155
|
+
"describe": "Create a master-detail relationship between the parent and child object with a roll-up summary field that fitters on the status held.",
|
156
|
+
"isRight": true
|
157
|
+
},
|
158
|
+
{
|
159
|
+
"describe": "Create a lookup relationship between the parent and child object with a roll-up summary held that filters on the status field.",
|
160
|
+
"isRight": false
|
161
|
+
},
|
162
|
+
{
|
163
|
+
"describe": "Utilize Apex code to roll up the desired amounts.",
|
164
|
+
"isRight": false
|
165
|
+
}
|
166
|
+
],
|
167
|
+
"hashCode": 710148481
|
168
|
+
},
|
169
|
+
{
|
170
|
+
"describe": "Cloud Kicks wants to make sure that users without the Marketing role are unable to update the Contact Retail Opt In picklist field to Yes.\n4\nWhat validation rule would an app builder use to prevent other users from making this update?",
|
171
|
+
"answerOptions": [
|
172
|
+
{
|
173
|
+
"describe": "AND( $UserRole.Name != 'Marketing', ISCHANGED(Retail_Opt_In__c), ISPICKVAL(Retail_0pt_In_c,\"Yes\") )",
|
174
|
+
"isRight": true
|
175
|
+
},
|
176
|
+
{
|
177
|
+
"describe": "AND( $UserRole.Name != 'Marketing', Retail_Opt_In_c = \"Yes\" )",
|
178
|
+
"isRight": false
|
179
|
+
},
|
180
|
+
{
|
181
|
+
"describe": "AND( $UserRole.Name = 'Marketing', ISPICKVAL(Retail_Opt_In_c,\"Yes\") )",
|
182
|
+
"isRight": false
|
183
|
+
},
|
184
|
+
{
|
185
|
+
"describe": "AND( $UserRole.Name = 'Marketing', Retail_Opt_In__c = \"Yes\" )",
|
186
|
+
"isRight": false
|
187
|
+
}
|
188
|
+
],
|
189
|
+
"hashCode": -910849156
|
190
|
+
},
|
191
|
+
{
|
192
|
+
"describe": "The Recruiting ream at AW Computing captures the job acceptance and date of hire of a candidate on the Job Application custom object. Once the candidate accepts the recruiter s job offer, the date of hire should be entered and not be changed on subsequent cecord edit.\nWhich validation formula should the app builder use?",
|
193
|
+
"answerOptions": [
|
194
|
+
{
|
195
|
+
"describe": "NOT(ISCLANK(Job_Accepted_c)) && ISCHANGED(Hire_Date_c)",
|
196
|
+
"isRight": true
|
197
|
+
},
|
198
|
+
{
|
199
|
+
"describe": "(ISBLANK(Job_Accepted_c) II NOT(lSCMANGED(Mire_Daie_c))",
|
200
|
+
"isRight": false
|
201
|
+
},
|
202
|
+
{
|
203
|
+
"describe": "NOT{IS&lANK(Job_Accepted_c)) II ISCHANGED(Hire_Date_c)",
|
204
|
+
"isRight": false
|
205
|
+
},
|
206
|
+
{
|
207
|
+
"describe": "(lSBLANK(Job_Accepted_c) && NOT(lSCHANGED(Hire_Date_c))",
|
208
|
+
"isRight": false
|
209
|
+
}
|
210
|
+
],
|
211
|
+
"hashCode": 467305167
|
212
|
+
},
|
213
|
+
{
|
214
|
+
"describe": "An app builder has created a custom Lightning App and wants to make it available to the internal users at Universal Containers.\nWhich two steps are necessary to accomplish this task?\nChoose 2 answers",
|
215
|
+
"answerOptions": [
|
216
|
+
{
|
217
|
+
"describe": "Add the app to a Visualforce page.",
|
218
|
+
"isRight": true
|
219
|
+
},
|
220
|
+
{
|
221
|
+
"describe": "Upload the app to Static Resources.",
|
222
|
+
"isRight": false
|
223
|
+
},
|
224
|
+
{
|
225
|
+
"describe": "Create a subdomain using My Domain.",
|
226
|
+
"isRight": false
|
227
|
+
},
|
228
|
+
{
|
229
|
+
"describe": "Build a Custom Tab for the app.",
|
230
|
+
"isRight": true
|
231
|
+
}
|
232
|
+
],
|
233
|
+
"hashCode": -1002180686
|
234
|
+
},
|
235
|
+
{
|
236
|
+
"describe": "DreamHouse Realty wants to import its property records from an external system into Salesforce. The app builder will use an external ID field to house the property ID from the external system.\nWhich two details should the app builder know when using external ID fields?\nChoose 2 answers",
|
237
|
+
"answerOptions": [
|
238
|
+
{
|
239
|
+
"describe": "An external ID field can be a number field.",
|
240
|
+
"isRight": true
|
241
|
+
},
|
242
|
+
{
|
243
|
+
"describe": "An external ID field can be a URL field.",
|
244
|
+
"isRight": false
|
245
|
+
},
|
246
|
+
{
|
247
|
+
"describe": "An external ID field can be a phone field.",
|
248
|
+
"isRight": false
|
249
|
+
},
|
250
|
+
{
|
251
|
+
"describe": "An external ID field can be a text field.",
|
252
|
+
"isRight": true
|
253
|
+
}
|
254
|
+
],
|
255
|
+
"hashCode": 1414273358
|
256
|
+
},
|
257
|
+
{
|
258
|
+
"describe": "Cloud Kicks (CK) switched to Lightning Experience and started using Chatter across its global workforce to support its fast-paced sales cycle. CK loves Chatter but struggle with gathering feedback from core team members, including understanding who is available to respond.\nWhich two ways could CK use Chatter to solve this problem?\nChoose 2 answers",
|
259
|
+
"answerOptions": [
|
260
|
+
{
|
261
|
+
"describe": "Streams",
|
262
|
+
"isRight": false
|
263
|
+
},
|
264
|
+
{
|
265
|
+
"describe": "Polls",
|
266
|
+
"isRight": true
|
267
|
+
},
|
268
|
+
{
|
269
|
+
"describe": "Out of Office",
|
270
|
+
"isRight": true
|
271
|
+
},
|
272
|
+
{
|
273
|
+
"describe": "Topics",
|
274
|
+
"isRight": false
|
275
|
+
}
|
276
|
+
],
|
277
|
+
"hashCode": 1685554524
|
278
|
+
},
|
279
|
+
{
|
280
|
+
"describe": "Cloud Kicks (CK) keeps track of its shoe inventory in Salesforce. When an order's status is changed to Activated, the inventory for the ordered shoe is reduced. At that point, a SOAP web service on the CK website must be called so that the website is updated to display the correct inventory amount for the shoe.\nWhat should an app builder use to communicate to the CK web service when a shoe's inventory has changed?",
|
281
|
+
"answerOptions": [
|
282
|
+
{
|
283
|
+
"describe": "After-Save Record-Triggered flow",
|
284
|
+
"isRight": false
|
285
|
+
},
|
286
|
+
{
|
287
|
+
"describe": "Before-Save Record-Triggered flow",
|
288
|
+
"isRight": false
|
289
|
+
},
|
290
|
+
{
|
291
|
+
"describe": "Process Builder",
|
292
|
+
"isRight": false
|
293
|
+
},
|
294
|
+
{
|
295
|
+
"describe": "Workflow rule",
|
296
|
+
"isRight": true
|
297
|
+
}
|
298
|
+
],
|
299
|
+
"hashCode": -1910384827
|
300
|
+
},
|
301
|
+
{
|
302
|
+
"describe": "Universal Containers allows all employees to submit reviews for leadership using a custom object called Review. These Reviews should only be visible to the HR department and the employee who submitted the record.\nWhich three steps should an app builder take to properly control access to Reviews?\nChoose 3 answers",
|
303
|
+
"answerOptions": [
|
304
|
+
{
|
305
|
+
"describe": "Disable Grant Access Using Hierarchies.",
|
306
|
+
"isRight": true
|
307
|
+
},
|
308
|
+
{
|
309
|
+
"describe": "Add a Master-Detail(User; field on the Review object.",
|
310
|
+
"isRight": false
|
311
|
+
},
|
312
|
+
{
|
313
|
+
"describe": "Create a criteria-based Sharing Rule for the HR Department.",
|
314
|
+
"isRight": true
|
315
|
+
},
|
316
|
+
{
|
317
|
+
"describe": "Remove Review Read permission from non-HR Department user Profiles.",
|
318
|
+
"isRight": false
|
319
|
+
},
|
320
|
+
{
|
321
|
+
"describe": "Set organization-wide default to Private.",
|
322
|
+
"isRight": true
|
323
|
+
}
|
324
|
+
],
|
325
|
+
"hashCode": -523123007
|
326
|
+
},
|
327
|
+
{
|
328
|
+
"describe": "An app builder wants to update a field on the parent record when a child record connected via lookup is deleted.\n4\nWhat automation should the app builder use?",
|
329
|
+
"answerOptions": [
|
330
|
+
{
|
331
|
+
"describe": "Screen flow",
|
332
|
+
"isRight": false
|
333
|
+
},
|
334
|
+
{
|
335
|
+
"describe": "Process Builder",
|
336
|
+
"isRight": false
|
337
|
+
},
|
338
|
+
{
|
339
|
+
"describe": "Apex code",
|
340
|
+
"isRight": true
|
341
|
+
},
|
342
|
+
{
|
343
|
+
"describe": "Workflow rule",
|
344
|
+
"isRight": false
|
345
|
+
}
|
346
|
+
],
|
347
|
+
"hashCode": -775715467
|
348
|
+
},
|
349
|
+
{
|
350
|
+
"describe": "Universal Containers is setting up salesforce for the first time. Management wants the sales and marketing teams to have different navigation names in the salesforce1 mobile app. Which option is available to an app builder to satisfy the requirement?",
|
351
|
+
"answerOptions": [
|
352
|
+
{
|
353
|
+
"describe": "Create sales and marketing profiles to ensure read access to different objects",
|
354
|
+
"isRight": false
|
355
|
+
},
|
356
|
+
{
|
357
|
+
"describe": "Create roles for sales and marketing and assign a custom homepage layout for each role.",
|
358
|
+
"isRight": false
|
359
|
+
},
|
360
|
+
{
|
361
|
+
"describe": "Create mobile navigation menus for both the sales and marketing profiles.",
|
362
|
+
"isRight": true
|
363
|
+
},
|
364
|
+
{
|
365
|
+
"describe": "Create public groups for sales and marketing and create mobile navigation menus for each group .",
|
366
|
+
"isRight": false
|
367
|
+
}
|
368
|
+
],
|
369
|
+
"hashCode": -118303124
|
370
|
+
},
|
371
|
+
{
|
372
|
+
"describe": "An app builder created multiple custom fields, page layouts, and reports in the sandbox and added them to a change set set was deployed to production, the reports were NOT deployed.\nWhat should the app builder do?",
|
373
|
+
"answerOptions": [
|
374
|
+
{
|
375
|
+
"describe": "Move the reports to the Untried Public Reports folder and add them to a new change set.",
|
376
|
+
"isRight": true
|
377
|
+
},
|
378
|
+
{
|
379
|
+
"describe": "Move the reports from the Unfiled Public Reports folder and add them to a new change set",
|
380
|
+
"isRight": false
|
381
|
+
},
|
382
|
+
{
|
383
|
+
"describe": "Recreate the reports in production. Reports are not supported in change sets",
|
384
|
+
"isRight": false
|
385
|
+
},
|
386
|
+
{
|
387
|
+
"describe": "Add the reports to an unmanaged package and install the unmanaged package into production.",
|
388
|
+
"isRight": false
|
389
|
+
}
|
390
|
+
],
|
391
|
+
"hashCode": -358983186
|
392
|
+
},
|
393
|
+
{
|
394
|
+
"describe": "SERVICE AGENTS ARE REQUIRED TO CONFIRM A USER IDENTITY BEFORE PROVIDING SUPPORT INFORMATION OVER THE PHONE. WHAT FEATURE CAN AN APP BUILDER USE TO HELP AGENTS MEET THIS REQUIREMENT?",
|
395
|
+
"answerOptions": [
|
396
|
+
{
|
397
|
+
"describe": "Include Surveys as a Case related list",
|
398
|
+
"isRight": false
|
399
|
+
},
|
400
|
+
{
|
401
|
+
"describe": "Case Validation Rules",
|
402
|
+
"isRight": false
|
403
|
+
},
|
404
|
+
{
|
405
|
+
"describe": "Add Path to the top of the Case layout",
|
406
|
+
"isRight": false
|
407
|
+
},
|
408
|
+
{
|
409
|
+
"describe": "Guided Action Flows on the record page",
|
410
|
+
"isRight": true
|
411
|
+
}
|
412
|
+
],
|
413
|
+
"hashCode": -1508983994
|
414
|
+
},
|
415
|
+
{
|
416
|
+
"describe": "An app builder has downloaded a component from the AppExchange successfully; however, they are unable to add it to the Lightning home page.\nWhich two reasons can be preventing the app builder from being able to add the custom component?\nChoose 2 answers\nA My Domain must be deployed to add custom components to the page with the App Builder.\nB",
|
417
|
+
"answerOptions": [
|
418
|
+
{
|
419
|
+
"describe": "custom tab must be created to add custom components to the page with the App Builder.\nC The component requires a developer permission to add it to the page with the App Builder.\nD The component is tagged for record pages instead of home pages and is not showing up in the App Builder.\n5",
|
420
|
+
"isRight": true
|
421
|
+
}
|
422
|
+
],
|
423
|
+
"hashCode": -1711754862
|
424
|
+
},
|
425
|
+
{
|
426
|
+
"describe": "Universal Containers's app builder has been tasked with replacing workflow rules and Apex triggers with Process Builders where possible.\nWhat are two important considerations an app builder should know before the project is started? Choose 2 answers",
|
427
|
+
"answerOptions": [
|
428
|
+
{
|
429
|
+
"describe": "Avoid generating infinite loops.",
|
430
|
+
"isRight": true
|
431
|
+
},
|
432
|
+
{
|
433
|
+
"describe": "Apex has a different SOQL query limit than Flow.",
|
434
|
+
"isRight": false
|
435
|
+
},
|
436
|
+
{
|
437
|
+
"describe": "Create a process for each workflow rule.",
|
438
|
+
"isRight": false
|
439
|
+
},
|
440
|
+
{
|
441
|
+
"describe": "Combine actions when possible.",
|
442
|
+
"isRight": true
|
443
|
+
}
|
444
|
+
],
|
445
|
+
"hashCode": -2002185607
|
446
|
+
},
|
447
|
+
{
|
448
|
+
"describe": "Universal Containers wants to track installation information once it container has been purchased on a custom object. Sales reps should have visibility of all the installation with their opportunities.\nvisibility of all the installations associated with their opportunities.\nWhat kind of relationship should this new object have to the Opportunity?",
|
449
|
+
"answerOptions": [
|
450
|
+
{
|
451
|
+
"describe": "Lookup",
|
452
|
+
"isRight": false
|
453
|
+
},
|
454
|
+
{
|
455
|
+
"describe": "Hierarchical",
|
456
|
+
"isRight": false
|
457
|
+
},
|
458
|
+
{
|
459
|
+
"describe": "Master-Detail",
|
460
|
+
"isRight": false
|
461
|
+
},
|
462
|
+
{
|
463
|
+
"describe": "Many to Many",
|
464
|
+
"isRight": true
|
465
|
+
}
|
466
|
+
],
|
467
|
+
"hashCode": -1304558473
|
468
|
+
},
|
469
|
+
{
|
470
|
+
"describe": "Ursa Major Solar wants to convert the relationship between Galaxy and Star from a lookup relationship to a master-detail relationship so each Galaxy record can be equipped with a roll-up summary count of Star records.\nWhich two considerations should be made?\nChoose 2 answers",
|
471
|
+
"answerOptions": [
|
472
|
+
{
|
473
|
+
"describe": "The Star records are all required to have an existing value in their Galaxy field.",
|
474
|
+
"isRight": true
|
475
|
+
},
|
476
|
+
{
|
477
|
+
"describe": "The Galaxy object has fewer than two existing master-detail relationships.",
|
478
|
+
"isRight": false
|
479
|
+
},
|
480
|
+
{
|
481
|
+
"describe": "The Galaxy object is required to contain existing roll-up summary fields.",
|
482
|
+
"isRight": false
|
483
|
+
},
|
484
|
+
{
|
485
|
+
"describe": "The Star object has fewer than two existing master-detail relationships.",
|
486
|
+
"isRight": true
|
487
|
+
}
|
488
|
+
],
|
489
|
+
"hashCode": 438531646
|
490
|
+
},
|
491
|
+
{
|
492
|
+
"describe": "Northern Trail Outfitters wants to broadcast an email to 7,000 contacts m Salesforce on a regular basis but realizes Salesforce is mass functionality has a limitation on the number erf emails that can be sent each day.\n5\nWhat action should the app builder take?",
|
493
|
+
"answerOptions": [
|
494
|
+
{
|
495
|
+
"describe": "Request Salesforce increase the number of maximum daily emails.",
|
496
|
+
"isRight": false
|
497
|
+
},
|
498
|
+
{
|
499
|
+
"describe": "Develop Apex code and bghtnrrvg web component to send dairy emails",
|
500
|
+
"isRight": false
|
501
|
+
},
|
502
|
+
{
|
503
|
+
"describe": "Research and evaluate products available on AppExchange to send mass emails.",
|
504
|
+
"isRight": true
|
505
|
+
},
|
506
|
+
{
|
507
|
+
"describe": "Export Contacts to a CSV file and use an email client to send tha emails.",
|
508
|
+
"isRight": false
|
509
|
+
}
|
510
|
+
],
|
511
|
+
"hashCode": -165089578
|
512
|
+
},
|
513
|
+
{
|
514
|
+
"describe": "The convert button on leads should NOT appear until the lead status picklist is set to a qualified. What should an app builder suggest to meet these requirements?",
|
515
|
+
"answerOptions": [
|
516
|
+
{
|
517
|
+
"describe": "Picklist dependency, page layouts, record types",
|
518
|
+
"isRight": false
|
519
|
+
},
|
520
|
+
{
|
521
|
+
"describe": "Custom button, validation rule, record types",
|
522
|
+
"isRight": false
|
523
|
+
},
|
524
|
+
{
|
525
|
+
"describe": "Process builder field update, quick action, record type",
|
526
|
+
"isRight": false
|
527
|
+
},
|
528
|
+
{
|
529
|
+
"describe": "Page layout, record types, process builder field update",
|
530
|
+
"isRight": true
|
531
|
+
}
|
532
|
+
],
|
533
|
+
"hashCode": 609407796
|
534
|
+
},
|
535
|
+
{
|
536
|
+
"describe": "An app builder needs a custom solution and is considering using community. Ease of updates is the primary consideration.\nWhat should the app builder consider?\nA",
|
537
|
+
"answerOptions": [
|
538
|
+
{
|
539
|
+
"describe": "managed package from AppExchange",
|
540
|
+
"isRight": true
|
541
|
+
},
|
542
|
+
{
|
543
|
+
"describe": "An unmanaged package from AppExchange",
|
544
|
+
"isRight": false
|
545
|
+
},
|
546
|
+
{
|
547
|
+
"describe": "An open-source unmanaged package",
|
548
|
+
"isRight": false
|
549
|
+
},
|
550
|
+
{
|
551
|
+
"describe": "An open-source custom development",
|
552
|
+
"isRight": false
|
553
|
+
}
|
554
|
+
],
|
555
|
+
"hashCode": -1806024963
|
556
|
+
},
|
557
|
+
{
|
558
|
+
"describe": "The sales Operations team at AWS Computing deletes accounts for a variety of a reasons. The sales ops director is worried that the Sales team may delete accounts that sales reps are actively selling into.\nMow should the app builder keep accounts with open opportunities from being delected?",
|
559
|
+
"answerOptions": [
|
560
|
+
{
|
561
|
+
"describe": "Create an Apex Trigger on the Account object",
|
562
|
+
"isRight": true
|
563
|
+
},
|
564
|
+
{
|
565
|
+
"describe": "Create a validation rule on the Account object.",
|
566
|
+
"isRight": false
|
567
|
+
},
|
568
|
+
{
|
569
|
+
"describe": "Remove the delete button on the account layout",
|
570
|
+
"isRight": false
|
571
|
+
},
|
572
|
+
{
|
573
|
+
"describe": "Remove the Delete permission from the Sales Rep profile.",
|
574
|
+
"isRight": false
|
575
|
+
}
|
576
|
+
],
|
577
|
+
"hashCode": -1480304611
|
578
|
+
},
|
579
|
+
{
|
580
|
+
"describe": "Universal Containers require different fields to be filled out at each stage of the Opportunity sates process.\nWhat configuration steps can an app builder use to meet this requirement?",
|
581
|
+
"answerOptions": [
|
582
|
+
{
|
583
|
+
"describe": "Set page layout required fields based on the current stage.",
|
584
|
+
"isRight": false
|
585
|
+
},
|
586
|
+
{
|
587
|
+
"describe": "Create a Process Builder to prompt the User for field information.",
|
588
|
+
"isRight": false
|
589
|
+
},
|
590
|
+
{
|
591
|
+
"describe": "Define record types and page layouts for each stage.",
|
592
|
+
"isRight": false
|
593
|
+
},
|
594
|
+
{
|
595
|
+
"describe": "Add the Path component to the Lightning record page.",
|
596
|
+
"isRight": true
|
597
|
+
}
|
598
|
+
],
|
599
|
+
"hashCode": 720141189
|
600
|
+
},
|
601
|
+
{
|
602
|
+
"describe": "Cloud Kicks has five years of sales data and would like to track when customers made their first purchase.\nHow should an app builder use a roll-up summary to meet the requirements?\n5",
|
603
|
+
"answerOptions": [
|
604
|
+
{
|
605
|
+
"describe": "Create a new roll-up summary field called First Order Date, using Type MIN on the Opportunity Close Date with a filter where IsWon = TRUE.",
|
606
|
+
"isRight": true
|
607
|
+
},
|
608
|
+
{
|
609
|
+
"describe": "Create a new date field called First Order Date, create a new Workflow to set the date, and roll up the value with a filter where IsWon = TRUE.",
|
610
|
+
"isRight": false
|
611
|
+
},
|
612
|
+
{
|
613
|
+
"describe": "Create a new roll-up summary field called First Order Date, using Type SUM on Opportunity Close Date.",
|
614
|
+
"isRight": false
|
615
|
+
},
|
616
|
+
{
|
617
|
+
"describe": "Create a new date field called First Order Date, then create a roll-up summary to update the field using Type MIN.",
|
618
|
+
"isRight": false
|
619
|
+
}
|
620
|
+
],
|
621
|
+
"hashCode": -639740226
|
622
|
+
},
|
623
|
+
{
|
624
|
+
"describe": "DreamHouse Realty (DR) is expanding into subsidized housing by partnering with local government entitles.\nDR uses Sales Cloud and has enabled field history tracking on the Opportunity object. Due to increased Information requirements, the App Dev team is changing Text Area (Long) fields to Rich Text fields to allow for up to 1,000 characters and better descriptions.\nWhich two considerations should be made by the team?\nChoose 2 answers",
|
625
|
+
"answerOptions": [
|
626
|
+
{
|
627
|
+
"describe": "Rich text field values of all lengths are displayed fully in reports.",
|
628
|
+
"isRight": false
|
629
|
+
},
|
630
|
+
{
|
631
|
+
"describe": "Data loss may occur when changing custom field types.",
|
632
|
+
"isRight": true
|
633
|
+
},
|
634
|
+
{
|
635
|
+
"describe": "Field History Tracking records value changes of 255 characters or less.",
|
636
|
+
"isRight": true
|
637
|
+
},
|
638
|
+
{
|
639
|
+
"describe": "Audit Trail is available through REST API extracts.",
|
640
|
+
"isRight": false
|
641
|
+
}
|
642
|
+
],
|
643
|
+
"hashCode": 517296169
|
644
|
+
},
|
645
|
+
{
|
646
|
+
"describe": "",
|
647
|
+
"answerOptions": [
|
648
|
+
{
|
649
|
+
"describe": "Service Coordinator (SC) for Ursa Major Solar (UMS) does a final review of work orders owned by a technician for a specific region before the records are submitted for an invoice. Before closing out the work order, the SC needs to modify data or remove attachments that were added by mistake. The SC also needs access to any other related records owned by the technician.\nWhat solution would provide the required access, given a private data model?",
|
650
|
+
"isRight": false
|
651
|
+
}
|
652
|
+
],
|
653
|
+
"hashCode": -1483431938
|
654
|
+
},
|
655
|
+
{
|
656
|
+
"describe": "Cloud Kicks wants to efficiently Increase the company's adoption of Salesforce while simultaneously moving away from their reliance on spreadsheets. An app builder is given a spreadsheet everyone is sharing that needs to be added to Salesforce. The object with fields needs to be created and the data inserted simultaneously.\nWhich tool should be used?",
|
657
|
+
"answerOptions": [
|
658
|
+
{
|
659
|
+
"describe": "Import Wizard",
|
660
|
+
"isRight": false
|
661
|
+
},
|
662
|
+
{
|
663
|
+
"describe": "Lightning Object Creator",
|
664
|
+
"isRight": true
|
665
|
+
},
|
666
|
+
{
|
667
|
+
"describe": "Data Loader",
|
668
|
+
"isRight": false
|
669
|
+
},
|
670
|
+
{
|
671
|
+
"describe": "Schema Builder",
|
672
|
+
"isRight": false
|
673
|
+
}
|
674
|
+
],
|
675
|
+
"hashCode": -88800096
|
676
|
+
},
|
677
|
+
{
|
678
|
+
"describe": "Cloud Kicks wants to know the total value of all won Opportunities for Accounts and display\n5\nit on the record.\nWhat type of summary should the app builder use in the roll-up summary field?",
|
679
|
+
"answerOptions": [
|
680
|
+
{
|
681
|
+
"describe": "Count",
|
682
|
+
"isRight": false
|
683
|
+
},
|
684
|
+
{
|
685
|
+
"describe": "Q Max",
|
686
|
+
"isRight": false
|
687
|
+
},
|
688
|
+
{
|
689
|
+
"describe": "Sum",
|
690
|
+
"isRight": true
|
691
|
+
},
|
692
|
+
{
|
693
|
+
"describe": "Min",
|
694
|
+
"isRight": false
|
695
|
+
}
|
696
|
+
],
|
697
|
+
"hashCode": -346868483
|
698
|
+
},
|
699
|
+
{
|
700
|
+
"describe": "Sales reps at Cloud Kicks (CK) forget to submit for approval when CK needs orders reviewed before close won. CK wants to automatically submit opportunities into the Secure Commitment Stage to eliminate manual submission.\nWhich three features would meet the business requirements?\nChoose 3 answers",
|
701
|
+
"answerOptions": [
|
702
|
+
{
|
703
|
+
"describe": "Workflow",
|
704
|
+
"isRight": false
|
705
|
+
},
|
706
|
+
{
|
707
|
+
"describe": "Process Builder",
|
708
|
+
"isRight": true
|
709
|
+
},
|
710
|
+
{
|
711
|
+
"describe": "Apex",
|
712
|
+
"isRight": true
|
713
|
+
},
|
714
|
+
{
|
715
|
+
"describe": "Chatter action",
|
716
|
+
"isRight": false
|
717
|
+
},
|
718
|
+
{
|
719
|
+
"describe": "Flow",
|
720
|
+
"isRight": true
|
721
|
+
}
|
722
|
+
],
|
723
|
+
"hashCode": 1006248736
|
724
|
+
},
|
725
|
+
{
|
726
|
+
"describe": "UC has a requirement that an opportunity should have a field showing the value of its associated account's billing state. This value should not change after the opportunity has been created. Is there a recommended solution to configure this automated behavior?",
|
727
|
+
"answerOptions": [
|
728
|
+
{
|
729
|
+
"describe": "Formula field",
|
730
|
+
"isRight": false
|
731
|
+
},
|
732
|
+
{
|
733
|
+
"describe": "Apex",
|
734
|
+
"isRight": false
|
735
|
+
},
|
736
|
+
{
|
737
|
+
"describe": "Workflow",
|
738
|
+
"isRight": true
|
739
|
+
},
|
740
|
+
{
|
741
|
+
"describe": "Roll-up summary field",
|
742
|
+
"isRight": false
|
743
|
+
}
|
744
|
+
],
|
745
|
+
"hashCode": -18538208
|
746
|
+
},
|
747
|
+
{
|
748
|
+
"describe": "Cloud Kicks recently implemented the application lifecycle management process to its release management strategy.\nWhich category handles bug fixes and simple changes?",
|
749
|
+
"answerOptions": [
|
750
|
+
{
|
751
|
+
"describe": "Patch",
|
752
|
+
"isRight": true
|
753
|
+
},
|
754
|
+
{
|
755
|
+
"describe": "Minor",
|
756
|
+
"isRight": false
|
757
|
+
},
|
758
|
+
{
|
759
|
+
"describe": "Major",
|
760
|
+
"isRight": false
|
761
|
+
},
|
762
|
+
{
|
763
|
+
"describe": "Rollback",
|
764
|
+
"isRight": false
|
765
|
+
}
|
766
|
+
],
|
767
|
+
"hashCode": 2132780982
|
768
|
+
}
|
769
|
+
],
|
770
|
+
"hashCode": 328385632
|
771
|
+
}
|