050-6201-ARCHERASC01 Sample Questions Answers

Delete the subscription notification

Inactivate the subscription notification

Delete the application associated with the subscription notification

Disable notifications for the application associated with the subscription notification

A Security Parameter cannot be assigned by default

A user can only be assigned one Security Parameter

Only Application Owners can be assigned a Security Parameter

A user can be assigned up to three Security Parameters

Identifying owners for regulation-related controls

Clearly and consistently documenting corporate policies, including mapping those policies to industry regulations

Implementing a policy lifecycle maintenance process

Testing corporate controls to identify current gaps in compliance

Only Federal organizations should implement Public Sector

Any organization complying with NIST SP 800-53

Any organization with vendors

Any organization complying with SOX

Only fields that all users can see can be evaluated within a rule.

This is a non-issue, as only administrators are able to configure events.

If a user cannot interact with an evaluated field, he cannot trigger the action included in an event.

If a user cannot interact with all fields, he cannot save the record, and therefore, cannot trigger calculations.

Personal Reports can only be created by System Administrators, Application Owners, and Report Administrators

Personal Reports are the reports available on public Dashboards

Personal Reports are the only report type that can be emailed to a non-Archer user

Personal Reports can be created by anyone and are only accessible by the user who created them

It increases the complexity of key tasks

It eliminates the need to select relevant users individually

It eliminates the ability to synchronize with your LDAP server

It simplifies access control by enforcing the one-role, one-group rule

IP Address

Values List

Text Date

Platform Planning Guide

DDE Reconciliation Guide

What's New Guide

Platform Administration Guide

All fields in the records are included in all Notifications.

Only fields that have the Search results checkbox selected can be included in the notification email.

The fields specified in the Notification Template will appear, assuming the recipient has access to all included fields.

The end user has complete editing rights over the fields that will appear, so it is up to each user to define the included content.

The field will be calculated only when the record is initially created.

The field will be calculated only when there is a scheduled calculation.

The field will be calculated every time a user clicks "Save" or when there is a scheduled calculation.

The system will analyze the fields referenced by the calculation and determine when the field should be calculated.

A Dashboard can be accessed by a person who does not have an RSA Archer user account

The small windows that display reports and other items are called Dashboards

A Workspace can include one or more dashboards; dashboards can include one or more iViews

iViews can be displayed directly on a Workspace

The administrator should verity the user has been assigned a role that grants access to the application

The administrator should verify the user has been granted access rights to Private fields within the application

The administrator should confirm the user is named within a Record Permissions field within the application

The administrator should verify the user belongs to at least one group

FOIA

Gramm-Leach-Bliley Act

ADA

FISMA

Hourly, Daily, Weekly, Monthly

Daily, Weekly, Monthly Quarterly

Weekly, Monthly Quarterly Annually

Minutely, Hourly, Daily, Weekly

Baseline issues provide a basic understanding of business and IT infrastructure

Issues logged by a variety of groups provide a partial inventory of software applications, acting as a foundation for other inventories

Issues generated by several groups can be handled in Issues Management, including audit and risk and compliance

Issues Management helps to decentralize risk at a high level

The global report must be displayed in a Report iView the user has access to.

The user must have access to the application on which the global report was built.

There can be no private fields in the application on which the global report was built.

There can be no Record Permission fields in the application on which the global report was built.

They can delete a Solution.

They can add new user accounts to the platform.

They can see all records within their assigned applications.

They can see all records in all applications across the system.