New Year Sale ! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam CRT-250 Topic 5 Question 38 Discussion

Actual exam question for Salesforce's CRT-250 exam
Question #: 38
Topic #: 5
[All CRT-250 Questions]

A Marketing Cloud admin at a bank is asked to avoid storing sensitive data in the

cloud. This data will only be sent to Marketing cloud to execute a send.

Which feature would the admin use to meet this requirement?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Dona
6 months ago
C) Field Level Encryption is the way to go, no doubt about it. Gotta keep that sensitive data locked down tight, you know? Unless you want your bank customers' info plastered all over the internet. Yikes!
upvoted 0 times
Vincenza
5 months ago
C) Field Level Encryption is the way to go, no doubt about it. Gotta keep that sensitive data locked down tight, you know? Unless you want your bank customers' info plastered all over the internet. Yikes!
upvoted 0 times
...
Vanda
5 months ago
A) Tokenized Sending
upvoted 0 times
...
...
Emmanuel
6 months ago
D) Distributed Marketing Sends? Sounds like a fancy feature, but I'm not sure how that helps with the sensitive data issue. I'd stick with C) to play it safe.
upvoted 0 times
Dolores
5 months ago
C) Field Level Encryption. That's a good choice, better safe than sorry.
upvoted 0 times
...
Junita
5 months ago
C) Field Level Encryption.
upvoted 0 times
...
Linn
5 months ago
B) List Sending
upvoted 0 times
...
Alease
5 months ago
C) Field Level Encryption.
upvoted 0 times
...
Melinda
6 months ago
A) Tokenized Sending
upvoted 0 times
...
Jesse
6 months ago
A) Tokenized Sending
upvoted 0 times
...
...
Leota
6 months ago
Yes, Tokenized Sending could be a good alternative to ensure data security.
upvoted 0 times
...
Roxane
6 months ago
I'm leaning towards A) Tokenized Sending. That way, the sensitive data never actually leaves the bank's systems, it's just a token that gets passed to Marketing Cloud. Keeps everything nice and secure.
upvoted 0 times
Eladia
6 months ago
Plus, it keeps everything compliant with regulations regarding sensitive data.
upvoted 0 times
...
Nobuko
6 months ago
Definitely, it's a smart way to handle the data without risking any security breaches.
upvoted 0 times
...
Sanjuana
6 months ago
I agree, A) Tokenized Sending sounds like the best option to keep the sensitive data secure.
upvoted 0 times
...
...
Kip
7 months ago
Hmm, I'm not sure. B) List Sending could work, but that might just be moving the problem, not solving it. I'd go with C) to be safe.
upvoted 0 times
Barabara
5 months ago
Yeah, I agree. It's better to be safe with sensitive data.
upvoted 0 times
...
Renea
6 months ago
Yeah, I agree. It's better to be safe with sensitive data.
upvoted 0 times
...
Trinidad
6 months ago
I think C) Field Level Encryption is the best option.
upvoted 0 times
...
Danica
6 months ago
I think C) Field Level Encryption is the best option.
upvoted 0 times
...
...
Nicolette
7 months ago
I think C) Field Level Encryption is the way to go here. Avoids storing sensitive data in the cloud, and still lets you execute the send. Seems like a no-brainer to me.
upvoted 0 times
Raina
7 months ago
Yes, it's a secure way to handle sensitive data without storing it in the cloud.
upvoted 0 times
...
Meaghan
7 months ago
I agree, C) Field Level Encryption is the best option for this scenario.
upvoted 0 times
...
...
Annelle
7 months ago
But wouldn't Tokenized Sending also be a good option to avoid storing sensitive data?
upvoted 0 times
...
Malinda
7 months ago
I agree, using Field Level Encryption would keep sensitive data secure.
upvoted 0 times
...
Bettyann
7 months ago
I think the admin should use Field Level Encryption to meet this requirement.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77