Salesforce Updated Marketing-Cloud-Administrator Exam Questions and Answers by monroe

The Einstein STO activity allows the journey to send five different versions of an initial welcome email to new subscribers at the optimal time for each subscriber. This activity requires only one email and one activity, whereas the Join activity would require five emails and five activities.

Synchronized Data Sources is the feature that would allow this functionality. Synchronized Data Sources are data sources that allow marketers to import and synchronize data from Salesforce CRM objects into Marketing Cloud data extensions. Synchronized Data Sources can be configured with different settings, such as sync frequency, field mapping, and filter criteria. Synchronized Data Sources enable marketers to use Sales Cloud data in their queries and other Marketing Cloud activities.

To resolve the issue of the encrypted file being decrypted after the File Transfer Activity completes, the decrypted data would be in the original SFTP folder. The File Transfer Activity can be configured to decrypt an encrypted file using a decryption key provided by NTO. The decrypted file will be placed in the same location as the encrypted file on the SFTP site. The other options are incorrect because:

• Selected SFTP folder. This is not where the decrypted data would be after the File Transfer Activity completes, as the File Transfer Activity does not allow NTO to select a different SFTP folder for the decrypted file. The decrypted file will be placed in the same location as the encrypted file on the SFTP site.
• Target Data Extension. This is not where the decrypted data would be after the File Transfer Activity completes, as the File Transfer Activity does not import data into a data extension. The File Transfer Activity only moves files from one location to another, such as from an FTP site to the Safehouse or from the Safehouse to a data extension. To import data into a data extension, NTO needs to use an Import File Activity.
• Safehouse. This is not where the decrypted data would be after the File Transfer Activity completes, as the File Transfer Activity does not move files to the Safehouse when decrypting them. The File Transfer Activity only moves files to the Safehouse when encrypting them or when transferring them from an external FTP site to Marketing Cloud. The Safehouse is a temporary storage location within Marketing Cloud that can be used for staging files before importing them into a data extension.

 The two fields that would need minimal consideration for size/scalability related reasons when creating a data extension to house the data are:

• Number. This is a field type that stores numeric values in a data extension. A number field can store up to 18 digits before the decimal point and up to 2 digits after the decimal point5. A number field has a fixed size of 8 bytes regardless of the number of digits stored in it. Therefore, a number field would need minimal consideration for size/scalability related reasons when creating a data extension.
• Boolean. This is a field type that stores logical values in a data extension. A boolean field can store only two possible values: true or false5. A boolean field has a fixed size of 1 byte regardless of the value stored in it. Therefore, a boolean field would need minimal consideration for size/scalability related reasons when creating a data extension. The other options are incorrect because:
• Text. This is a field type that stores alphanumeric values in a data extension. A text field can store up to 4000 characters per value5. A text field has a variable size depending on the number of characters stored in it; each character takes up 1 byte of space. Therefore, a text field would need considerable consideration for size/scalability related reasons when creating a data extension.
• Decimal. This is a field type that stores numeric values with decimal precision in a data extension. A decimal field can store up to 28 digits before the decimal point and up to 10 digits after the decimal point5. A decimal field has a variable size depending on the number of digits stored in it; each digit takes up 0.5 bytes of space. Therefore, a decimal field would need considerable consideration for size/scalability related reasons when creating a data extension.