New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Public Sector Solutions Accredited Professional (AP-222) Exam - Topic 1 Question 17 Discussion

Actual exam question for Salesforce's Public Sector Solutions Accredited Professional (AP-222) exam
Question #: 17
Topic #: 1
[All Public Sector Solutions Accredited Professional (AP-222) Questions]

A Public Sector Organization (PSO) would like to enhance its publicly available website, built in Experience Cloud, to allow constituents to report their concerns about someone's health or safety. The PSO is already using Public Sector Solutions. The requirement from the PSO is that the constituent should be able to report their concerns both as authenticated users and anonymously. Additionally, internal staff should be able to separately track their investigations and any follow-up in a separate Case.

Leveraging Public Sector Solutions functionality, what configuration should the Technical Consultant use to meet the requirements?

Show Suggested Answer Hide Answer
Suggested Answer: C

For a Public Sector Organization enhancing its website to allow both authenticated and anonymous reporting of health or safety concerns, the appropriate configuration using Salesforce Public Sector Solutions would involve:

Using the Public Complaint and Case objects (Option C). Salesforce Public Sector Solutions includes specialized objects like Public Complaint, which is designed to handle situations where the public can report issues. These can be configured to allow anonymous entries while maintaining the capability to create and track related Cases for internal follow-up. This setup enables the organization to efficiently manage and segregate public inputs from internal case management processes.

Options A, B, and D do not fully address the requirements:

Option A and B involve using only the Case object or different record types on the Case object. While these configurations could segment reports internally, they do not cater specifically to the need for public input, particularly anonymous reporting.

Option D suggests creating a custom object for the Complaint with a lookup relationship to Case, which would require additional customization and might not leverage existing functionality as efficiently as using Public Complaint.


Contribute your Thoughts:

