When we have a * wildcard entity configured in the File Type section with tightening enabled, the following may occur when requests are passed through the policy. Which is the most accurate statement?

Violations are still triggered with a wildcard and tightening enabled because the tightening mechanism relies on violations to identify file types that are candidates for explicit policy inclusion.

A wildcard (*) entry in the File Type section permits requests with any file extension to pass without being blocked, but when tightening is enabled the ASM system still generates violations for file types not explicitly defined. These violations populate the learning suggestions, allowing an administrator to review observed file types and selectively add them to the policy, progressively tightening it over time.

File type entities are not automatically added to the policy; an administrator must review and manually accept learning suggestions before any entity is added.

Violations are actively triggered when tightening is enabled - the wildcard prevents blocking but does not suppress violation logging or learning population.