




Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
A comprehensive overview of the various roles and stakeholders involved in the cogito system, a platform for reporting and analytics. It outlines the responsibilities of each role, including database administrators, application analysts, business intelligence developers, and cogito project managers. The document also includes a series of questions and answers related to the cogito system, providing insights into its functionality and data flow.
Typology: Exams
1 / 8
This page cannot be seen from the preview
Don't miss anything!
Database |Administrator |- |correct |answer | ✔ Each |of |Epic's |databases |has |this. | They |sometimes |oversee |operation |of |more |than |one |database Chronicles |Administrator |- |correct |answer | ✔ Oversees |the |daily |functioning |and | troubleshooting |of |Chronicles, |as |well |as |updates |to |the |system Clarity |Administrator |- |correct |answer | ✔ Oversees |and |troubleshoots |nightly | and |ad ‐ hoc |Clarity |ETL |executions |that |move |data |from |Chronicles |to |Clarity. Cogito |Project |Manager |- |correct |answer | ✔ Responsible |for |the |success |of |the | Cogito |team. |They |have |a |high ‐ level |understanding |of |each |of |the |databases | and |tools |used |by |their |organization |and |have |a |detailed, |specific |knowledge |of | the |processes |and |policies |that |govern |the |reporting |and |analytics |goals |of |the | organization. Application |Analyst |- |correct |answer | ✔ They |interact |most |often |with |the |Cogito |team |as |subject |matter |experts |(SMEs) |who |can |help |a |report |writer |find |the | right |data |or |understand |a |workflow |used |to |populate |the |data |for |a |report. Business |Intelligence |Developer |- |correct |answer | ✔ They |use |all |of |Cogito's |tools |to |retrieve |and |analyze |data |from |all |of |Epic's |databases. Caboodle |Developer |- |correct |answer | ✔ Build |the |packages |to |bring |additional | Clarity |data |and |non ‐ Epic |data |into |Caboodle
They |know |how |and |why |all |data |comes |into |Caboodle Cogito |Principal |Trainer |- |correct |answer | ✔ Responsible |for |customizing |and | delivering |reporting |training |to |end |users |at |each |organization Which |of |the |following |responsibilities |are |often |met |by |the |Cogito |team? |- | correct |answer | ✔ Creating |custom |Radar |dashboards |for |end |users Managing |the |flow |of |data |between |Clarity |and |Caboodle Your |Chronicles |Administrator, |Clarity |Administrator |and |Caboodle | Administrator |will |always |be |three |separate |people |- |correct |answer | ✔ False. Database |administrators |sometimes |oversee |operation |of |more |than |one | database. |- |correct |answer | ✔ True The |Cogito |team: |- |correct |answer | ✔ Builds, |validates, |and |distributes |reports | from |three |different |databases Is |responsible |for |the |flow |of |data |between |those |databases Cogito |teams |may |be |involved |in |building |extracts |to |feed |non Epic ‐ |data | warehouses |- |correct |answer | ✔ True
Reasons |to |contact |the |Clarity |Administrator |include |- |correct |answer | ✔ A | Clarity |report |looking |at |the |last |year's |data |isn't |displaying |anything |for |the | most |recent |two |months | Meeting |to |decide |which |new |Epic released ‐ |views |and |derived |tables |should |be |enabled |during |an |upgrade Corrupted |or |incorrect |data |has |made |its |way |into |Clarity |reports |that |used |to | work |perfectly Caboodle |Administrator |- |correct |answer | ✔ Oversees |and |troubleshoots |nightly | and |ad ‐ hoc |Caboodle |ETL |executions |that |move |data |from |Clarity |to |Caboodle. Also |responsible |for |updates |to |Caboodle Caboodle |Administrator's |are |also |known |as |- |correct |answer | ✔ Caboodle |ETL | Administrator ETL |Administrator |﴾without |mention |of |Caboodle﴿, |particularly |if |they |oversee | both |Clarity |and |Caboodle |ETL Caboodle |Administrators |are |primarily |responsible |for |customization |of | Caboodle |- |correct |answer | ✔ False Your |Caboodle |Administrator |may |be |involved |in |Caboodle |Development, |may | be |a |Caboodle |Developer, |or |may |be |mostly |uninvolved |- |correct |answer | ✔ True
Reasons |to |contact |the |Caboodle |Administrator |include |- |correct |answer | ✔ Requesting |an |ad |hoc |ETL |into |a |test |Caboodle |database |to |validate |a |report | with |test |data | SlicerDicer |sessions |are |missing |data |for |a |conspicuous |date |range | Scheduling |ETLs |from |a |new |non Epic ‐ |data |source |into |Caboodle Reasons |to |contact |the |Cogito |Project |Manager |include |- |correct |answer | ✔ Questions |about |the |report |request |process | Help |managing |workload |and |appropriately |estimating |time |commitments |for | reporting |projects |Projects |that |require |strong |data |governance |across |multiple |databases |or | entities |within |the |organization | Triaging |or |prioritizing |reporting |projects Reasons |to |contact |a |BID |may |include: |- |correct |answer | ✔ Need |for |a |new | workbench |report | Can't |find |specific |report |or |dashboard |and |need |someone |to |grant |appropriate | access | Troubleshooting |existing |reports, |dashboards, |or |SlicerDicer |sessions
Reasons |to |contact |a |Caboodle |Developer |may |include: |- |correct |answer | ✔ Need |to |add |custom |SlicerDicer |Filter |to |an |existing |SlicerDicer |Data |Model | Scoping |out |the |possibility |of |building |a |SlicerDicer |Data |Model |on |non Epic ‐ | data Caboodle |developers |may |also |be |Caboodle |BIDs, |building |SQL |queries |to | retrieve |data |from |Caboodle. |- |correct |answer | ✔ True Caboodle |developers |are |involved |in |building |custom |SlicerDicer |Filter |or |even | entire |data |models |- |correct |answer | ✔ True Cogito |Tools |Administrator |- |correct |answer | ✔ Responsible |for |building |and | maintaining |AdHoc |and |SQL |Workbench |templates, |as |well |as |overseeing | distribution |of |dashboards |for |the |Cogito |team. Cogito |Tools |Administrator |needs |to |have |a |deep |understanding |of |the | Chronicles |data |structure |that |drives |Workbench |queries. |- |correct |answer | ✔ True The |Cogito |Tools |Administrator |may |be |one |person's |full time ‐ |job, |or |it |may |be | a |task |that |several |BIDs |share |at |an |organization. |- |correct |answer | ✔ True Reasons |to |contact |a |Cogito |Tools |Administrator |include |- |correct |answer | ✔ The | need |for |a |brand ‐ new |template |that |doesn't |yet |exist | Troubleshooting |a |custom |template's |parameters
|A |SQL |report |has |been |built |and |needs |to |be |integrated |into |Hyperspace |so | users |can |build |reports |from |it The |Cogito |Principal |Trainer |may |be |one |person's |full time ‐ |role, |or |a |Principal | Trainer |may |be |responsible |for |several |applications |and |include |Cogito |in |their | list |of |responsibilities |- |correct |answer | ✔ True Reasons |to |contact |a |Cogito |Principal |Trainer |may |include |- |correct |answer | ✔ Planning |for |which |users |should |receive |specialized |SlicerDicer |training |after | go ‐ live | Some |users |have |been |incorrectly |building |Workbench |reports |and |need |re ‐ training | Generating |and |distributing |tip |sheets |or |other |training |tools |for |ongoing | optimization |projects BIDs |may |specialize |in |certain |tools, |all |get |training |in |Workbench, |Radar, | SlicerDicer, |and |SQL |and |build, |maintain, |troubleshoot |reports |in |Chronicles, | Clarity, |and |Caboodle |- |correct |answer | ✔ True