Q: 7
You need to define the tables used for the non-conformity entity.
What should you use?
Options
Discussion
B, not C
Its B. This is where you define the main entity in Dynamics, not the details/history. Makes sense based on data structure here.
Probably B. The question says entity, so it's got to be the document table, not supplemental (that's more for line details). A is just a distractor about history.
That lines up for me, definitely B. Document table defines the entity itself, not just the history or lines.
Had something like this in a mock, went with B since document table is for the main entity.
B tbh
Honestly not 100% but I'd go for B here. The entity itself usually means document table in Dynamics setups, right? C feels more for lines/details. Correct me if I'm off.
I think it's C here. The supplemental table feels like the right choice for handling non-conformity since you sometimes need those extra lines. Maybe I'm missing something, but B seems more for documents, not this case. Agree?
My pick: it's B. In Dynamics, the document table is what you use to define and introduce the main entity like non-conformities. The others are more for details or history. I've seen similar logic in the official docs and some practice tests. Someone correct me if supplemental ever works for the core entity?
Option B makes more sense to me. The document table sets up the core entity definition, not just the history. A is a trap since document history is about tracking changes, not introducing the entity. If I’m misunderstanding the role of the supplemental table though, let me know.
Be respectful. No spam.
