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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Exam Marketing Cloud Developer Topic 3 Question 80 Discussion

Actual exam question for Salesforce's Marketing Cloud Developer exam
Question #: 80
Topic #: 3
[All Marketing Cloud Developer Questions]

A developer is troubleshooting why a parent-level data extension cannot be accessed by a child business unit.

What should the developer check to validate the data available can be accessed for child business unit queries?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Maryrose at Sep 16, 2024, 04:15 PM

Limited Time Offer

25%

Off

Get Premium Marketing Cloud Developer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Charisse
7 months ago
I'm going with A. The ENT. prefix is key, and the Shared Data Extensions folder is where it's at.
upvoted 0 times
Kristel
5 months ago
User1: Makes sense, the structure needs to be set up correctly for the child business unit to query the data.
upvoted 0 times
...
Freeman
6 months ago
User2: Definitely, the data extension needs to be in the Shared Data Extensions folder for it to be accessible.
upvoted 0 times
...
Laticia
6 months ago
I agree, A is the correct option. The ENT. prefix is important for accessing data in child business units.
upvoted 0 times
...
...
Aron
7 months ago
I'm not sure about that. I think the data extension should be in the Shared Items root folder for the child business unit to access it.
upvoted 0 times
...
Gracie
7 months ago
I agree with Christiane. It's important for the data extension to be in the right folder for the child business unit to access it.
upvoted 0 times
...
Hyun
7 months ago
B is the way to go. Gotta love those Shared Items, they make life so much easier!
upvoted 0 times
Barrett
6 months ago
Definitely, it's important for smooth data access across units.
upvoted 0 times
...
Brianne
6 months ago
That's a good point, it ensures accessibility for all business units.
upvoted 0 times
...
Ryan
6 months ago
I always make sure my data extensions are in the Shared Items root folder.
upvoted 0 times
...
Merilyn
7 months ago
I agree, Shared Items definitely make things easier.
upvoted 0 times
...
...
Juliana
7 months ago
Hmm, I'm not sure. Maybe C? The data extension being in the Salesforce Data Extensions folder and accessible to the child business unit seems plausible.
upvoted 0 times
...
Christiane
7 months ago
I think the developer should check if the data extension is in the Shared Data Extensions folder and the query includes the ENT. prefix.
upvoted 0 times
...
Marylou
7 months ago
D sounds right to me. The data extension should be in the Synchronized Data Extensions folder and the query needs the ENT. prefix.
upvoted 0 times
Johnetta
6 months ago
D) The data extension is in the Synchronized Data Extensions folder and the query includes the ENT. prefix
upvoted 0 times
...
Mari
7 months ago
B) The data extension is in the Shared Items root folder and is accessible to the child business unit
upvoted 0 times
...
Royal
7 months ago
A) The data extension is in the Shared Data Extensions folder and the query includes the ENT. prefix
upvoted 0 times
...
...
Carey
7 months ago
I think the answer is B. The data extension needs to be in the Shared Items root folder and accessible to the child business unit.
upvoted 0 times
Alisha
6 months ago
D) The data extension is in the Synchronized Data Extensions folder and the query includes the ENT. prefix
upvoted 0 times
...
Brandon
7 months ago
C) The data extension is in the Salesforce Data Extensions folder and Is accessible to the child business unit
upvoted 0 times
...
Ahmad
7 months ago
B) The data extension is in the Shared Items root folder and is accessible to the child business unit
upvoted 0 times
...
Matthew
7 months ago
A) The data extension is in the Shared Data Extensions folder and the query includes the ENT. prefix
upvoted 0 times
...
...

Save Cancel