This functionality provides a simple way to build criteria once, which can be reused in other platform areas.

• A.Conditions
• B.Filte Group
• C.Favorites
• D.Filters

Comment: *

Name: *

Email: *

Verification: *

The components Installed with Vulnerability Response Include:

• A.Business Rules, Roles, Workflows
• B.Ul Pages. Business Rules, Vulnerability Scanners
• C.Properties, Client Scripts, Wizards
• D.Tables, Scheduled Jobs, Security Operations Common

Comment: *

Name: *

Email: *

Verification: *

To ensure that Vulnerabilities are processed correctly, you can define a Service Level Agreement (SLA) for Vulnerability Response. To achieve this you would:

• A.Create a custom workflow to monitor the time between States
• B.Log in as a system admin, and using the globally scoped baseline SLA Modules
• C.Have the role of Vulnerability admin, but only in the Vulnerability Scope
• D.Make sure you have at least the sn_vul.vulnerability_write role and using the baseline SLA Application Modules

Comment: *

Name: *

Email: *

Verification: *

Filter Groups provide a way to:

• A.Reuse criteria in a variety of places
• B.Build criteria once
• C.All of the above
• D.Decouple the use of the grouping from the definition of the grouping

Comment: *

Name: *

Email: *

Verification: *

What is the ID associated with the Vulnerability Response plugin?

• A.com.snc.security_incident
• B.com.snc.threat.intelligence
• C.com.snc.threat.feeds
• D.com.snc.vulnerability

Comment: *

Name: *

Email: *

Verification: *