CC360: Out of the box, Cloud MDM cleanses and standardizes data in which Salesforce objects?
Accounts
Products
Contacts
Leads
CC360: What does 'Consolidation' mean in Cloud Customer 360?
The process of taking data from multiple sources to create a 'golden record'.
The process of merging two or more duplicate records.
CC360: The Cloud MDM hierarchies feature allows you to represent various relationships with your customers.
CC360: The Cloud MDM application has components that run inside Salesforce, as well as components that run outside of Salesforce.
CC360: Running Cloud MDM using the default settings is recommended.
CC360: The following statements regarding the Cloud MDM custom settings are true:
Changing the settings is only required for advanced operations.
The settings should be configured before running Cloud MDM jobs.
The settings are present but not visible after installation.
CC360: The default Cloud MDM profile that is assigned to all users is called:
Admin
Default
User
CC360: Which fields should be added to the Cloud MDM Information section on a page layout?
Synchronize
Company Norm
Record Type
Country ISO Code
CC360: The Master Beans related list should be added to the Contact page layout (for the data steward/admin user).
CC360: Field sets allow you to:
Select which fields to display on a Visual Force page.
Control which fields are compared when searching for duplicates.
CC360: When an account records is synchronized to the Cloud MDM staging area, the following records are created:
Java Bean
Account Bean
Contact Bean
Master Bean
CC360: The process of running synchronization on all records of a particular object type is known as:
Migration
Synchronization
Standardization
CC360: The following statements regarding the Synchronize flag are true:
For newly created records, the value will be true.
For existing records in Salesforce the value will be false.
Allows the movement of a record to and from the Cloud MDM staging area.
Can be used to synchronize a subset of data.
CC360: Which settings determine the field mappings between the transactional record and the bean?
Matching settings
Bean settings
Synchronization settings
CC360: How many custom fields can be mapped to a bean?
20
5
10
CC360: Data cleansing ensures that data is in a consistent format, which is important for:
Hierarchies
Quality of reports
Improving matching results
CC360: When does Cloud MDM cleanse the data?
When Cloud MDM is installed.
When a record is synchronized.
When a data steward clicks the 'Cleanse' button.
CC360: Cloud MDM looks for a legal form at the beginning and end of an account name.
CC360: The normalized company name is used to update the Name on the account record.
CC360: The normalized Country name is used to update the Country on the Account, Lead or Contact record.
CC360: Cloud MDM uses fuzzy matching for the following processes:
Identifying duplicate records.
Matching records from external data sources to accounts.
Grouping records with similar characteristics.
Matching leads/contacts to accounts.
CC360: Fuzzy matching is a two-step process. In step 1, Cloud MDM:
Performs a fuzzy match on all included fields.
Performs a fuzzy match on the segments.
Performs an exact match on the segments.
CC360: The following statements are true regarding data segmentation:
Slows down the fuzzy matching process.
Determines which records will be fuzzy matched.
Speeds up the fuzzy matching process.
Reduces the total number of records being fuzzy matched.
CC360: The segment component fields must be fields on the bean, not the transactional record.
CC360: You can control the fuzzy matching by setting the following:
Null scores
Field order
Field weighting
Threshold values
CC360: In which settings do you set fuzzy matching options?
Duplicate settings
CC360: If the fuzzy match score for a field is 40 and the field weighting is set to 25, what will the total field score be?
25
CC360: If you set a field's weighting to 200, the values of this field must be an exact match or...
The total score will be set to 0 and the records will not be considered a match.
The weighted score for that field will be doubled.
A score of 0 is assigned to that field.
CC360: When you run the Duplicate Check job, Cloud MDM compares:
All master beans in the same segment.
All account records in the Salesforce org.
All account records in the same segment.
CC360: When you run the Duplicate Contact Check job, Cloud MDM compares:
Contact to Lead beans in the same segment.
All Contact beans in the same segment.
Account and Contact beans in the same segment.
All Lead beans in the same segment.
CC360: You should increase the number of processes when running the Duplicate Check jobs if your org contains more than 1000 records.
CC360: In order to view a list of MDM-identified potential duplicates for an account, you must:
Assign a Cloud MDM profile to your user.
Be the Salesforce administrator.
Add the Duplicate Accounts VisualForce page to the Account page layout.
CC360: What 3 things should you do before using the automated merge jobs?
Identify and mark any 'no duplicate' pairs.
Toggle the master record where necessary.
Use Salesforce side-by-side comparison to examine each duplicate pair.
Analyze duplicate records using reports and side-by-side comparisons.
CC360: To create powerful duplicate reports, you should create a custom report type that:
Groups records by the master.
Is only available to data stewards and administrators.
Pulls in data from the related master and detail Account, Contact or Lead.
CC360: What controls the display of the Toggle Master, No Duplicate and Merge buttons on the Duplicates VisualForce page?
The Salesforce page layout.
The Cloud MDM Profile of the user.
The default Salesforce profile of the user.
CC360: With the Cloud MDM Merge jobs, you can merge up to 1000 records at a time.
CC360: With Cloud MDM's enhanced lead conversion functionality, when a lead (for which a contact already exists) is converted, the following happens:
The lead will not convert.
The lead is converted and the existing contact is updated.
The existing contact is automatically deleted, then the lead is converted.
CC360: What new fields can be added to the Lead Detail page with Cloud MDM?
Lead Parent
Contact (lookup)
Master Account
Account (lookup)
CC360: In order to use the Cloud MDM lead functionality, leads must be 'matched' to accounts. Which 2 things facilitate this?
Matching threshold for Account.
Matching settings for Account and Contact.
Batch Acceleration Level for Matching job.
Segment settings for Account and Contact.
CC360: Which approach should you use for performing a one-time load of data (e.g. migration from existing system to Salesforce)?
Integrate to Staging Area (Beans).
Integrate directly to Account object.
CC360: What should you do before loading external data into beans?
Create a Data Source.
You should load data before doing any setup.
Perform Duplicate Check.
CC360: Matching can be defined as:
The process of associating leads and contacts to accounts.
The process of associating records of the same object class.
The process of associating beans to master beans.
The process of associating data from an external source with an account.
CC360: If external data is loaded directly into beans and matching is run, how does Cloud MDM handle beans that were not matched to master beans (i.e. net new accounts)?
The bean is associated with a global master bean.
The bean is flagged as 'No Match'.
A new master bean is created.
CC360: Which is true regarding the Consolidated View?
Shows data currently on account.
Shows data currently on master bean.
Shows historical data for account.
Lists data sources for the master bean.
CC360: Enrichment can be defined as the process of writing data from the account to the master bean.
CC360: Which enrichment operator will only update a field if that field's present value is NULL?
+
-
++
0
CC360: You don't need to run the consolidation job if you are not integrating data from external systems.
CC360: Multi-dimensional hierarchies means that a single account can belong to more than one hierarchy type - e.g. a Sales and Financial hierarchy.
CC360: What is another name for an account in a hierarchy?
Entity
Level
Node
Branch
CC360: In order to view hierarchies using the MDM functionality, which configuration steps must you complete?
Configure field sets for Account search and results.
Ensure the Parent ID field is mapped in the Account Synchronization settings.
Add the Parent ID field to the Master Bean page layout.
Add the Hierarchies VisualForce page to the Account page layout.
CC360: In which ways can hierarchies be built?
Cloud MDM's graphical hierarchy editor.
Via the master beans.
The native Salesforce Parent field.
Imported from an external system.
CC360: What happens if you add an account (that already belongs to a hierarchy) to another hierarchy?
The account, along with any children, will be moved to the new hierarchy.
The account will be copied and assigned a unique name.
The account will be added to both hierarchies.
CC360: How can you change the hierarchy type?
Navigate to the Account bean for the ultimate parent and edit the Hierarchy Type field.
Edit the Hierarchy Type field on the Account that is the ultimate parent.
Navigate to the Master bean for the ultimate parent and edit the Hierarchy Type field.
CC360: In order to clone a node, you can use the Cloud MDM edit hierarchies interface.
CC360: If you clone an account into another hierarchy type, what happens behind the scenes?
A second bean with source equal to the other is created and associated with the master bean for the account.
The second bean with source equal to the account is created under the master bean.
A second bean is created and associated with the account.
CC360: Select two valid approaches for loading hierarchy data from an external data source.
Load data then manually update the Parent ID fields.
Load data in order - parent accounts, then child accounts, etc
Load data in first job, then create parent relationships in second job.
Populate the Parent ID field and load all data in a single job.
DaaS - AddressDoctor Cloud: Which input file format is supported with the Data Quality Centre?
Delimited plain text files
Word document
Binary document
Fixed-width
Excel document
DaaS - AddressDoctor Cloud: What is the maximum file size that can be uploaded to the Data Quality Centre?
50Mb
100Mb
1Gb
500Mb
DaaS - AddressDoctor Cloud: Does the Data Quality Center support de-duplication functionality?
Yes
No
DaaS - AddressDoctor Cloud: Incorrect address field assignments might result in which of the below status codes?
P1
C2
I3
P2
All of these.
DaaS - AddressDoctor Cloud: What versions of Excel are supported?
2010
2003
2013
2007
DaaS - AddressDoctor Cloud: Which enrichment's are supported?
NCOA (National Change of Address)
Geocoding
Deceased Check
DaaS - AddressDoctor Cloud: Which Address Doctor return status codes indicate a 50% or greater chance of an address being undeliverable?
C4
I2
DaaS - AddressDoctor Cloud: Which of the following Salesforce modules are supported with Address Validation?
Opportunities
DaaS - AddressDoctor Cloud: What is the maximum character length for a password?
DaaS - AddressDoctor Cloud: A country must be specified in order to verify an address.
DaaS - Email Verification: The biggest benefit to verifying email addresses at point of collection is to increase your list size by ensuring valid emails at acquisition point.
DaaS - Email Verification: What is the shortest recommended timeout, in seconds?
8
15
DaaS - Email Verification: It is recommended to prompt customers for invalids in the following situation(s)?
Any time your main objective is to collect email addresses.
Any time an email is collected for transactional messages, such as e-receipts, order confirmations and shipping notifications.
Any time a customer service representative is verbally asking for a customer's email address and typing it in.
All of these options.
DaaS - Email Verification: At what point in the process are real-time verification emails verified?
Point of collection
2 days later
1 week later
DaaS - Email Verification: An example of a hygiene code is:
200 Email Valid
220 Analytics in Progress
Safe to Send
300 Email Not Valid
Emails with the code 220 Analytics in Progress are safe to send from a hygiene perspective.
DaaS - Email Verification: Which of the following is NOT a reason you receive an 'Analytics in Progress' status?
The target email domain is a 'Grey List' server.
The email is invalid.
The timeout value you have specified is too short for the specified domain.
All are correct.
DaaS - Email Verification: The GetReason code for 'Server Actively Rejected' has a code of:
300
206
200
225
DaaS - Email Verification: A 'Net Protected' domain uses a third party service or appliance to filter and detect spam email.
DaaS - Email Verification: The standard input and output file for an automated batch job is:
XML
HTML
CSV
DaaS - Email Verification: The email address field does not have to be present in input filing.
DaaS - Email Verification: What is the max length of characters that an email address can have?
100
500
250
DaaS - Email Verification: When you receive a hygiene result of 'Mole' this means:
These emails are based internationally and are safe.
The email addresses are not directly owned or controlled by a 3rd party DNSBL site.
3rd party oversight emails specifically used for monitoring resources, many times for deliverability monitoring.
DaaS - Email Verification: Before installing the product you must obtain a StrikeIron subscription for Email Verification Plus Hygiene.
DaaS - Email Verification: What is the highest number a timeout can be set to, in seconds?
30
120
90
80
DaaS - Email Verification: What can you set the schedule type to when creating new batch jobs?
Monthly
Never
Both of these
Neither of these
DaaS - Email Verification: You can only select lists for automatic verification on demand.
DaaS - Email Verification: Bronto improves customer contactability by:
33%
50%
75%
90%+
DaaS - Email Verification: The app is free for Bronto users who have purchased a subscription to StrikeIron Email Verification Plus Hygiene.
DaaS - Email Verification: The Informatica tool will verify the email address, mailing address and phone numbers instantly before the invalid contact record is stored in the CRM system.
DaaS - Email Verification: What is the default email verification timeout, in seconds?
60
DaaS - Email Verification: On the batch job result page, you can sort out the list order by:
Status description
Field name
DaaS - Email Verification: What are the 4 steps (in order) to integrate StrikeIron's Email Verification and Hygiene API into Marketo?
Configure Webhook, create form, create Smart Campaign, test landing page
Create Webhook, create Smart Campaign, create form, test landing page
Create form, test landing page, create Webhook, create Smart Campaign
DaaS - Email Verification: What is the purpose of the question mark in the middle of the actual REST call?
It separates the endpoint of the API from the parameters that are supplied.
It tells customer that they need to edit the REST information.
To make customers confused.
DaaS - Email Verification: The parameters that must be included in webhook template are:
Message
Licence key
Neither of these.
DaaS - Email Verification: Before you map the Response Mappings, it is recommended that you create how many new fields?
2
3
DaaS -SMS Mobile Messaging: Messages can be sent to non-mobile numbers.
DaaS -SMS Mobile Messaging: Consent is required to send SMS messages.
DaaS -SMS Mobile Messaging: What type of consent is required to send SMS messages?
Oral
Written
Both
DaaS -SMS Mobile Messaging: The frequency of you sending SMS messages to your customer base does not matter after you have consent.
DaaS -SMS Mobile Messaging: An opt-out option is required.
DaaS -SMS Mobile Messaging: What are the 4 types of Compliance Messages?
Welcome, opt in, help, stop
Opt in, stop, help, unknown
Welcome, opt in, help, unknown
Welcome, stop, help, unknown
DaaS -SMS Mobile Messaging: Is bulk SMS possible?
DaaS -SMS Mobile Messaging: Can we push HTTPs address?
DaaS -SMS Mobile Messaging: Messages cannot be customized when using a trial account.
DaaS -SMS Mobile Messaging: How many messages are tracked in a single TrackMessageBulk invocation?
1000
50
DaaS -SMS Mobile Messaging: What does the getstatuscode 200 mean?
Issue
Not found
Found
None of the above
DaaS -SMS Mobile Messaging: The syntax used by StrikeIron to describe the contents of SMS messages.
XLS
SQL
DaaS -SMS Mobile Messaging: What is the first thing you need to do in creating a Marketo Integration?
Create Campaign
Create response mapping
Create a secondary webhook
DaaS -SMS Mobile Messaging: What request type do you use in the webhook?
Pre
Post
DaaS -SMS Mobile Messaging: What are the 4 steps involved in a Marketo Integration and in what order?
Smart campaign, Webhook, form, test landing page
Webhook, form, smart campaign, test landing page
Form, Webhook, smart campaign, test landing page
Test landing page, Webhook, form, smart campaign
DaaS -SMS Mobile Messaging: What 3 parameters need to be included in the template?
Account ID, to number, message txt
License key, from number, message txt
License key, to number, header txt
License key, to number, message txt
DaaS - Email Verification: Select all of the key benefits to email verification and hygiene.
Improve email campaign performance with better deliverability
Minimize risks associated with bad list hygiene
Enhance customer loyalty and satisfaction
DaaS - Email Verification: What are the risks associated with bad email list hygiene?
Wasting your marketing budget by sending to bad email addresses.
Sending to a trap/spam email, resulting as being blacklisted as a spam sender.
Reaching customers with no interest in your products or services.
DaaS - Email Verification: When/Where can email verification and hygiene be used?
Webforms and landing pages
E-commerce websites (e.g. at checkout or newsletter sign-up)
Preference centres
Point of sale (in-store email acquisition and e-receipts)
List acquisition
CRM and marketing databases
Call centres
DaaS - Email Verification: What are the types of email verification and hygiene implementation?
Real-time - verified at point of collection or when data is synchronized with the CRM system / marketing database.
Batch - one off verification or as part of a routine back-end process
End-point - verifying successfully sent emails
DaaS - Email Verification: What are the three output data points of the email verification process?
Status codes, Reason codes, Hygiene results
Progress codes, Reason codes, Hygiene codes
Status codes, Hygiene codes, Recipient type codes
DaaS - Email Verification: Select all of the correct status codes provided by email verification.
300 Email Valid
210 Domain Confirmed
420 Analytics in Progress
250 Email Valid, Potentially Dangerous
250 Domain Confirmed, Potentially Dangerous
270 Analytics in Progress, Potentially Dangerous
410 Not Verified
310 Not Verified
DaaS - Email Verification: Select all of the correct status codes provided by email verification which indicate a problem or potential problem with an email address.
250 Email Valid, Potentiall Dangerous
260 Domain Confirmed, Potentially Dangerous
310 Not Verfied
400 Not Verified
DaaS - Email Verification: What is the purpose of the output Reason Codes in the email verification process?
To provide further insight into the Status Codes, particularly in the case of Analytics in Progress or failure codes.
To tell you when an email has been automatically sent to a customer's spam/junk mail folder.
To highlight invalid email address formats.
DaaS - Email Verification: What is the best practice approach to email verification?
Place email validation at the end of the inputs form, so that all information is available.
Place the email validation at the start of the input form and give a 'Verify' button to the user.
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.
DaaS - Email Verification: A target email is set to reject the 1st send from an address, then after a given timeout permit a second send attempt to reach the desired inbox. This is known as:
Black listing
Grey listnig
White listing
Red listing
DaaS - Email Verification: The standard input for a batch email verification job is:
.csv file with mandatory email address column
.txt file with mandatory email address column
.csv file with mandatory email address and id columns
.txt file with mandatory email address and id columns
DaaS - Email Verification: The standard output file format of email verification is:
.csv
.txt
.bat
DaaS - SMS Mobile Messaging: What is the status code for Not Found?
DaaS - SMS Mobile Messaging: What is the status code for Internal Error?
DaaS - SMS Mobile Messaging: What is the status code for Invalid Method Name?
400
CC360: Which Migration jobs are available in the CC360 console?
Migrate Hierarchy
Migrate Accounts
Migrate Contacts
Migrate Leads
Migrate Products
Migrate Opportunities
CC360: Migration jobs pick up all records with the synchronize flag = FALSE.
CC360: If the synchronize flag is set to TRUE then the record is NOT in the CC360 beans staging area yet.
CC360: Which type of comparison is used in bean custom fields 1 and 2?
Numeric
Fuzzy
Numeric (Fuzzy if non-numeric)
Exact match
CC360: Which type of comparison is used in bean custom fields 3 and 4?
CC360: Which type of comparison is used in bean custom fields 5 and 6?
CC360: Which type of comparisons are used in in bean custom fields?
3-4 Fuzzy matching
5-6 Exact match
1-5 Numeric matching
1-2 Numeric matching
16-20 used for consolidation/enrichment/comparison
7-20 used for consolidation/enrichment/comparison
1-6 used for consolidation/enrichment/comparison
1-6 Numeric matching
6-10 Exact matching
10-15 Fuzzy matching
CC360: Legal form normalization can only look at the last word in the company name.
CC360: By default CC360 includes common legal entity names for which of the following countries?
UK
USA
Germany
France
Japan
CC360: Fuzzy matching is a two-step process. In step 2, Cloud MDM:
Performs fuzzy matching on records, calculating a score between record pairs.
Performs an exact match between records.
Performs fuzzy matching between records, reporting on identical records only.
Removes duplicate records identified in the first step of the process.
CC360: The default master bean segment is 'Country ISO Code || Company Norm' with all spaced removed.
CC360: The batch acceleration level is the number of characters in the segment used for record grouping.
CC360: For which of the following processes can the batch acceleration level be set separately?
Duplicate check
Duplicate Bean / Other Duplicate check
Matching
CC360: When a segment field is blank, the position(s) in the segment will be replaced with:
an underscore
a percentage sign
a question mark
a zero
a blank space
CC360: For which fields is exact matching used?
Email address
Phone number
Birth date
City
Address Line 1
Title
Surname
CC360: How many concurrent APEX processes can CC360 run?
1
CC360: There is no rollback functionality for a merge job.
CC360: Which of the following enrichment operators are correct?
'-' a hypher means ignore the field and never update
'0' a zero means only update the field if the account field has a null
'+' a plus means only update the field if the present value is not null
'++' a double-plus means always update the field
'-' a hypher means only update the field if the account field has a null
'0' a zero means ignore the field and never update
'0' a zero means only update the field if the present value is not null
'+' a plus means always update the field
'++' a double-plus means only update the field if the present value is not null
'++' a double-plus means only update the field if the account field has a null
CC360: When searching for records to add to a hierarchy the following search modes are available:
Numeric match
Fuzzy matching
And
Or
Contains
CC360: As default, when updating hierarchies of <500 nodes the updates are done synchronously.
CC360: Hierarchy synchronous update limits can be set via the maximum trigger hierarchy limit setting.
CC360: What is the default hierarchy batch size limit?
2000
5000
CC360: The default maximum number of nodes in a hierarchy is called the 'maximum hierarchy limit' and is set to 45,000. Although there is no technical limit.
