Free Salesforce Marketing-Cloud-Administrator Practice Exam with Questions & Answers | Set: 2

Smart Capture is the feature that should be used to create a survey form. Smart Capture is a feature that allows marketers to create and insert forms within landing pages or emails, such as surveys, polls, or feedback requests. Smart Capture can be customized with different fields, labels, buttons, and actions. Smart Capture can capture subscriber responses and store them in a data extension or update existing records in Marketing Cloud.

 To link the new data extensions to the existing contact records, the subscriber ID value should be used. Subscriber ID is a unique identifier for each contact in Marketing Cloud and is automatically generated when a contact is created. It can be used to relate data extensions in Data Designer.

 Minimum password length is 12 characters and Once created, the user will need to be activated in order to use the SFTP are two considerations that should be taken when configuring an SFTP User. SFTP User is a type of user that allows marketers to securely transfer files between Marketing Cloud and an external location using Secure File Transfer Protocol (SFTP). SFTP User can be configured with different settings, such as username, password, folder access, and activation status. The password for an SFTP User must be at least 12 characters long and must meet certain complexity requirements. The user must also be activated before they can use the SFTP service.

To troubleshoot the issue with their sends, NTO can use the following links in Setup Home:

• Failed Sends3. This page shows the details of any sends that failed to complete due to errors or issues with the send definition or data extension3.
• System Status4. This page shows the current status and performance of Marketing Cloud and its features, such as Email Studio, Journey Builder, and Automation Studio4. The other options are not relevant for troubleshooting send issues because:
• Create Support Case5. This link allows NTO to create a case with Salesforce Support for any technical issues or questions they have with Marketing Cloud. However, this is not a direct way to troubleshoot their own send issues.
• Help and Training. This link allows NTO to access various resources and guides for learning and using Marketing Cloud. However, this is not a specific way to troubleshoot their own send issues.

 Microsite with Smart Capture to store entrants on a data extension is the correct component for capturing the contact information of the booth visitors. Smart Capture allows creating a form that can validate the entries and prevent duplicates. Data Extension with double opt-in status defined is the correct component for storing the entrants and their opt-in status. Double opt-in is a best practice for email marketing and ensures that the entrants have given their consent to receive the monthly newsletter.

The correct answer is A and D because Data Designer can be used to link data from different sources to the contact record, and Synchronized Data Sources can be used to bring data from Sales Cloud into Marketing Cloud. B is incorrect because Import Activity cannot import data from a Salesforce Report. C is incorrect because list attributes are not related to Sales Cloud data.

To avoid storing email addresses or phone numbers within Marketing Cloud, NTO should use Tokenized Sending2. Tokenized Sending is a feature that allows NTO to send emails or SMS messages using encrypted tokens instead of actual email addresses or phone numbers. The tokens are generated by an external system and stored in a secure database outside of Marketing Cloud. When NTO sends an email or SMS message, Marketing Cloud sends the token to the external system, which decrypts it and returns the actual email address or phone number. This way, NTO can avoid storing sensitive information in Marketing Cloud. The other options are incorrect because:

• Field Level Encryption. This is a feature that encrypts specific fields in data extensions using encryption keys managed by NTO. However, this feature does not prevent NTO from storing email addresses or phone numbers in Marketing Cloud; it only encrypts them within data extensions.
• Lookup reference to Contact Object. This is a method that allows NTO to use a lookup field in a data extension to reference a contact attribute from the Contact Object in Contact Builder. However, this method does not prevent NTO from storing email addresses or phone numbers in Marketing Cloud; it only reduces the duplication of data across data extensions.
• Master-detail relationship to Contacts. This is a type of relationship that allows NTO to link a data extension to the Contacts data model in Contact Builder. However, this type of relationship does not prevent NTO from storing email addresses or phone numbers in Marketing Cloud; it only enables them to use contact attributes for personalization and segmentation.

 The Collect Tracking code is a JavaScript code that is added to a website to capture and send user behavior data to Marketing Cloud. This data is stored in data extensions and can be used for Einstein Recommendations1

To correct the issue of not being designated as an integrated Marketing Cloud user, the admin should apply the administrator and Marketing Cloud Administrator permission sets to the user5. The administrator permission set grants the user access to all standard objects and settings in Sales Cloud, while the Marketing Cloud Administrator permission set grants the user access to Marketing Cloud Connect features and settings in Sales Cloud. These permission sets are required for completing the integration between Sales Cloud and Marketing Cloud. The other options are incorrect because:

• Apply the Marketing Cloud for AppExchange User option as well. This option will not correct the issue, as it only grants the user access to Marketing Cloud Connect features in Marketing Cloud, not in Sales Cloud. The user also needs access to Marketing Cloud Connect features in Sales Cloud to complete the integration5.
• Reset all passwords to force new tokens. This option will not correct the issue, as it only affects the authentication tokens for API users, not for integrated users. The user needs to be designated as an integrated user before they can use their credentials to log in to Marketing Cloud from Sales Cloud5.
• Apply the appropriate user mappings in the CRM configuration. This option will not correct the issue, as it only affects how users are mapped between Sales Cloud and Marketing Cloud based on their email addresses or usernames. The user needs to be designated as an integrated user before they can be mapped between the two systems5.

Custom roles are available on their Marketing Cloud account is what should be taken into consideration to accomplish this. Custom roles are roles that can be created and modified by Marketing Cloud administrators to grant specific permissions to users based on their business needs. Custom roles can be applied to users across all business units in an account or within a specific business unit