An administrator imports a scan result from a third-party scanner and receives a warning that 'The scan result contains findings for URLs that are not in the policy'. The administrator wants to ensure that these findings are incorporated into the policy. What is the most appropriate action?

Ignore the warning because the findings are not relevant to the policy.

Change the policy's enforcement mode to 'Transparent' to allow all findings.

Create a new policy for the URLs and import the scan result there.

Add the URLs to the policy's enforcement scope and re-import the scan result.

An administrator uploads a scan result file from Acunetix into ASM, but the import fails with a 'File format not recognized' error. The file extension is .xml. What is the most likely cause of this error?

The administrator is not logged in with administrative privileges.

The ASM policy is in blocking mode, preventing the import.

The file size exceeds the maximum upload limit of 10 MB.

The XML file is not in the Acunetix-specific schema that ASM expects.

What is a common reason for a third-party scan result upload to fail in ASM?

The policy is in enforcement mode

The file is in an unsupported format

An administrator is importing a scan result file into ASM and wants to ensure that the import does not overwrite any existing policy configuration. What should the administrator do?

Import the file into a new policy and then copy the settings.

Disable the policy before importing.

Select the option to 'Merge' the imported findings with the existing policy.

Create a backup of the policy before importing.

How does ASM map imported third-party scan findings to its own entities?

By matching the port number to a service

By matching the IP address to a virtual server

By matching the severity to a policy

By matching the vulnerability name to an ASM signature

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

Domain 2Objective 5

Objective 2.05 Explain the Process to Integrate and Configure Natively Supported Third-Party Vendors and Generic Formats with ASM (e.g., Difference Between Scanning Modes, iCAP) 303 Practice Questions (Page 2)

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

18questions here

4free pages

4concepts

Questions 6–10

6expert · hard
An administrator imports a scan result from a third-party scanner and receives a warning that 'The scan result contains findings for URLs that are not in the policy'. The administrator wants to ensure that these findings are incorporated into the policy. What is the most appropriate action?
Select an answer first
7application · medium
An administrator uploads a scan result file from Acunetix into ASM, but the import fails with a 'File format not recognized' error. The file extension is .xml. What is the most likely cause of this error?
Select an answer first
8foundation · easy
What is a common reason for a third-party scan result upload to fail in ASM?
Select an answer first
9application · medium
An administrator is importing a scan result file into ASM and wants to ensure that the import does not overwrite any existing policy configuration. What should the administrator do?
Select an answer first
10foundation · easy
How does ASM map imported third-party scan findings to its own entities?
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.