MENU
Northern Trail Outfitters runs a nightly automation consisting of a File Transfer and a File Import. Following an update from the engineering team, the automation began failing. The Marketing Cloud admin suspects the CSV file now has an invalid format.
How could the admin receive a file of the bad data rows to confirm this theory?
Suggested Answer: D
Get Premium Salesforce Certified Marketing Cloud Engagement Administrator (MCE-Admn-201) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
35 comments · newest first
MI
Mitzie
11 months ago
Not sure if just adding an email will help diagnose the issue.
LU
Lucy
11 months ago
Definitely need to separate the automations for clarity.
RA
Raul
12 months ago
Wait, can you really get bad data rows just by adding a notification?
SH
Shaquana
12 months ago
I think C could work too, but not as effectively.
RO
Royal
1 year ago
Option D seems like the best choice for catching those errors.
CE
Celia
1 year ago
I believe updating the Import definition to include a notification email could work, but I wonder if it would capture all the bad data rows effectively.
ME
Melodie
1 year ago
I'm a bit confused about whether the Import definition needs to be updated or if it should just be moved. I feel like I've seen similar questions before, but I can't recall the exact details.
RO
Rosita
1 year ago
I remember a practice question where we had to set up notifications for errors, so maybe option D is the best choice since it specifically mentions Runtime Errors.
YU
Yuriko
1 year ago
I think moving the File Transfer to its own automation could help isolate the issue, but I'm not sure if that would actually send the bad data rows.
LU
Luis
1 year ago
This is a tricky one. I'm tempted to go with option D and update the automation to include a notification email for runtime errors, but I'm not sure if that will give me the specific information I need about the bad data rows. I think I'll need to weigh the pros and cons of each choice.
LI
Lili
1 year ago
Okay, I've got an idea. If the issue is with the CSV file format, then moving the File Transfer to its own automation and including a notification email address seems like the best way to get the bad data rows. That way I can confirm the issue and then focus on fixing the file format.
EM
Emelda
1 year ago
Hmm, I'm a little unsure about this one. The question mentions a File Transfer and a File Import, but it's not clear to me where the bad data is coming from. I'll need to think through the different options carefully.
HE
Helene
1 year ago
This seems like a straightforward question about troubleshooting an automation issue. I think the key is to identify where the problem is occurring and how to get more information about the error.
FR
Francesco
1 year ago
I'm a bit unsure about this one. I know Milestones are used for tracking progress, but I'm not entirely sure which Object types support them. I'll have to think this through.
IV
Ivette
1 year ago
I'm a bit confused on this one. The question is asking about the earliest possible amendment date, but it's not clear to me how the previous amendment dates factor in. I'll need to re-read the question carefully.
DE
Delsie
1 year ago
I'm not sure I feel comfortable answering a question about cracking passwords. That seems like it could be unethical.
LA
Lakeesha
2 years ago
Option D is a little too broad. Updating the entire automation with a notification email might give you too much information to sift through. B is the winner here.
FA
Fabiola
1 year ago
Yeah, B is definitely the way to go in this situation. It will make it easier to identify and address the problem with the CSV file format.
HE
Herminia
1 year ago
I agree, B seems like the most efficient solution to receive the file of bad data rows for confirmation.
JO
Joye
1 year ago
I think B is the best option. Moving the Import definition to its own automation with a notification email address will help pinpoint the issue.
LE
Leontine
2 years ago
Haha, the admins must be pulling their hair out trying to figure this one out. I bet they wish they had a crystal ball to see the bad data!
ER
Erinn
1 year ago
C) Update the Import definition to include a notification email address
QU
Quentin
1 year ago
B) Move the Import definition to its own automation and include a notification email address
PA
Paris
1 year ago
A) Move the File Transfer to its own automation and include a notification email address
MA
Marjory
2 years ago
I agree with Gennie. Moving the Import definition to its own automation and including an email notification is the best way to get the bad data file.
CO
Corrina
1 year ago
D) Update the automation to include a notification email address for Runtime Errors
LU
Luann
1 year ago
C) Update the Import definition to include a notification email address
EL
Eliz
1 year ago
B) Move the Import definition to its own automation and include a notification email address
GE
German
2 years ago
A) Move the File Transfer to its own automation and include a notification email address
GE
Gennie
2 years ago
Option B makes the most sense. Separating the Import definition into its own automation and including a notification email address would allow the admin to get a report of any bad data rows.
LE
Lelia
1 year ago
That sounds like a good plan. It's important to quickly identify and address any issues with the CSV file format.
CR
Craig
1 year ago
Option B makes the most sense. Separating the Import definition into its own automation and including a notification email address would allow the admin to get a report of any bad data rows.
CA
Cammy
2 years ago
But wouldn't updating the Import definition to include a notification email address also be a good solution?
GR
Graham
2 years ago
I agree with Leonor. That way, they can easily identify the bad data rows and confirm the theory.
LE
Leonor
2 years ago
I think the admin should move the File Transfer to its own automation and include a notification email address.