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

Pegasystems Exam PEGACPLSA88V1 Topic 3 Question 27 Discussion

Actual exam question for Pegasystems's PEGACPLSA88V1 exam
Question #: 27
Topic #: 3
[All PEGACPLSA88V1 Questions]

Case Type A and Case Type B capture information about multiple line items. Each line item is an Instance erf the same Line Item data type. Separate work pool classes are used for Case Types A and B.

What is the optimal data model design to meet these requirements?

Show Suggested Answer Hide Answer
Suggested Answer: D

Embedded List with Declare Index:

Both Case Types A and B possess an embedded list of line items. Using a Declare Index against each embedded list ensures efficient data retrieval and indexing.

Changing the direct inheritance class for each Declare Index class to the Line Item data type allows for proper data management and querying.

Reference:

Pega best practices for data modeling and indexing recommend using Declare Index for embedded lists to enhance performance and data organization.

Therefore, the correct answer is:

D . Case Types A and B both possess an embedded list of line items. Define a Declare Index against each embedded list. Change the direct inheritance class for each Declare Index class to the Line Item data type.


Contribute your Thoughts:

Martha
2 months ago
Haha, I bet the exam writers came up with these options just to mess with us. Who needs Case Type A and Case Type B when you can just have Case Type Chaos?
upvoted 0 times
...
Meghann
2 months ago
I prefer option C, it seems like the most efficient design.
upvoted 0 times
...
Cyndy
2 months ago
Option D is an interesting approach, but it might get messy if you have a large number of line items. Embedding the lists could make the data model more complex than necessary.
upvoted 0 times
Gretchen
14 days ago
Option D is an interesting approach, but it might get messy if you have a large number of line items. Embedding the lists could make the data model more complex than necessary.
upvoted 0 times
...
Nobuko
16 days ago
C) Add CaseTypeARef and CaseTypeBRef properties to the Line Item data type. The CaseTypeARef property is a case reference to Case Type A. The CaseTypeBRef property is a case reference to Case Type B.
upvoted 0 times
...
Bettina
17 days ago
B) Add a CsseTypeRef property, an ObjClass property, and Query property related to the Line Item data type. The Query property sources a Lookup Data Page that accepts ObjClass and CaseTypeRef parameters.
upvoted 0 times
...
Cristina
24 days ago
A) Add a CaseTypeRef property to the Line Item data type. Case Types A and B possess a Query (tisf Uneltem) property. This List Query property sources a D_UneltemList data page that accepts a pylD parameter.
upvoted 0 times
...
...
Jannette
2 months ago
You know, I'm surprised they didn't include an option for storing the line items in a NoSQL database. That would really throw a wrench in the works!
upvoted 0 times
Lai
25 days ago
C) Add CaseTypeARef and CaseTypeBRef properties to the Line Item data type. The CaseTypeARef property is a case reference to Case Type A. The CaseTypeBRef property is a case reference to Case Type B.
upvoted 0 times
...
Belen
1 months ago
B) Add a CsseTypeRef property, an ObjClass property, and Query property related to the Line Item data type. The Query property sources a Lookup Data Page that accepts ObjClass and CaseTypeRef parameters.
upvoted 0 times
...
Jacquelyne
1 months ago
A) Add a CaseTypeRef property to the Line Item data type. Case Types A and B possess a Query (tisf Uneltem) property. This List Query property sources a D_UneltemList data page that accepts a pylD parameter.
upvoted 0 times
...
...
Haydee
2 months ago
I disagree, I believe option B is more suitable.
upvoted 0 times
...
Noah
2 months ago
Option B seems the most logical choice. Having separate CaseTypeRef and ObjClass properties along with a Lookup Data Page that can accept both parameters sounds like a robust and flexible data model design.
upvoted 0 times
Portia
2 months ago
I prefer Option B as well, it offers more flexibility with the Lookup Data Page.
upvoted 0 times
...
Graciela
2 months ago
Option C might be simpler with separate CaseTypeARef and CaseTypeBRef properties.
upvoted 0 times
...
Emogene
2 months ago
I think Option A could also work well, with the List Query property sourcing a data page.
upvoted 0 times
...
Cordell
2 months ago
I agree, Option B does seem like the most logical choice.
upvoted 0 times
...
...
Pansy
2 months ago
I think option A is the best choice.
upvoted 0 times
...

Save Cancel