Dq Mke 3rd Quarter - 2018

30 Questions | Total Attempts: 46

SettingsSettingsSettings
Please wait...
Dq Mke 3rd Quarter - 2018

Hi! To save time, you are allowed to jump to the next question even if you are not yet sure of your answer. For all of your unsure answers and unanswered questions, you can review and answer them once you click the Review all of my Answers tab after the last question. Once you have clicked the Submit my Final Answers tab at the end of the page, there is no going back. Wrong spelling is wrong. You will immediately know your scores right after the exam. We wish you the best!


Questions and Answers
  • 1. 
    SG Preliminary Data Checks for [Blank] Post-Race Data Checks for 27/07/2018 to 29/07/2018
  • 2. 
    Whenever we reprocess a missing race card in Data Store, we still need to raise an Event ticket for documentation. Once we resolve the ticket, what should be the resolution code?
    • A. 

      Resolved – Permanently

    • B. 

      Resolved – Workaround

    • C. 

      Resolved – External Vendor / 3rd Party

  • 3. 
    I need to raise a ticket for the missing race results for multiple races on 08/08/2018. Affected races are: Launceston R1-R5 (Tab) Rockhampton R1-R9 (Tab) Pinjarra R1-R4 (Non-tab) The Impact should be based on their total prize money, including the non-tab races.
    • A. 

      True

    • B. 

      False

  • 4. 
    When you have to raise a ticket for the UK-HorseWeightIsNull violation during live session, what should be the Issue Category?
    • A. 

      Live Data Issues

    • B. 

      Missing/Incomplete Data

    • C. 

      Invalid/Wrong Data

    • D. 

      Data Issues

  • 5. 
     In the USG Final Pool Size Check, even if you have confirmed that the affected race was abandoned, you still need to raise a JIRA for documentation.
    • A. 

      True

    • B. 

      False

  • 6. 
    For US Fair races, if you encounter the RaceMustHaveAtLeast2NonScratchedRunners violation and you have confirmed that race has only [Blank] runner/s, you can abandon the race.
  • 7. 
    We can acknowledge the FinishTimeIsNull violation for PMH races.
    • A. 

      True

    • B. 

      False

  • 8. 
    The new correct track venues that we are checking for AU are Pakenham, Newcastle and [Blank].
  • 9. 
    You have raised a JIRA for WinOddsIsNull violation. Later on, you have realized that it is a non-tab race so you need to close the ticket. The Root Cause Code for this scenario is:
    • A. 

      Data Issue

    • B. 

      Skill-based error

    • C. 

      Known Error

  • 10. 
    I need to downgrade the ticket from Critical/High to Minor/Low since the analyst who conducted the initial data checks incorrectly set the Impact and Urgency. Based on my findings, affected races were PMH races. These are the complete steps that I should follow: 1. Leave a comment in the JIRA: Hi SA, I need to downgrade the ticket from Critical/High to Minor/Low due to incorrect input of the first analyst. 2. SA approves 3. I’ll now downgrade the ticket
    • A. 

      True

    • B. 

      False

  • 11. 
    If a MissingResults violation is due to a missing race card that is still not fixed, there is no need for you to raise a ticket for the MissingResults violation.
    • A. 

      True

    • B. 

      False

  • 12. 
    What type of race is this?
    • A. 

      Gallops

    • B. 

      Harness

    • C. 

      Mounted Trot

    • D. 

      Flat

  • 13. 
    During the AU Mappings check, if there is a duplicate mapping for [Blank], we need to raise an Incident ticket and change the assigned group to 2nd line DEx.
  • 14. 
    Troubleshooting: UK Correct Track Check What should you input in the Venue Code field if there is a Newcastle meeting for the day?
  • 15. 
    If you encounter BarrierDrawIsNull violation during GRV live session, we are allowed to manually set the barrier draw of the runner from tab.com.au.
    • A. 

      True

    • B. 

      False

  • 16. 
    Which of the following violations can be ignored across all markets?
    • A. 

      AcceptableRangeEloRatingStdev

    • B. 

      RaceTypeDistanceRangeCheck

    • C. 

      AcceptableRangeLBWAStdev

  • 17. 
    What is the first step that we can do to resolve the missing race cards for SG/MY that are published in source?
    • A. 

      Raise a ticket

    • B. 

      Try to download

    • C. 

      Raise a ticket and escalate to 2nd line dex

  • 18. 
    During AU Live Session Monitoring, we need to start checking for any missing BF odds at [Blank] minutes before TTJ.
  • 19. 
    FR: Race-level mappings to be checked during data checks.
    • A. 

      CE

    • B. 

      CE_FR

    • C. 

      GT

    • D. 

      All of the above

  • 20. 
    The status for the Basic Checks should be Not Ok even if the missing race card was resolved since we still need 1st line to run the process.
    • A. 

      True

    • B. 

      False

  • 21. 
    The Data Source/Project for the SG market is [Blank]
  • 22. 
    In the UK Correct Track Check, if the xml file shows Lingfiled (A.W) as the course, the race_type is “FLT” and there is no ISAW field, no action is needed.
    • A. 

      True

    • B. 

      False

  • 23. 
    For GRV HorseWeightIsNull violation, when do we report in Skype that the weights are still incomplete or a runner is missing on the list?
    • A. 

      20mins

    • B. 

      15mins

    • C. 

      10mins

    • D. 

      Issue can be ignored

  • 24. 
    What is the Impact and Urgency for the combined missing P1 and P2 race cards?
    • A. 

      Based on prize money – High

    • B. 

      Critical – High

    • C. 

      Based on the prize money – depends on the SST of the 1st race of the market

    • D. 

      Critical– depends on the SST of the 1st race of the market

  • 25. 
    Based on the JIRA format, what should be the JIRA title for this issue? Violation: WinOddsIsNull Affected races: Hobart R1, R3, R5, R8
    • A. 

      WinOddsIsNull for multiple races

    • B. 

      WinOddsIsNull for Hobart R1, R3, R5, R8

    • C. 

      WinOddsIsNull for Hobart R1-R8

Back to Top Back to top