Test
FIX II Quiz
Este test tiene tiempo límite, así que se abre en el reproductor de siempre.
Preguntas del test (63)
1Batch processing is implemented in which moxy version?
- A6.0
- B7.3
- C5.2
- D8.0
2How many executions can FIX handle per second?
- A15,000
- B30,000
- C45,000
- D50,000
3To be able to write messages to the FIX log, FIX.NET needs which system credential?
- AWindows Administrator Account
- BPower User - Windows Account
- CLocal System - Windows Account
- DDomain Administrator
4In order to access the FIXNET database, FIX.NET service needs permission to recover the DatabaseConnectionString which is located in:
- AODBC
- BWindows Registry
- CSolution Forge folder
5Select all the details the DatabaseConnectionString from SolutionForge registry key contains:
- ADatabase name
- BWindows User
- CSQL User
- DUser's password
- EServer name
6Which tables are consulted in order to read tags and parse FIX messages before they are stored in the RX_MESSAGE_STORE table?
- AFIX_FIELDS
- BFIX_TAGS
- CFIX_MESSAGE_BLOCKS
- DFIX_MESSAGEBLOCK
7All messages are stored in the RX_MESSAGE_STORE table, except heartbeats.
- AVerdadero
- BFalso
8To be able to store heartbeats, what should be installed?
- AFIXNET Service
- BMxFixNetServices
- CRTM Service
9Which column in the FIX_MESSAGES table should be set to value = 1 to make sure heartbeats are being stored?
- APERSIST_MESSAGE_RX
- BPERSIST_MSG_TX
- CPERSIST_MSG_RX
- DPERSIST_HEARTBEAT_RX
10FIX.NET service tracks the state of each open session with each provider in which table?
- AFIX_CONNECTION_STATE
- BFIX_SESSIONS
- CMoxyFIXConnection
- DFIX_SESSION_STATE
11MxFIXNETServices installation ties the FIX.NET service to which two objects?
- Acomadptr.dll
- BRTM service
- CMxSrvcs.dll
- DADVS.MxFIXInboundProcessor
12The ADVS.MxFIXInboundProcessor is a COM+ object that lives within the comadptr.dll.
- AVerdadero
- BFalso
13Which tables are checked to know which Moxy database to deliver fills?
- AMxSrvcsFIXConnection
- BFIX_SESSIONS
- CMoxyFIXConnection
- DMxSrvcsDatabase
14Which of the following are parameters passed by the pMxFIXInPutMessage sproc to Moxy?
- ASender and Target CompIDs
- BFIX Version
- CFIX Message String
- DFIX Connection Name
- ESequence Number
- FFIX Message Type
15The sproc pMxFIXInPutMessage kicks off the following actions and procedures:
1. Increment the [blank_start]LastRxMsgSeqNum[blank_end] in MoxyFIXConnectionData table when it gets a heartbeat or any FIX message that Moxy's not interested in
2. Trigger [blank_start]replay[blank_end] of FIX Messages from FIXNET if Moxy's sequence number is behind, calling a sproc that puts an [blank_start]Event 91[blank_end] into the RTM Event Queue
3. Check to see how many times it should request a replay by looking at [blank_start]MaxReXmit[blank_end]
4. Detect [blank_start]duplicate[blank_end] FIX message by noticing if the FIX sequence number is lower than the Moxy sequence number
5. Log the fact that the new message was successfully received in the [blank_start]Moxy Event Log[blank_end]
6. Increment the Moxy [blank_start]sequence number[blank_end] after each successfully processed message
7. Call upon the [blank_start]pMxFIXPutMessageStaging[blank_end] sproc to actually process the incoming message- ALastRxMsgSeqNum
- Breplay
- CEvent 91
- DMaxReXmit
- Eduplicate
- FMoxy Event Log
- Gsequence number
- HpMxFIXPutMessageStaging
16The pMxFIXPutMessageStaging sproc will:
1. Parse the [blank_start]FIX message[blank_end] out, separate all the tags and verify that execution actually applies to an actual Moxy order/FIX place
2. Insert the [blank_start]acknowledgement[blank_end] messages in the [blank_start]MoxyFIXExtMessage[blank_end] where a trigger fires to put an [blank_start]Event 72[blank_end] in the RTM Event Queue
3. Insert every [blank_start]acknowledgement[blank_end] and every [blank_start]fill[blank_end] in to the MoxyFIXExtMessage table
4. Trigger a stored procedure [blank_start]_pMxFIXGenRTMFillEvent[blank_end] to insert an Event 72 into RTM Event Queue- AFIX message
- Backnowledgement
- CMoxyFIXExtMessage
- DEvent 72
- Eacknowledgement
- Ffill
- G_pMxFIXGenRTMFillEvent
17Both the pMxFIXPutMessageStaging and pMxFIXInPutMessage sprocs won't be executed if the RTM service is not started.
- AVerdadero
- BFalso
18The FIX Inbound Processor through triggering the pMxFIXInputMessage sproc inserts new events into the RTM Event Queue but if the RTM service is not running, these events will simple sit forever in the queue and will never be processed.
- AVerdadero
- BFalso
19Sender and Target CompID values are contained in which tags?
- ATags 49 and 65
- BTags 34 and 56
- CTags 49 and 56
20Sender and Target CompIDs are stored in which table?
- AMoxyFIXConnection
- BMoxyFIXExtMessage
- CMxSrvcsFIXConnection
21The MoxyFIXExtMessage table is basically like the RX_MESSAGE_STORE table in the FIXNET database since it also stores heartbeats.
- AVerdadero
- BFalso
22Messages that Moxy cannot process successfully are also stored in the MoxyFIXExtMessage table.
- AVerdadero
- BFalso
23Acknowledgements like all execution reports have a value of Tag 35=8 with the addition of having:
- ATag 39 = 1
- BTag 93 = 1
- CTag 39 = 0
- DTag 39 =2
24RTM Event Queue Status:
-3 = [blank_start]Retry[blank_end]
-2 = [blank_start]On the Bubble[blank_end]
-1 = [blank_start]Failure[blank_end]
0 = [blank_start]Unprocessed[blank_end]
1 = [blank_start]Success[blank_end]- ARetry
- BOn the Bubble
- CFailure
- DUnprocessed
- ESuccess
25Select all the correct statements regarding the ExecTime and ExecType in the MoxyRTMEventQueue
- AExecType = 0 means process immediately
- BExecType = 1 means periodic event with its periodicity set by the TickInterval column
- CExecType =2 means periodic event with its periodicity set by the TickInterval column
- DExecType = 1 means scheduled event that would be processed at the time specified in TickInterval
- EExecType = 1 means scheduled event that would be processed at the time specified in ExecTime
26RTM Events:
Event ID - Event Name
51 - [blank_start]FIX SEND Order[blank_end]
52 - [blank_start]FIX Replace Order[blank_end]
53 - [blank_start]FIX Cancel Order[blank_end]
54 - FIX Request Order Status
55 - [blank_start]FIX Send DK Trade[blank_end]
56 - FIX Send Reject
72 = [blank_start]FIX Recv Message[blank_end]
73 - FIX Recv State Change
81 - FIX Connect
82 - FIX Disconnect
83 - [blank_start]FIX EOD[blank_end]
91 - FIX Request Retransmit RX Messages- AFIX SEND Order
- BFIX Replace Order
- CFIX Replace Order
- DFIX Request Order Status
- EFIX Cancel Order
- FFIX Send Reject
- GFIX Send DK Trade
- HFIX Recv Message
- IFIX Recv Message
- JFIX Send Reject
- KFIX EOD
- LFIX DK
27Select all options that can flush the Moxy RTM Event Queue:
- AMoxyResetDatabase job
- BMoxyRefreshDatabase job
- Cexec pMxRTMCleanUpQueue, 0, 1
- Dexec pMxRTMCleanUpRecords, 0, 1
28Select all possible reasons why an entry in the RTM Event Queue is not being processed while other RTM events are processing just fine:
- ARTM Service is not started
- BEvent Group is not enabled
- CRTM service is not restarted after enabling the Event Group
29Select all tables where the statuses are flipped to 1 once RTM is able to process entries/events successfully:
- AMoxyRTMEventQueue
- BMoxyRTMEventQueueData
- CMoxyRTMevent
- DMoxyRTMEventDataActionStatus
- EMoxyRTMRuleAction
- FMoxyFIXExtMessage
30If there is an entry in the Event Queue for EventID = 72 and Status = 0, Moxy will think "go and process ALL available fills".
- AVerdadero
- BFalso
31Before fills are put into the MoxyFill table, they are:
- AChecked to make sure they are not duplicates that have already been processed
- BVerified to have the correct quantity
- CChecked to make sure they have the correct broker
- DMake sure they are associated with existing, open FIX places in Moxy
32Sequence numbers are tracked in which tag?
- ATag 54
- BTag 34
- CTag 11
- DTag 17
33Moxy and FIXNET are "in sync" when Moxy's sequence number is ahead of FIXNET.
- AVerdadero
- BFalso
34To check if Moxy and the FIXNet database are in sync, we can verify the sequence numbers stored in their respective tables.
For Moxy, we can check the [blank_start]LastRxMsgSeqNum[blank_end] column in the [blank_start]MoxyFIXConnectionData[blank_end] table which represents the sequence number of the [blank_start]last processed[blank_end] incoming FIX message.
While in FIXNET, we can check the [blank_start]FIX_SESSION_STATE[blank_end] table for the [blank_start]RX_MSG_SEQ_NUM[blank_end] column that contains the [blank_start]next anticipated[blank_end] incoming sequence number.
Moxy's sequence number should always be [blank_start]one less[blank_end] than the FIX sequence number.- ALastRxMsgSeqNum
- BMoxyFIXConnectionData
- Clast processed
- DFIX_SESSION_STATE
- ERX_MSG_SEQ_NUM
- Fnext anticipated
- Gone less
35Which SQL Agent job will perform an EOD on the Moxy/FIXNET system?
- AMoxyFIXStartTime job
- BMoxyFIXStopTime job
- CMoxyRefreshDatabase job
- DMoxyResetDatabase job
36Select all true statements regarding Moxy's mechanism for getting back in sync with the FIXNET database:
- AWhen Moxy finds itself ahead of FIXNet's sequence number, it will request for a replay
- BWhen Moxy finds itself ahead of FIXNet's sequence number, it will do nothing
- CWhen Moxy finds itself behind FIXNET's sequence number by more than one, it will stop processing FIX messages
- DWhen Moxy finds itself behind FIXNET's sequence number by more than one, it will do nothing
- EWhen Moxy finds itself behind FIXNET's sequence number by more than one, it will request for a replay
37Moxy replays messages from FIXNET in batches of 100.
- AVerdadero
- BFalso
38Bad messages to have "Failed the SolutionForge session-level validation" are caused by:
- AFIX executions that are not acknowledged
- BFIX executions with unsupported tags being sent by the broker
- CBroker has sent a standard tag back on a wrong type of message
- DBroker is not listed in Moxy
39Bad messages to have "Failed the SolutionForge session-level validation" will be responded by FIX.NET with a:
- AReject Message (35=1)
- BDK Trade (35=Q)
- CReject Message (35=3)
- DDK Trade (35=3)
40In order to prevent RTM from forever asking for the same missing message, MoxyFIXConnectionData maintains a request count number in which column?
- ARxRequestCount
- BRxRqstCount
- CMaxReXmit
- DRqstRxCount
41This hidden dipswitch/setting tells RTM how many times it should request the same sequence number:
- AMaxRemitX
- BMaxReXmit
- CRxRqstCount
42To activate the hidden dispwitch for RTM replay logic, which should you run?
- AWriteProfileInt 'MaxReXmit', 'FIX', '', 2
- BWriteProfileInt 'FIX', RxRqstCount' ,'', 2
- CWriteProfileInt 'FIX', 'MaxReXmit', '', 2
43To delete the hidden dipswitch/setting for RTM replay logic, which should you run?
- ADeleteProfile 'FIX', 'MaxReXmit', ''
- BDeleteProfile 'MaxReXmit', 'FIX', ''
- CDeleteProfile 'RxRqstCount, 'FIX', ''
44FIXNET will not replay EXPIRED messages.
- AVerdadero
- BFalso
45What should you do to unexpire a FIX message?
- AUpdate RX_MESSAGE_STORE.MESSAGE_EXPIRED_TIME, set to NULL
- BUpdate FIX_MESSAGES.MSG_EXPIRED_TIME, set to NULL
- CUpdate RX_MESSAGE_STORE.MSG_EXPIRED_TIME, set to NULL
- DUpdate FIX_MESSAGES.MESSAGE_EXPIRED_TIME, set to NULL
46Tag 11 is for which field?
- ABroker's Order ID
- BBroker's Execution ID
- CClient Order ID
47Tag 11 or Client Order ID can be found in which column of the MoxyFIXPlaceOrder table?
- AFIXORID
- BFIXOrderID
- CFIXClOrdID
48If Moxy receives a FIX message with a Tag = 11 that doesn't correspond to real Client Order ID, what will be sent to the broker?
- AReject Message (35=3) complaining about BadClOrdID
- BDon't Know Trade (35=Q) complaining about BadClOrdID
- CDon't Know Trade (35=3)complaining about BadClOrdID
49Subsequent executions can still find their way to the correct trade even after Close and Split off Remainder is used because of which column in the MoxyFIXPlaceOrder table?
- AOrigFIXOrderID
- BFIXParentOrderID
- COrigOrderFIXID
50What is tag 37 for?
- AMoxy Client Order
- BBroker's OrderID
- CBroker's Execution ID
- DExecuting Broker Tag
51Select all true statements for Tag 37:
- AIt is the same with Moxy Client Order ID
- BIt is generated by the broker
- CIt can be found in the FIXBrokerOrderID field in MOxyFIXPlaceOrder
- DIt cannot contain letters
52What is the tag number for Broker's Execution ID?
- ATag 17
- BTag 37
- CTag 34
- DTag 7
53Which tag indicates the broker who executed the trade?
- ATag 17
- BTag 76
- CTag 11
- DTag 27
- ETag 16
54To prevent duplicate fills while processing executions, Moxy will extract 4 pieces of data which will be combined into a Message Key. This Message Key contains which of the following?
- ATag 11 (if present), Tag 37, Tag 17, Tag 76)
- BTag 17 (if present), Tag 11, Tag 76, Tag 37)
- CTag 76 (if present), Tag 17, Tag 37, Tag 11)
- DTag 37 (if present), Tag 11, Tag 17, tag 76)
55If Moxy sees a duplicate Message Key while processing executions, what would it do?
- AReprocess the execution and insert it into the MoxyFill table
- BStop processing all executions until the duplicate is deleted
- CIgnore the fill and insert a message into the Moxy Event Log declaring "Ignored duplicate message..."
- DReplay all executions and insert a message into the Moxy Event Log declaring "Ignored duplicate message..."
56All incoming FIX messages are recorded in which two places?
- ATX_MESSAGE_STORE
- BRX_MESSAGE_STORE
- CFIX_MESSAGE_LOG
- DMoxyFIXExtMessage
- ELog file in the SolutionForge Log directory
- FFIX_MESSAGES
57Name the following tags:
Tag 52 - [blank_start]Sending Time[blank_end]
Tag 60 - [blank_start]Transaction Time[blank_end]
Tag 63 - [blank_start]Settlement Type[blank_end]
Tag 75 - [blank_start]Trade Date[blank_end]- ASending Time
- BTransaction Time
- CSettlement Type
- DTrade Date
58Tag 60 is an optional standard tag that takes precedence over Tag 52 or Tag 75.
- AVerdadero
- BFalso
59If this tag is present, Moxy will take the date supplied as Fill Settle Date and will override all other tags.
- ATag 63
- BTag 64
- CTag 65
- DTag 75
60You need to activate a dipswitch to be able to use Tag 75 as your Trade Date.
- AVerdadero
- BFalso
61You need to activate a dipswitch to use Tag 52 as your Trade Date.
- AVerdadero
- BFalso
62Select all the methods clients employ to make Moxy's functionality work for International trading:
- ASuppress Tag 105
- BSuppress Tag 60
- CUse Tag 52
- DUse Tag 64
- EUse Tag 75
63What are the requirements for UTRs or Drop Copies?
- ATag 35 = 8, Tag 11 = 1
- BTag 35 = 8
- CTag 11 is not present
- DTag 35 = 11
- ETag 17 matches a valid Broker FIX ID in Moxy
- FUTR check box is activated for the Broker
- GTag 76 or 50 matches a valid Broker FIX ID in Moxy
Información
- Descripción
- Precertification Exam for FIX II
- Autor
- Janine Northcott
- Idioma
- English
- Visitas
- 93
- Historial
- Creado el 14 may 2017 · actualizado el 14 may 2017
- Etiquetas
- Valoración
- Aún sin valoraciones Valora este test