Salesforce Certified Education Cloud Consultant (ED-Con-101) Exam - Topic 6 Question 67 Discussion

Actual exam question for Salesforce's Salesforce Certified Education Cloud Consultant (ED-Con-101) exam

Question #: 67
Topic #: 6

[All Salesforce Certified Education Cloud Consultant (ED-Con-101) Questions]

During the requirements gathering phase, the academic staff stated that students are independent of any Account or Company. The staff requested that the Contact's Account field be blank and hidden on the page layout.

What is the impact of creating a Contact without a parent Account?

AContacts are private only to the record owner, and inaccessible to other users.

BContacts are at risk of ownership data skew, which may result in performance issues.

CContacts will require manually creating a related Affiliation record to enable sharing, adding more complexity.

DContacts are public to all users, potentially sharing sensitive data.

Show Suggested Answer

Suggested Answer: A

by Judy at Apr 23, 2023, 01:27 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified Education Cloud Consultant (ED-Con-101) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Merlyn

4 months ago

Hiding the Account field might lead to confusion later on.

upvoted 0 times

...

Vincenza

4 months ago

I think ownership issues could be a big problem too.

upvoted 0 times

...

Nelida

4 months ago

Wait, are they really public to all users? That seems risky.

upvoted 0 times

...

Tandra

4 months ago

I agree, it adds unnecessary complexity!

upvoted 0 times

...

Magdalene

4 months ago

Contacts without an Account can be tricky.

upvoted 0 times

...

Nu

5 months ago

I vaguely recall that having no Account could lead to performance issues, so option B could be relevant, but I'm not entirely sure how that connects to ownership data skew.

upvoted 0 times

...

Vicente

5 months ago

I'm a bit confused about the implications of not having a parent Account. I thought it might make Contacts private, but I'm not certain if that's what option A is saying.

upvoted 0 times

...

Latonia

5 months ago

I think we practiced a similar question where we talked about ownership and sharing rules. I feel like option C might be the right answer since it mentions needing an Affiliation record.

upvoted 0 times

...

Maryanne

5 months ago

I remember discussing how creating a Contact without an Account could lead to issues with data visibility, but I'm not sure which option reflects that best.

upvoted 0 times

...

Deeanna

5 months ago

I'm pretty confident that the answer is A, Checkpointing and Write-ahead Logs. That's the approach I've learned about in the course materials, and it makes sense for Structured Streaming to use those techniques to ensure reliable processing.

upvoted 0 times

...

Mozell

5 months ago

I'm a bit unsure about the process, but I'll give it my best shot.

upvoted 0 times

...

Precious

5 months ago

This one seems pretty straightforward. I'm pretty sure the answer is B, Rainbow table.

upvoted 0 times

...

Coletta

5 months ago

Hmm, I'm a bit unsure about the relationship between business architecture and solution architecture. I'll need to think this through carefully.

upvoted 0 times

...

Mari

5 months ago

Okay, I've got this. The question is asking about resolving a name resolution issue, and the solution provided is to modify the name servers at the domain registrar. That makes sense to me, so I'll go with that.

upvoted 0 times

...

Raymon

9 months ago

Haha, imagine if the solution was to just leave the Contact's Account field blank and hidden. That would be like a big 'out of sight, out of mind' kind of deal. Not exactly the most practical approach, is it?

upvoted 0 times

Fausto

8 months ago

User 3: Maybe there's a better way to handle this situation without compromising data security.

upvoted 0 times

...

Jerilyn

9 months ago

User 2: I agree, it could lead to some data integrity issues down the line.

upvoted 0 times

...

France

9 months ago

User 1: Yeah, that does seem like a strange request from the academic staff.

upvoted 0 times

...

Charisse

10 months ago

D is definitely not the answer. Exposing sensitive student data to all users is a huge security risk and goes against the requirements. Good thing that's not the case here!

upvoted 0 times

Reta

9 months ago

C) Contacts will require manually creating a related Affiliation record to enable sharing, adding more complexity.

upvoted 0 times

...

Mignon

9 months ago

B) Contacts are at risk of ownership data skew, which may result in performance issues.

upvoted 0 times

...

Tamra

9 months ago

A) Contacts are private only to the record owner, and inaccessible to other users.

upvoted 0 times

...

Penney

10 months ago

I'm leaning towards B. Contacts without a parent Account could lead to data skew and performance issues down the line. The academic staff may want to reconsider this requirement.

upvoted 0 times

Stephen

9 months ago

It's important to address potential issues early on in the requirements gathering phase.

upvoted 0 times

...

Deja

9 months ago

Maybe the academic staff should consider the implications of not having a parent Account for Contacts.

upvoted 0 times

...

Erasmo

10 months ago

I agree, data skew can definitely cause performance issues.

upvoted 0 times

...

Johana

10 months ago

But wouldn't manually creating a related Affiliation record add more complexity to the process?

upvoted 0 times

...

Norah

11 months ago

Option C seems to be the right choice here. Creating a separate Affiliation record is definitely more complex, but it aligns with the requirement of keeping students independent from any Account or Company.

upvoted 0 times