In runtime access tracking, what are the available options for script operations?

In runtime access tracking, what are the available options for script operations?

• A. none, tracking, enforcing
• B. allow, block, audit
• C. enabled, disabled, pending
• D. on, off, auto

Answer: (A)

Runtime access tracking controls how script operations are handled at run time. The three modes are none, tracking, and enforcing. None means no runtime checks or logs—scripts run without monitoring. Tracking logs attempts to perform restricted actions so you can see what would happen without blocking anything. Enforcing actively blocks disallowed operations to enforce security policies. Starting with tracking lets you observe script behavior and build an audit trail, then you can switch to enforcing to enforce protections once you’re confident in what scripts are doing. The other option sets describe different concepts (policy language like allow/block/audit; generic statuses like enabled/disabled/pending; or generic on/off/auto) and don’t correspond to the specific runtime access behavior modes.

Runtime access tracking controls how script operations are handled at run time. The three modes are none, tracking, and enforcing. None means no runtime checks or logs—scripts run without monitoring. Tracking logs attempts to perform restricted actions so you can see what would happen without blocking anything. Enforcing actively blocks disallowed operations to enforce security policies.

Starting with tracking lets you observe script behavior and build an audit trail, then you can switch to enforcing to enforce protections once you’re confident in what scripts are doing. The other option sets describe different concepts (policy language like allow/block/audit; generic statuses like enabled/disabled/pending; or generic on/off/auto) and don’t correspond to the specific runtime access behavior modes.