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

GAQM CBAF-001 Exam - Topic 5 Question 11 Discussion

Actual exam question for GAQM's CBAF-001 exam
Question #: 11
Topic #: 5
[All CBAF-001 Questions]

A business analyst wishes to show that a company wants to store information about different types of product. Some attributes are common to every product (for example; product name) but other attributes only apply to certain product types. For example, product material only applies to accessory products. Which of the following constructs could the business analyst use to represent this on a class model?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

0/2000 characters
Gail
3 months ago
D is interesting, but I think it complicates things unnecessarily.
upvoted 0 times
...
Leontine
3 months ago
Wait, can you really use generalization for this? Seems off.
upvoted 0 times
...
Mozell
3 months ago
I thought an association class could work too.
upvoted 0 times
...
Trevor
3 months ago
Totally agree, generalization makes sense here!
upvoted 0 times
...
German
4 months ago
C is the best choice for this scenario.
upvoted 0 times
...
Kallie
4 months ago
The extend structure doesn't seem quite right for this scenario. That's usually used for optional functionality, not for modeling different product types with their own attributes. I'm going to go with the generalization approach.
upvoted 0 times
...
Kirk
4 months ago
I'm leaning towards the generalization structure as well. It seems like the cleanest way to model the common and specific attributes for the different product types. The association class could work, but might get a bit messy.
upvoted 0 times
...
Annice
4 months ago
The many-to-many multiplicity seems like it could work too, if the different product types have a many-to-many relationship with the common attributes. I'll have to think that one through a bit more.
upvoted 0 times
...
Horace
4 months ago
Hmm, I'm not sure about that. The question mentions that the attributes only apply to certain product types, so I'm thinking an association class might be a better fit to capture those relationships.
upvoted 0 times
...
Rodolfo
5 months ago
I think the generalization structure would be the best way to represent this. The common attributes can be in the parent class, and the specific attributes for each product type can be in the subclasses.
upvoted 0 times
...
Jacquelyne
5 months ago
I’m a bit confused about the extend structure; I thought it was more for optional features rather than core attributes.
upvoted 0 times
...
Michael
5 months ago
I feel like we practiced a question similar to this, and I think the generalization structure was the right choice then too.
upvoted 0 times
...
Mica
5 months ago
I'm not entirely sure, but I think an association class might be useful for linking attributes to specific product types.
upvoted 0 times
...
Lelia
5 months ago
I remember we discussed generalization structures in class, and they seem to fit well for representing common and specific attributes.
upvoted 0 times
...
Anthony
5 months ago
Based on the information provided, it seems like the content slot is set up properly and should render correctly. I don't see any obvious issues that would require additional action, so I'm leaning towards option A.
upvoted 0 times
...
Huey
5 months ago
This looks like a pretty straightforward configuration question. I think the key is to set up the account structure and advanced rules properly to meet the client's requirements.
upvoted 0 times
...
Deonna
5 months ago
Hmm, I'm a bit unsure about the differences between Power Automate, Business Process Modeler, and PowerApps. I'll need to review those options carefully to determine the best solution.
upvoted 0 times
...
Christiane
5 months ago
The key is remembering that testing identifies issues, while debugging fixes them. I think I've got a good handle on this, I'll mark my answer confidently.
upvoted 0 times
...

Save Cancel