[&] Which scripting vulnerability is most often tested when bypassing client-side filters?
- Cross-Site Scripting (XSS)
- SQL Injection
- Cross-Site Request Forgery (CSRF)
- Command Injection

[&] What is a primary reason why client-side filters can be easily bypassed?
- Client-side filters are usually written in simple HTML.
- Client-side filters process data in a way that requires no reverse engineering.
- Client-side filters are only applied after data reaches the server.
- Client-side filters are not as secure as server-side filters.

[&] What is an effective method to bypass client-side filters in a web application?
- Use bug bounty platforms
- Use a different user interface
- Disable JavaScript
- Modify server-side scripts

[&] Why is it important to understand regular expressions (regex) when bypassing client-side filters?
- Regex is used to format browser cookies, not for filtering.
- Regular expressions are only used to enhance the performance of web applications.
- Regular expressions are only used on the server-side for filtering.
- Regex filtering is a common technique on both client-side and server-side.

[&] Why might Regex 101 be a useful tool for security testers?
- It is an alternative tool for penetration testing instead of using Kali Linux
- It provides comprehensive security certifications
- It automatically bypasses all known client-side filters
- It explains and tests regular expressions used in filters

[&] What tool can be used to view and alter client-side filtering behavior?
- SQLmap
- Metasploit
- Wireshark
- Burp Suite