Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Marketing Cloud Administrator Topic 4 Question 83 Discussion

Actual exam question for Salesforce's Marketing Cloud Administrator exam
Question #: 83
Topic #: 4
[All Marketing Cloud Administrator Questions]

To prevent retention of stagnant data, Northern Trail Outfitters wants any inactive data stored in data extensions to be cleared after 12 months.

What action should be taken?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Tom
1 months ago
I'm putting my money on D. Row-based retention is the way to go - it's like taking out the trash on a schedule instead of waiting for it to pile up.
upvoted 0 times
Jani
4 days ago
Definitely, it's like having a system in place to regularly clean up old data.
upvoted 0 times
...
Karma
5 days ago
I agree, setting retention at the row level ensures that each data extension is managed properly.
upvoted 0 times
...
Merilyn
13 days ago
I think D is the best option too. It's more efficient to set retention at the row level.
upvoted 0 times
...
Tonja
19 days ago
I agree, setting retention at the row level ensures that each data extension is managed properly.
upvoted 0 times
...
Yaeko
21 days ago
I think D is the best option too. It's more efficient to set retention at the row level.
upvoted 0 times
...
...
Stanton
2 months ago
Hmm, D seems like the way to go. I wonder if there's a way to set a global default retention policy instead of doing it manually on each data extension? That would be a real time-saver.
upvoted 0 times
...
Esteban
2 months ago
A and B sound like they'd affect the entire business unit or enterprise, which might be overkill for just this use case. D is the way to go.
upvoted 0 times
Adelina
19 days ago
D is definitely the best option for managing inactive data in this case.
upvoted 0 times
...
Lenna
20 days ago
It's important to have a specific retention setting for each data extension.
upvoted 0 times
...
Gregoria
1 months ago
D seems like the most targeted approach for clearing inactive data after 12 months.
upvoted 0 times
...
Long
1 months ago
I agree, A and B seem too broad for this specific situation.
upvoted 0 times
...
...
Delfina
2 months ago
I'd go with D. Applying the retention setting during data extension creation is a proactive approach, and it's less likely to be overlooked than manually configuring each one later.
upvoted 0 times
Edelmira
1 months ago
I think D is the most efficient option as well.
upvoted 0 times
...
Isadora
1 months ago
I agree, setting it during creation is the way to go.
upvoted 0 times
...
...
Gaston
2 months ago
I'm torn between C and D. C sounds good since the data is recoverable, but D might be easier to manage in the long run.
upvoted 0 times
...
Gerald
2 months ago
D seems like the most straightforward way to handle this requirement. Applying a row-based retention on each data extension ensures the inactive data is cleared consistently across the board.
upvoted 0 times
...
Emilio
2 months ago
I think option C) Set inactive data to be automatically cleared after one year, but is recoverable, strikes a good balance between data retention and manageability.
upvoted 0 times
...
Floyd
2 months ago
I disagree, I believe option D) Apply a Row Based Retention to each data extension as it is created, set to 12 months, is more efficient.
upvoted 0 times
...
Raymon
2 months ago
I think the best option is A) Configure the business unit data retention setting to 12 months.
upvoted 0 times
...

Save Cancel