An SELinux security context is required to ensure that all files in /opt have the default context of system_u:object_r:usr_t. How should the corresponding configuration entry be formatted?

This format places the context before the path and uses a shell glob `*` instead of a regular expression, which is incorrect for SELinux file context configuration.

SELinux file context configuration entries, typically found in files like `file_contexts` or configured with `semanage fcontext`, use regular expressions to match file paths followed by the security context. The pattern `/opt/.*` (or more precisely `^/opt(/.*)?$`) correctly matches the `/opt` directory and all its contents, and the format `path_regexp context` is standard.

This option uses a shell glob `*` instead of a regular expression, which is not how SELinux file contexts are defined in configuration files.

This format places the context before the path, includes an extra colon after the context, and uses a regular expression that doesn't fully match the common pattern for `/opt` and its contents.

This format places the context before the path, which is incorrect for common SELinux file context configuration files like `file_contexts` where the path regexp comes first.