A utility proposes dynamic scoping so newly discovered critical applications automatically enter GRC scope. Which capability does that approach rely on?
Select an answer to reveal the explanation.
Short Explanation
Dynamic scoping is the automatic sprinkler that turns on when a new critical app appears—not someone walking the yard with a watering can every Friday. Entity-type conditions watch the CMDB for “critical application” and pull matches into scope. That keeps GRC current without heroic manual adds.
Full Explanation
Entity types define a source table plus filter conditions that identify which records become entities. When conditions encode criticality or similar durable attributes, generation/refresh brings new qualifying CIs into scope automatically. That pattern supports dynamic scoping without hardcoding sys_ids or relying solely on quarterly spreadsheet imports. Manual-only maintenance cannot keep pace with discovery-driven CMDB growth.