MENU
You are creating an ERD that models the data for a college and includes a Many-to-Many relationship, Student-to-Class, where a student can be enrolled in multiple classes, and a class can enroll multiple students.
How can you handle this relationship so that it can be supported in Appian and remain in at least First Normal Form? (Choose the best answer.)
Suggested Answer: A
Get Premium ACD200 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
14 comments · newest first
AN
Andree
1 month ago
A is clear and straightforward. No confusion there.
CO
Corinne
1 month ago
D is not true. Appian can handle it with the right setup.
AN
Antonio
2 months ago
B and C seem inefficient. Arrays complicate queries.
MA
Mari
2 months ago
Agreed, A keeps it normalized. Easy to manage relationships.
LO
Loren
2 months ago
I think A is the best choice. Joining tables are standard for Many-to-Many.
JE
Jess
2 months ago
I thought Appian could handle this without a joining table?
PA
Pamela
2 months ago
Option A is the best choice, keeps it clean and normalized!
BL
Blair
2 months ago
Wait, can Appian really not handle Many-to-Many? That seems off.
TA
Tabetha
3 months ago
I disagree, arrays in fields just complicate things.
LE
Leatha
3 months ago
A joining table is definitely the way to go!
AN
Annamaria
3 months ago
I thought I heard that Appian can handle Many-to-Many relationships, so option D seems incorrect to me.
AN
Antonio
3 months ago
This question reminds me of a similar practice one we did about managing enrollments. I think the joining table option is definitely the best choice.
AR
Arthur
3 months ago
I'm not entirely sure, but I think storing arrays in the Student or Class tables might violate First Normal Form.
FA
Fairy
4 months ago
I remember we talked about using a joining table for Many-to-Many relationships in class. That seems like the right approach here.