0/2000 characters
Beth
3 months ago
Wait, can they really report anonymously? That’s surprising!
upvoted 0 times
...
Lon
3 months ago
D could work, but creating a custom object seems like overkill.
upvoted 0 times
...
Dean
3 months ago
C sounds like a good fit, but I'm not sure about the Public Complaint object.
upvoted 0 times
...
Izetta
4 months ago
I disagree, B seems better for separating user types.
upvoted 0 times
...
Anissa
4 months ago
I think option A makes the most sense for tracking complaints.
upvoted 0 times
...
Reyes
4 months ago
I’m leaning towards the custom object option, but I worry about the complexity it might add to the system. I need to think more about the lookup relationship.
upvoted 0 times
...
Son
4 months ago
I practiced a similar question where we had to set up cases for different user types, and I feel like using the Case objects might be the way to go here.
upvoted 0 times
...
Tina
4 months ago
I think using record types on Case could help differentiate between authenticated users and anonymous reports, but I'm not entirely confident if that's the best approach.
upvoted 0 times
...
Jeanice
5 months ago
I remember we discussed the importance of using the right objects for tracking complaints, but I'm not sure if it's better to use the Complaint Case or the Public Complaint object.
upvoted 0 times
...
Dorethea
5 months ago
The record types on Case idea sounds promising. That way we can have one record type for constituents and another for internal staff to track the investigations and follow-up. I'll make sure to review the details on how to set that up.
upvoted 0 times
...
Dylan
5 months ago
Hmm, I'm not sure if the Complaint Case object is the right fit here. The requirement mentions that the constituents should be able to report concerns both as authenticated users and anonymously, so I'm thinking a custom object might be a better approach.
upvoted 0 times
...
Kara
5 months ago
This sounds like a pretty straightforward use case for the Public Sector Solutions functionality. I'd probably start by looking at the Complaint Case and Case objects to see if they can meet the requirements.
upvoted 0 times
...
Almeta
5 months ago
I'm a bit confused about the difference between the Complaint Case and Public Complaint objects. I'll need to dig into the documentation to understand which one would be the better fit for this scenario.
upvoted 0 times
...
Jeannetta
5 months ago
Hmm, this looks like a tricky one. I'll need to carefully read through the question and options to figure out the right control to use.
upvoted 0 times
...
Johanna
5 months ago
I'm a bit confused on the best way to compare strings in Solidity. I'll have to review the material again.
upvoted 0 times
...
Taryn
5 months ago
I'm uncertain about the special token usage, ${localname}. Is that really applicable for the CIFS server? Seems a bit off to me.
upvoted 0 times
...
Ricarda
5 months ago
Okay, I've got this. The key roles are HDFS components like NameNode and DataNode. I'll double-check the other options, but I'm confident I can nail this question.
upvoted 0 times
...
Peggie
2 years ago
What about D though? A custom object would give full control, especially fitting different configurations to the Case.
upvoted 0 times
...
Deandrea
2 years ago
Option A? Really? Using the generic Complaint Case and Case objects? Sounds like a recipe for a maintenance nightmare. Unless there's a compelling reason, I'd avoid that one and go with something more purpose-built.
upvoted 0 times
Myra
2 years ago
I think using record types on Case for different user types would be a better option.
upvoted 0 times
...
Aleshia
2 years ago
I agree, using the generic Complaint Case and Case objects could lead to maintenance issues.
upvoted 0 times
...
Alishia
2 years ago
D) Use a custom object for the Complaint with a lookup relationship to Case.
upvoted 0 times
...
Maryanne
2 years ago
B) Use record types on Case, one for the constituents and one for internal staff
upvoted 0 times
...
Yuki
2 years ago
I see your point, but using a custom object for the Complaint with a lookup relationship to Case could also work well.
upvoted 0 times
...
Frederic
2 years ago
I think using record types on Case would be a better option to differentiate between constituents and internal staff.
upvoted 0 times
...
Shenika
2 years ago
I agree, using the generic Complaint Case and Case objects could lead to maintenance issues.
upvoted 0 times
...
...
Kanisha
2 years ago
I’m leaning towards C. Public Complaint and Case objects sound made for this kind of public reporting system.
upvoted 0 times
...
Madalyn
2 years ago
I'm leaning towards option C. The Public Complaint and Case objects seem designed specifically for this kind of use case, so I'd expect them to provide the best out-of-the-box functionality. Plus, it's always nice when the solution aligns with the product's intended use.
upvoted 0 times
Katina
2 years ago
I agree, using the Public Complaint and Case objects seems like the most logical choice for this scenario.
upvoted 0 times
...
Erasmo
2 years ago
I think option C makes the most sense too. It seems like the most straightforward solution.
upvoted 0 times
...
...
Jacquline
2 years ago
Could be, but I prefer A. The Complaint Case and Case objects seem straightforward and aligned with Public Sector Solutions.
upvoted 0 times
...
Orville
2 years ago
I think the best answer is B. Using record types on Case could help distinguish between the constituents and internal staff.
upvoted 0 times
...
Lynda
2 years ago
Yes, making it available for both authenticated and anonymous users while tracking investigations separately. Not easy.
upvoted 0 times
...
Luz
2 years ago
Option D looks interesting. A custom object for the Complaint with a lookup to Case could give you more flexibility in how you structure and manage the data. Might be worth exploring further, though I'd want to understand the tradeoffs compared to the other options.
upvoted 0 times
Merilyn
2 years ago
D) Use a custom object for the Complaint with a lookup relationship to Case.
upvoted 0 times
...
Evangelina
2 years ago
D) Use a custom object for the Complaint with a lookup relationship to Case.
upvoted 0 times
...
...
Mayra
2 years ago
I think option B is the way to go. Using record types on the Case object allows you to differentiate between constituent and internal staff cases, while keeping everything in a single, centralized location. Seems like the most straightforward solution to me.
upvoted 0 times
Marge
2 years ago
Agreed, it's a straightforward solution that meets the requirements effectively.
upvoted 0 times
...
Erinn
2 years ago
I think it's a smart choice to keep everything centralized with record types on the Case object.
upvoted 0 times
...
Sherell
2 years ago
It's important to have a clear distinction between the two types of cases for better organization.
upvoted 0 times
...
Toi
2 years ago
Using record types on the Case object would make it easier to track and manage the cases.
upvoted 0 times
...
Jacquelyne
2 years ago
It definitely simplifies the process for both constituents and internal staff.
upvoted 0 times
...
Eden
2 years ago
I agree, option B seems like the most efficient way to handle this.
upvoted 0 times
...
...
Terrilyn
2 years ago
This question seems a bit tricky. Enhancing a website for health or safety concerns, right?
upvoted 0 times
...

Save Cancel