A financial services company hosts an online banking portal. The compliance team requires that all requests containing SQL injection attempts be blocked, but they also want to minimize false positives for legitimate users. The ASM policy currently enforces the 'SQL injection' violation in blocking mode. After a week, the security team notices that some legitimate requests with the word 'select' in a text field are being blocked. What should the security team do to reduce false positives while still meeting the compliance requirement?

Disable the 'SQL injection' violation for the text field and enable it for all other parameters.

Add a security policy exception for the specific text field that contains the word 'select'.

Refine the SQL injection signature set to be more specific and reduce false positives.

Change the 'SQL injection' violation to alarming mode and rely on the log to identify attacks.

Which ASM violation type is triggered when a request contains a parameter value that does not match the expected data type defined in the security policy?

Parameter value length exceeded

Parameter value does not match data type

A security policy aims to prevent SQL injection attacks. Which ASM violation type is most directly relevant to this objective?

Parameter value length exceeded

An ASM policy is blocking many legitimate requests because it enforces strict data type checks on a parameter that sometimes contains alphanumeric values. What is the most likely issue with the current violation enforcement?

The violation is not relevant to the application

The violation is causing excessive false positives

The violation is not enforced at all

The violation is configured to alert only

An ASM policy is not blocking any requests, but the security team expects some violations to be blocked. What is the most likely reason for this?

The violations are configured to alert only

The violations are not relevant to the application

The violations are not being detected

F5Certified Technology Specialist, BIG-IP ASM (F5-CTS, BIG-IP ASM)

Domain 2Objective 6

Objective 2.06 Determine Whether the Rules Are Being Implemented Effectively and Appropriately to Mitigate the Violations 303 Practice Questions (Page 1)

Part of the Section 2: Create and customize policies domain, which makes up ~27% of our current practice bank.

11questions here

3free pages

4concepts

Questions 1–5

1application · medium
A financial services company hosts an online banking portal. The compliance team requires that all requests containing SQL injection attempts be blocked, but they also want to minimize false positives for legitimate users. The ASM policy currently enforces the 'SQL injection' violation in blocking mode. After a week, the security team notices that some legitimate requests with the word 'select' in a text field are being blocked. What should the security team do to reduce false positives while still meeting the compliance requirement?
Select an answer first
2foundation · easy
Which ASM violation type is triggered when a request contains a parameter value that does not match the expected data type defined in the security policy?
Select an answer first
3foundation · easy
A security policy aims to prevent SQL injection attacks. Which ASM violation type is most directly relevant to this objective?
Select an answer first
4foundation · easy
An ASM policy is blocking many legitimate requests because it enforces strict data type checks on a parameter that sometimes contains alphanumeric values. What is the most likely issue with the current violation enforcement?
Select an answer first
5foundation · easy
An ASM policy is not blocking any requests, but the security team expects some violations to be blocked. What is the most likely reason for this?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to 303

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by F5. “303” is a trademark of its owner, used for identification only.