Cloud Data Management Specialist

Question

CC360: Out of the box, Cloud MDM cleanses and standardizes data in which Salesforce objects?

Answer 1

The process of taking data from multiple sources to create a 'golden record'.

Answer 2

The process of merging two or more duplicate records.

Answer 3

Changing the settings is only required for advanced operations.

Answer 4

The settings should be configured before running Cloud MDM jobs.

Answer 5

The settings are present but not visible after installation.

Answer 6

Synchronize

Answer 7

Company Norm

Answer 8

Record Type

Answer 9

Country ISO Code

Answer 10

Select which fields to display on a Visual Force page.

Answer 11

Control which fields are compared when searching for duplicates.

Answer 12

Account Bean

Answer 13

Contact Bean

Answer 14

Master Bean

Answer 15

Synchronization

Answer 16

Standardization

Answer 17

For newly created records, the value will be true.

Answer 18

For existing records in Salesforce the value will be false.

Answer 19

Allows the movement of a record to and from the Cloud MDM staging area.

Answer 20

Can be used to synchronize a subset of data.

Answer 21

Matching settings

Answer 22

Bean settings

Answer 23

Synchronization settings

Answer 24

Hierarchies

Answer 25

Quality of reports

Answer 26

Improving matching results

Answer 27

When Cloud MDM is installed.

Answer 28

When a record is synchronized.

Answer 29

When a data steward clicks the 'Cleanse' button.

Answer 30

Identifying duplicate records.

Answer 31

Matching records from external data sources to accounts.

Answer 32

Grouping records with similar characteristics.

Answer 33

Matching leads/contacts to accounts.

Answer 34

Performs a fuzzy match on all included fields.

Answer 35

Performs a fuzzy match on the segments.

Answer 36

Performs an exact match on the segments.

Answer 37

Slows down the fuzzy matching process.

Answer 38

Determines which records will be fuzzy matched.

Answer 39

Speeds up the fuzzy matching process.

Answer 40

Reduces the total number of records being fuzzy matched.

Answer 41

Null scores

Answer 42

Field order

Answer 43

Field weighting

Answer 44

Threshold values

Answer 45

Synchronization settings

Answer 46

Duplicate settings

Answer 47

Matching settings

Answer 48

The total score will be set to 0 and the records will not be considered a match.

Answer 49

The weighted score for that field will be doubled.

Answer 50

A score of 0 is assigned to that field.

Answer 51

All master beans in the same segment.

Answer 52

All account records in the Salesforce org.

Answer 53

All account records in the same segment.

Answer 54

Contact to Lead beans in the same segment.

Answer 55

All Contact beans in the same segment.

Answer 56

Account and Contact beans in the same segment.

Answer 57

All Lead beans in the same segment.

Answer 58

Assign a Cloud MDM profile to your user.

Answer 59

Be the Salesforce administrator.

Answer 60

Add the Duplicate Accounts VisualForce page to the Account page layout.

Answer 61

Identify and mark any 'no duplicate' pairs.

Answer 62

Toggle the master record where necessary.

Answer 63

Use Salesforce side-by-side comparison to examine each duplicate pair.

Answer 64

Analyze duplicate records using reports and side-by-side comparisons.

Answer 65

Groups records by the master.

Answer 66

Is only available to data stewards and administrators.

Answer 67

Pulls in data from the related master and detail Account, Contact or Lead.

Answer 68

The Salesforce page layout.

Answer 69

The Cloud MDM Profile of the user.

Answer 70

The default Salesforce profile of the user.

Answer 71

The lead will not convert.

Answer 72

The lead is converted and the existing contact is updated.

Answer 73

The existing contact is automatically deleted, then the lead is converted.

Answer 74

Lead Parent

Answer 75

Contact (lookup)

Answer 76

Master Account

Answer 77

Account (lookup)

Answer 78

Matching threshold for Account.

Answer 79

Matching settings for Account and Contact.

Answer 80

Batch Acceleration Level for Matching job.

Answer 81

Segment settings for Account and Contact.

Answer 82

Integrate to Staging Area (Beans).

Answer 83

Integrate directly to Account object.

Answer 84

Create a Data Source.

Answer 85

You should load data before doing any setup.

Answer 86

Perform Duplicate Check.

Answer 87

The process of associating leads and contacts to accounts.

Answer 88

The process of associating records of the same object class.

Answer 89

The process of associating beans to master beans.

Answer 90

The process of associating data from an external source with an account.

Answer 91

The bean is associated with a global master bean.

Answer 92

The bean is flagged as 'No Match'.

Answer 93

A new master bean is created.

Answer 94

Shows data currently on account.

Answer 95

Shows data currently on master bean.

Answer 96

Shows historical data for account.

Answer 97

Lists data sources for the master bean.

Answer 98

Configure field sets for Account search and results.

Answer 99

Ensure the Parent ID field is mapped in the Account Synchronization settings.

Answer 100

Add the Parent ID field to the Master Bean page layout.

Answer 101

Add the Hierarchies VisualForce page to the Account page layout.

