Swift Certification Summary Alliance Access Administrator
Swift Certification Summary Alliance Access Administrator
Aim Individuals who pass this certification exam have a good knowledge of the administration of the latest
release of Alliance Access.
Content Upgrades and Updates
Security Functions
Gateway connectivity
Message partners
Routing
Monitoring
Target Audience Individuals who are Alliance Access Administrators or Alliance Security Officers in a Financial Institution
Recommended Study Deploy and Manage Solutions – Alliance Access Administrator – Associate
SWIFTS m a rt Curricul a’ s:
Deploy and Manage Solutions – Alliance Access Administrator – Professional
Experience At least six months of recent experience in an Alliance Access support role
Label the SWIFT components according to their Business data storage function
Identify the service, application and components needed to setup connections making use of FIN, InterAct, or FileAct protocol s
List the benefits of Alliance Access in terms of automation and easy integrat ion
Indicate where you can find an overview of the upgrade and installation path for Alliance Access software
List which other component of the SWIFT software stack, must usually be updated when there is an Alliance Access upgrade
Explain why the ‘MX Message Standards deployment package’ must be installed, when your institution uses an MX
message SWIFTNet service (e.g. SWIFTNet funds)
Describe the contents of the Alliance Bank File (sometimes referred to as the BIC File)
Explain the difference between an Alliance Bank file FULL and an Alliance Bank File DELTA
Select the two options you have to get the Alliance Bank Files (FULL or DELTA)
Select the three options (modes) used to upload the Alliance Bank File into Alliance Access
List the two critical contents of the Application Service Profile package
Security
List the factors of an Alliance Access Licence that influence the Initialisation & Master Passwords on the license
List at least one use of an Initialisation password (on an Alliance Access licence)
List at least one use of a Master password (on an Alliance Access licence)
Identify what entitlement or permission, left and right security officers (LSO and RSO) cannot assign to other operators
Explain the usage of permissions in an operator profile, specifically when it is expressed in the list values that are ‘Prohi bited’ or
‘Allowed’
List the two predefined operators that come with every Alliance Access installation
List the steps to create a new operator and enable the new user to use it
Explain at least two characteristics of the Authentication T ype: Password and TOTP
Explain the characteristics of the Authentication Type: RADIUS one time password
Recall at least four functional differences when using housekeeping mode compared to operational mode
Explain how both the normal user and admin user password policy is configured
Explain the purpose of the new security parameter ‘System – 4 eyes mechanism’
Explain what the SSL setting (in Gateway connection details); Data Encryption / Host Authentication means
Describe the resulting security features of implementing LAU between Alliance Access and Alliance Gateway
List the two components that you must stop in Alliance Access to add, modify, or delete a gateway connection
Describe what additional information you need to provide for a Test & Training Logical Terminal. (for example BANKHKH0A)
Explain the primary benefit of defining multiple Alliance Gateway Connections and adding them to a FIN Logical Terminal
Explain what is needed to exchange InterAct and FileAct messages through SWIFTNet
List the features that are provided by using input channels and input sequence numbers (ISN)
Recall at least one command to use with Alliance Remote Gateway (ARG)
Message Partners
Define at least one use of Message Partners in Alliance Access
Explain what is needed to exchange FileAct messages using the File transfer connection method
Recall the impacts of the 'Route' and 'Dispose' settings in a FROM Message Partner
Recall the configuration settings for a Direct FileAct FROM Message Partner
Compare the functionality of sending FileAct messages, using Direct FileAct to File Transfer
Routing
Explain the concept of a queue in Alliance Access
Explain in which queue you need to setup routing rules to route ACK and NAK messages back to a back-office application for
reconciliation
Explain what instance type in your routing action you need to select when you need to print out a hard -copy of a message before
sending it out to SWIFT
Describe the purpose of a routing schema
Describe IPLA
Message Searching and Reporting
Explain where you would go to find the messages (MT, MX or file) send and received
List the Wildcards that you can use when using Message Search criteria
Describe the result when you do not fill in any message search criteria
Explain where you would be able to see all the message interventions of a particular message and all its associated instances. (For
Example created, routed, sent to SWIFT, received from SWIFT, sent to a printer, etc.)
Explain what ‘Display expanded text’ does in the Test tab of the message details
List the kinds of reports you can get from Message Management
Explain why it is important to have all message instances of a day completed (in relation to archiving)
List where the different backup ‘tools’ available in the Access Configuration GUI (Graphical User Interface) can be found
Indicate if it is possible to use command line tools to create backups of the Alliance Access Database and message/event archives
Explain why it is important to backup and remove Event and Message archives in relation to disk space
Explain why it is important to have message and event archive backups on an external storage
List the options you have to start a restore of a message/event archive backup
Explain the difference between a partial database restore and a full database restore
Recall at least two Alliance Access user roles that can modify the System Configuration Parameters
Describe the Controlled Stop check box in the Scheduled Action Details popup of the Restart/Stop scheduling
Explain which Alliance Access Components need to be stopped when changing gateway details of a Logical Terminal and an
Emission Profile
Describe where you can find a description of the alarms that Alliance Access sends to an SNMP manager
Explain the options (All, Specific, None) of the Operators in the Distribution List details
Recall which System Configuration Parameter indicates which message structure of events to send to the local system log
Monitoring
Describe Alliance Access Monitoring
Explain what allows operators to easily focus on the situations which require their attention