An implementer creates one entity type with no table filter, so generation pulls every record from a very large table. What is wrong with that design?
Select an answer to reveal the explanation.
Short Explanation
An entity type without a filter is a fire hose aimed at your GRC database. Point at the table, yes—but add conditions like criticality or status so you get the population you meant. Unfiltered whole-table types drown the program in junk entities.
Full Explanation
The entity type approach combines a source table with filter conditions that define the intended population. Omitting conditions on a large table creates excessive, low-value entities and harms performance and ownership clarity. Meaningful predicates—business criticality, operational status, environment, or similar—constrain generation to what programs actually govern. Types are selectors, not bulk copy jobs.