Answer 102

Cloud MDM's graphical hierarchy editor.

Answer 103

Via the master beans.

Answer 104

The native Salesforce Parent field.

Answer 105

Imported from an external system.

Answer 106

The account, along with any children, will be moved to the new hierarchy.

Answer 107

The account will be copied and assigned a unique name.

Answer 108

The account will be added to both hierarchies.

Answer 109

Navigate to the Account bean for the ultimate parent and edit the Hierarchy Type field.

Answer 110

Edit the Hierarchy Type field on the Account that is the ultimate parent.

Answer 111

Navigate to the Master bean for the ultimate parent and edit the Hierarchy Type field.

Answer 112

A second bean with source equal to the other is created and associated with the master bean for the account.

Answer 113

The second bean with source equal to the account is created under the master bean.

Answer 114

A second bean is created and associated with the account.

Answer 115

Load data then manually update the Parent ID fields.

Answer 116

Load data in order - parent accounts, then child accounts, etc

Answer 117

Load data in first job, then create parent relationships in second job.

Answer 118

Populate the Parent ID field and load all data in a single job.

Answer 119

Delimited plain text files

Answer 120

Word document

Answer 121

Binary document

Answer 122

Fixed-width

Answer 123

Excel document

Answer 124

All of these.

Answer 125

NCOA (National Change of Address)

Answer 126

Deceased Check

Answer 127

Opportunities

Answer 128

Any time your main objective is to collect email addresses.

Answer 129

Any time an email is collected for transactional messages, such as e-receipts, order confirmations and shipping notifications.

Answer 130

Any time a customer service representative is verbally asking for a customer's email address and typing it in.

Answer 131

All of these options.

Answer 132

Point of collection

Answer 133

2 days later

Answer 134

1 week later

Answer 135

200 Email Valid

Answer 136

220 Analytics in Progress

Answer 137

Safe to Send

Answer 138

300 Email Not Valid

Answer 139

The target email domain is a 'Grey List' server.

Answer 140

The email is invalid.

Answer 141

The timeout value you have specified is too short for the specified domain.

Answer 142

All are correct.

Answer 143

These emails are based internationally and are safe.

Answer 144

The email addresses are not directly owned or controlled by a 3rd party DNSBL site.

Answer 145

3rd party oversight emails specifically used for monitoring resources, many times for deliverability monitoring.

Answer 146

Both of these

Answer 147

Neither of these

Answer 148

Status description

Answer 149

Field name

Answer 150

Both of these

Answer 151

Neither of these

Answer 152

Configure Webhook, create form, create Smart Campaign, test landing page

Answer 153

Create Webhook, create Smart Campaign, create form, test landing page

Answer 154

Create form, test landing page, create Webhook, create Smart Campaign

Answer 155

It separates the endpoint of the API from the parameters that are supplied.

Answer 156

It tells customer that they need to edit the REST information.

Answer 157

To make customers confused.

Answer 158

Licence key

Answer 159

Neither of these.

Answer 160

All of these.

Answer 161

Welcome, opt in, help, stop

Answer 162

Opt in, stop, help, unknown

Answer 163

Welcome, opt in, help, unknown

Answer 164

Welcome, stop, help, unknown

Answer 165

None of the above

Answer 166

Create Campaign

Answer 167

Create response mapping

Answer 168

Create a secondary webhook

Answer 169

Smart campaign, Webhook, form, test landing page

Answer 170

Webhook, form, smart campaign, test landing page

Answer 171

Form, Webhook, smart campaign, test landing page

Answer 172

Test landing page, Webhook, form, smart campaign

Answer 173

Account ID, to number, message txt

Answer 174

License key, from number, message txt

Answer 175

License key, to number, header txt

Answer 176

License key, to number, message txt

Answer 177

Improve email campaign performance with better deliverability

Answer 178

Minimize risks associated with bad list hygiene

Answer 179

Enhance customer loyalty and satisfaction

Answer 180

Wasting your marketing budget by sending to bad email addresses.

Answer 181

Sending to a trap/spam email, resulting as being blacklisted as a spam sender.

Answer 182

Reaching customers with no interest in your products or services.

Answer 183

Webforms and landing pages

Answer 184

E-commerce websites (e.g. at checkout or newsletter sign-up)

Answer 185

Preference centres

Answer 186

Point of sale (in-store email acquisition and e-receipts)

Answer 187

List acquisition

Answer 188

CRM and marketing databases

Answer 189

Call centres

Answer 190

Real-time - verified at point of collection or when data is synchronized with the CRM system / marketing database.

Answer 191

Batch - one off verification or as part of a routine back-end process

Answer 192

End-point - verifying successfully sent emails

Answer 193

Status codes, Reason codes, Hygiene results

Answer 194

Progress codes, Reason codes, Hygiene codes

Answer 195

Status codes, Hygiene codes, Recipient type codes

Answer 196

200 Email Valid

Answer 197

300 Email Valid

Answer 198

210 Domain Confirmed

Answer 199

220 Analytics in Progress

Answer 200

