Objective 2.01 Determine the Appropriate Criteria for Initial Policy Definition Based on Application Requirements (e.g., Wildcards, Violations, Entities, Signatures, User-Defined Signatures) 303 Practice Questions (Page 3)

Questions 11–14

1. 11foundation · easy

   What is the purpose of using wildcards in an ASM policy definition?

   • ATo bypass security checks for certain users
   • BTo enable automatic signature updates
   • CTo block all traffic from unknown IP addresses
   • DTo match a range of URLs or parameters that share a common pattern
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   What is the purpose of a user-defined signature in an ASM policy?

   • ATo detect threats that are not covered by the default signature set
   • BTo improve the performance of the ASM
   • CTo allow the application to bypass security checks
   • DTo replace the default signature set
   Reveal Solution Discussion Select an answer first
4. 13foundation · easy

   When initially defining an ASM policy for a new web application, which application requirement is most important to identify first?

   • AThe number of users expected to access the application simultaneously
   • BThe IP addresses of all potential attackers
   • CThe brand and model of the web server hardware
   • DThe application's expected user interactions and functionality
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   A company is deploying BIG-IP ASM to protect a legacy PHP application that handles employee timesheet submissions. The application uses a single URL (/submit.php) with a form that posts employee ID, hours worked, and a date. The security team wants to minimize false positives while ensuring the form is protected. The application has no other endpoints. Which initial policy definition approach best meets these requirements?

   • ACreate a policy that explicitly defines /submit.php as a URL, adds the three parameters as entities, and enables signatures relevant to PHP and SQL injection.
   • BCreate a policy with only the /submit.php URL entity and leave all signature settings at their default (disabled) state to avoid any false positives.
   • CCreate a policy with a wildcard URL (*) and enable all signature sets to catch any attack on any endpoint.
   • DCreate a policy with a wildcard URL (*) and enable only the SQL injection signature set, since the form posts data to a database.
   Reveal Solution Discussion Select an answer first