Free Cheat-test Samples and Demo Questions Download
Adobe exams Adobe
Apple exams Apple
Avaya exams Avaya
Check Point exams Check Point
Cisco exams Cisco
Citrix exams Citrix
CIW exams CIW
CompTIA exams CompTIA
CWNP exams CWNP
EC-Council exams EC-Council
EMC exams EMC
Exin exams Exin
Fortinet exams Fortinet
GIAC exams GIAC
Hitachi exams Hitachi
HP exams HP
IBM exams IBM
Isaca exams Isaca
ISC exams ISC
ISEB exams ISEB
Juniper exams Juniper
LPI exams LPI
McAfee exams McAfee
Microsoft exams Microsoft
Oracle exams Oracle
PMI exams PMI
Riverbed exams Riverbed
SNIA exams SAP
Sun exams SAS
Symantec exams Symantec
VMware exams VMware
All certification exams

RSA 050-v61-SESECURID Exam - Cheat-Test.com

Free 050-v61-SESECURID Sample Questions:

Q: 1
How the RSA ACE/Server system does prevent login conflicts?
The RSA ACE/Server system uses remote aliases to prevent login conflicts.

Q: 2
What information the User Record consists of about an RSA SecurID Token holder?
Each user record can contain the following information about an RSA SecurID tokenholder (some of the information, such as the default shell, is optional):
. Name of the user
. Default login
. Default shell (when on a UNIX Agent Host other than AIX)
. If the user is a local user, the Token Type, whether the user authenticates with a passcode or just a tokencode, token status, and serial numbers of the user’s assigned tokens
. Administration authority level
. Whether or not the user can make up his or her own PINs
. Start and end dates of the period during which the user can be authenticated
. If the user is directly activated on one or more Agent Hosts, the times when the user can be authenticated on each Agent Host

Q: 3
Do the RSA ACE/Server supports exporting the RSA SecurID token records among different server installations?
Yes. The RSA ACE/Server export option enables you to move token records among different Server installations. By default, the export option creates a dump file (.dmp) of the token records. Optionally, you can export user information associated with the token.

Q: 4
What are the limitations of exporting the token records in ASCII format?
If you export token records in ASCII format, the user information is automatically exported, but the resulting file has the following limitations:
. The First Name field of the user record is not exported.
. Only the first 20 characters of the Last Name field are exported.
. Only the first eight characters of the default login are exported.
. The user’s shell information is not exported.

Q: 5
What kind of tokens cannot be exported in ASCII format?
You cannot export the following tokens to ASCII file format:
. Tokens set to authenticate with tokencode only
. AES tokens

Q: 6
How to use the RSA SecurID token records on another system?
To use the token records on another system, use one of the Export Token options on either the Token or the User menu. Then, use the Import Tokens option on the Token menu to import the records to another system.

Q: 7
How to assign the RSA SecurID tokens for active users after installing the RSA ACE/Server?
When you first install the RSA ACE/Server database it is empty, and the token records you received from RSA are unassigned. You must import the token records to the database and create a record for each authorized user before you can assign tokens to users.
The act of assigning a token to a user activates that user. A user is considered active if one or more tokens (or User Passwords) is assigned to him or her.
Every active user counts against the number of active users allowed by your license. that is, if you are licensed for 900 active users, you can assign up to three tokens (or User Passwords) to each of 900 users.

Q: 8
What are the limitations of assigning more RSA SecurID tokens to a user?
The more tokens a user is assigned, the longer it takes the Server to process that user’s authentication request because it tries to match the input against each of the user’s tokens in turn. If no match is found, the Server updates the bad login count for all of the user’s tokens, increasing the chance that the tokens might be disabled or put into Next Tokencode mode.

Q: 9
How to protect the software token XML files?
Use passwords to protect software token XML files. In addition, store all software token files in a secure directory on a secure machine.

Q: 10
How to enable if a software token is issued to the user?
When you issue a software token, it is automatically enabled and assigned to the selected user or group of users, and a corresponding record file is created.
During the issuing process, you can specify that the user authenticate with just a tokencode when using the software token. When the user authenticates, he or she enters 0000 followed by the resulting tokencode.
Once you issue the software token, you cannot change the authentication setting.


© 2014 Cheat-Test.com, All Rights Reserved