Salesforce Exam Nonprofit Cloud Consultant Topic 4 Question 98 Discussion

Actual exam question for Salesforce's Nonprofit Cloud Consultant exam

Question #: 98
Topic #: 4

[All Nonprofit Cloud Consultant Questions]

A nonprofit using Salesforce configured with Person Accounts has recently installed NPSP into its org.

Which two configurations should a consultant set to ensure that Person Accounts and NPSP can coexist?

Choose 2 answers

AThe Household record type in NPSP Settings is different than the Person Accounts record type.

BCreate a validation rule to prevent the creation of Person Accounts.

CThe default record type for profiles of any user who converts leads is different than the Person Account record type.

DRemove permissions to Person Accounts for all profiles except System Admin.

Show Suggested Answer

Suggested Answer: A, C

To ensure that Person Accounts and NPSP can coexist within the same Salesforce org, follow these configurations:

Different Household Record Type in NPSP Settings:

Navigate to NPSP Settings.

Ensure that the Household record type specified in NPSP settings is different from the Person Account record type.

This prevents conflicts and ensures that NPSP correctly distinguishes between Household Accounts and Person Accounts.

Default Record Type for Profiles of Users Converting Leads:

Go to Setup > Profiles.

Ensure that the default record type for any profiles of users who convert leads is not set to the Person Account record type.

This ensures that when leads are converted, they do not automatically become Person Accounts, which could disrupt the NPSP data model.

By following these configurations, the nonprofit can effectively manage both Person Accounts and NPSP functionalities within the same Salesforce environment.

Salesforce NPSP Documentation: NPSP Configuration.

Salesforce Person Accounts Guide: Person Accounts.

by Margart at Sep 11, 2024, 07:45 PM

Limited Time Offer

25%

Off

Get Premium Nonprofit Cloud Consultant Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Tamera

2 months ago

Ah, the age-old battle between NPSP and Person Accounts. A and C are the winners here, folks. Gotta keep those record types in check!

upvoted 0 times

...

Almeta

2 months ago

Haha, B? Preventing Person Accounts altogether? That's like putting a Band-Aid on a bullet wound. A and C are the way to go, no doubt.

upvoted 0 times

Gilma

2 months ago

C) The default record type for profiles of any user who converts leads is different than the Person Account record type.

upvoted 0 times

...

Sharee

2 months ago

A) The Household record type in NPSP Settings is different than the Person Accounts record type.

upvoted 0 times

...

Katlyn

2 months ago

Ooh, a tricky one! But I reckon A and C are the right moves. Gotta keep those record types distinct, am I right?

upvoted 0 times

Geraldine

29 days ago

Exactly. A little configuration goes a long way in ensuring smooth operations.

upvoted 0 times

...

Rosalyn

1 months ago

Definitely. It's all about maintaining clarity and organization in the system.

upvoted 0 times

...

Rosio

2 months ago

Yeah, I agree. It's important to make sure they can coexist without any conflicts.

upvoted 0 times

...

Rima

2 months ago

I think A and C are the way to go. Keep those record types separate.

upvoted 0 times

...

Vilma

3 months ago

I think B and D are the correct choices because we need to prevent the creation of Person Accounts and restrict permissions.

upvoted 0 times

...

Yoko

3 months ago

But if we remove permissions to Person Accounts, won't that cause issues?

upvoted 0 times

...

Juliann

3 months ago

I disagree, I believe it should be C and D.

upvoted 0 times

...

Elvera

3 months ago

Removing permissions to Person Accounts for all profiles except System Admin? That's a bit extreme, don't you think? A and C are the more sensible choices here.

upvoted 0 times

Sue

2 months ago

Creating a validation rule can also help maintain data integrity when working with Person Accounts and NPSP.

upvoted 0 times

...

Lucille

2 months ago

It's important to ensure that the default record types align to avoid any conflicts.

upvoted 0 times

...

Kathryn

2 months ago

Yeah, removing permissions for all profiles except System Admin does seem extreme.

upvoted 0 times

...

Selma

2 months ago

Yeah, removing permissions for all profiles except System Admin does seem extreme. A and C make more sense for coexistence.

upvoted 0 times

...

Kiley

3 months ago

I agree, A and C seem like the best options for coexisting with Person Accounts and NPSP.

upvoted 0 times

...

Buffy

3 months ago

I agree, A and C seem like the better options to ensure compatibility between Person Accounts and NPSP.

upvoted 0 times

...

Mirta

3 months ago

Option A and C seem like the way to go. Keeping the record types separate is key for NPSP to work seamlessly with Person Accounts.

upvoted 0 times

Joaquin

2 months ago

C) The default record type for profiles of any user who converts leads is different than the Person Account record type.

upvoted 0 times

...

Kris

2 months ago

A) The Household record type in NPSP Settings is different than the Person Accounts record type.

upvoted 0 times

...

Ailene

2 months ago

C) The default record type for profiles of any user who converts leads is different than the Person Account record type.

upvoted 0 times

...

Devon

3 months ago

A) The Household record type in NPSP Settings is different than the Person Accounts record type.

upvoted 0 times

...

Yoko

3 months ago

I think we should choose A and C.

upvoted 0 times

...