Q: 8
Which metric will identify edit checks that may not be working properly?
Options
Discussion
Option A is the way to go. If an edit check never fires (count is zero), or triggers unexpectedly a ton, you know the logic could be broken. D looks similar, but it averages across checks and might hide individual problem checks. Pretty sure from exam reports-happy to hear another view if you disagree.
Why not C here? Discrepancies identified per form could show data issues but wouldn't help trace back to a specific edit check that's not firing. A feels like the only metric that links back directly to the actual edit check working or failing, right?
Its D. Had something like this in a mock, average per check firing felt like what they wanted for edit check performance.
Totally makes sense to use A for this. Counting each edit check separately is the best way to catch if one isn’t firing at all or too much, which points to a config issue. Pretty sure that’s how they expect you to flag broken checks.
A makes sense to me. If you track how many times each edit check fires, you can spot if something isn't working-like zero triggers for a required check or way too many for one that's misbehaving. I think that's the most direct way to flag broken logic. Anyone see it differently?
Doesn't D just average the firings, which could hide if one edit check is broken?
D might look tempting but it spreads the count too thin, which could mask a broken check. A is better since it lets you spot if a specific edit check never triggers or fires too often, pointing to a logic issue. Pretty sure that's what they want for finding faulty edit checks.
A imo
Probably A. Official guides and some practice exams focus on individual check counts for finding broken logic in edit checks.
Nah, not D. The average per edit check (D) might hide when a single check totally fails, since the rest could balance it out. Counting the number of times each specific edit check fires (A) highlights checks that aren't working at all. Seen this emphasized in practice questions.
Be respectful. No spam.