420 Analytics in Progress

Answer 201

250 Email Valid, Potentially Dangerous

Answer 202

250 Domain Confirmed, Potentially Dangerous

Answer 203

270 Analytics in Progress, Potentially Dangerous

Answer 204

410 Not Verified

Answer 205

310 Not Verified

Answer 206

250 Email Valid, Potentiall Dangerous

Answer 207

260 Domain Confirmed, Potentially Dangerous

Answer 208

270 Analytics in Progress, Potentially Dangerous

Answer 209

300 Email Not Valid

Answer 210

310 Not Verfied

Answer 211

400 Not Verified

Answer 212

220 Analytics in Progress

Answer 213

To provide further insight into the Status Codes, particularly in the case of Analytics in Progress or failure codes.

Answer 214

To tell you when an email has been automatically sent to a customer's spam/junk mail folder.

Answer 215

To highlight invalid email address formats.

Answer 216

Place email validation at the end of the inputs form, so that all information is available.

Answer 217

Place the email validation at the start of the input form and give a 'Verify' button to the user.

Answer 218

Place the email validation at the start of the input form and use the mouse-click or tab away from the email field to initiate the email verification process automatically.

Answer 219

Black listing

Answer 220

Grey listnig

Answer 221

White listing

Answer 222

Red listing

Answer 223

.csv file with mandatory email address column

Answer 224

.txt file with mandatory email address column

Answer 225

.csv file with mandatory email address and id columns

Answer 226

.txt file with mandatory email address and id columns

Answer 227

Migrate Hierarchy

Answer 228

Migrate Accounts

Answer 229

Migrate Contacts

Answer 230

Migrate Leads

Answer 231

Migrate Products

Answer 232

Migrate Opportunities

Answer 233

Numeric (Fuzzy if non-numeric)

Answer 234

Exact match

Answer 235

Numeric (Fuzzy if non-numeric)

Answer 236

Exact match

Answer 237

Numeric (Fuzzy if non-numeric)

Answer 238

Exact match

Answer 239

3-4 Fuzzy matching

Answer 240

5-6 Exact match

Answer 241

1-5 Numeric matching

Answer 242

1-2 Numeric matching

Answer 243

16-20 used for consolidation/enrichment/comparison

Answer 244

7-20 used for consolidation/enrichment/comparison

Answer 245

1-6 used for consolidation/enrichment/comparison

Answer 246

1-6 Numeric matching

Answer 247

6-10 Exact matching

Answer 248

10-15 Fuzzy matching

Answer 249

Performs fuzzy matching on records, calculating a score between record pairs.

Answer 250

Performs an exact match between records.

Answer 251

Performs fuzzy matching between records, reporting on identical records only.

Answer 252

Removes duplicate records identified in the first step of the process.

Answer 253

Duplicate check

Answer 254

Duplicate Bean / Other Duplicate check

Answer 255

an underscore

Answer 256

a percentage sign

Answer 257

a question mark

Answer 258

a blank space

Answer 259

Email address

Answer 260

Phone number

Answer 261

Birth date

Answer 262

Address Line 1

Answer 263

'-' a hypher means ignore the field and never update

Answer 264

'0' a zero means only update the field if the account field has a null

Answer 265

'+' a plus means only update the field if the present value is not null

Answer 266

'++' a double-plus means always update the field

Answer 267

'-' a hypher means only update the field if the account field has a null

Answer 268

'0' a zero means ignore the field and never update

Answer 269

'0' a zero means only update the field if the present value is not null

Answer 270

'+' a plus means always update the field

Answer 271

'++' a double-plus means only update the field if the present value is not null

Answer 272

'++' a double-plus means only update the field if the account field has a null

Answer 273

Exact match

Answer 274

Numeric match

Answer 275

Fuzzy matching

	Criado por Scott Forrest mais de 6 anos atrás

Próximo

Cloud Data Management Specialist

Descrição

Resumo de Recurso

Questão 1

Questão 2

Questão 3

Questão 4

Questão 5

Questão 6

Questão 7

Questão 8

Questão 9

Questão 10

Questão 11

Questão 12

Questão 13

Questão 14

Questão 15

Questão 16

Questão 17

Questão 18

Questão 19

Questão 20

Questão 21

Questão 22

Questão 23

Questão 24

Questão 25

Questão 26

Questão 27

Questão 28

Questão 29

Questão 30

Questão 31

Questão 32

Questão 33

Questão 34

Questão 35

Questão 36

Questão 37

Questão 38

Questão 39

Questão 40

Questão 41

Questão 42

Questão 43

Questão 44

Questão 45

Questão 46

Questão 47

Questão 48

Questão 49

Questão 50

Questão 51

Questão 52

Questão 53

Questão 54

Questão 55

Questão 56

Questão 57

Questão 58

Questão 59

Questão 60

Questão 61

Questão 62

Questão 63

Questão 64

Questão 65

Questão 66

Questão 67

Questão 68

Questão 69

Questão 70

Questão 71

Questão 72

Questão 73

Questão 74

Questão 75

Questão 76