[01/Quickstart/01]

180 Questions

Which of the following best describes the purpose of a SQL API in Flow.BI?

To provide experimental access to raw data from the repository for custom dashboards and ad-hoc queries

What is the purpose of multi-tenancy in Flow.BI?

To allow Flow.BI to serve multiple customers from the same infrastructure

How is a client identified in Flow.BI?

By a client id

What does an instance represent in Flow.BI?

A version of a data warehouse solution

What is the purpose of a snapshot in Flow.BI?

To represent a version of an instance over time

What is the underlying concept for the data warehouse automation in Flow.BI?

Data Vault 2.0

How does Flow.BI model the data in the Data Vault 2.0 model?

As it is stored in the source systems

Which of the following best describes Flow.BI?

A tool for automating data integration

What advantage does Flow.BI have over standalone tools like Wherescape, Vaultspeed, or dbt?

Flow.BI automates the data analysis process

What is the difference between Flow.BI and traditional data warehousing solutions?

Flow.BI models data-driven data models

Which tools can Flow.BI deliver metadata to for data warehouse automation?

Wherescape, Vaultspeed, and dbt

What does Flow.BI automate in the data warehouse setup process?

Data modeling

What type of data concepts does Flow.BI integrate better with?

NoSQL databases

What is the main advantage of using Flow.BI for data warehousing?

More automation and flexibility

Which approach is often used to avoid the overhead and non-agility of traditional data warehouse solutions?

Data lakes

What is one disadvantage of a pure data lake approach?

Data lakes are not relational integrated

What advantage does Flow.BI offer in terms of data warehousing?

Integration of data flows

What does the resulting data model from Flow.BI allow for?

Multiple business perspectives

What security feature does Flow.BI support?

Data reduction or deletion

Which tools turn the logical model from Flow.BI into a physical model?

Wherescape, dbt, and Vaultspeed

What can the generated logical model from Flow.BI be used for?

Analytical data platforms

Which concept does Flow.BI use to build new ships for data warehousing?

Data Vault 2.0

What terms does Flow.BI hide from the user interface for business users?

Hubs, links, and satellites

How does Flow.BI refer to the hidden terms in the user interface for business users?

Hubs, links, and satellites

What can users do if they are more familiar with Data Vault 2.0?

Switch their role to a technical user role

What is the purpose of Data Vault 2.0 in Flow.BI?

To build new ships for data warehousing

Which article from the technical user documentation describes the Flow.BI architecture by comparing it to the Data Vault 2.0 reference architecture?

Flow.BI Architecture

What does Flow.BI use to automate the data warehouse building process?

Data Vault 2.0

What is the analogy used to explain the process of applying business rules in data warehousing?

Painting bricks red

What does Flow.BI promise to build with Data Vault 2.0?

Data analytics platforms

Which of the following tools does Flow.BI deliver metadata to for data warehouse automation?

Wherescape

What is the advantage of Flow.BI over standalone tools like Wherescape, Vaultspeed, or dbt?

Flow.BI automates the design decisions of setting up the data model for data warehouse solutions

What type of data sources does Flow.BI integrate and historize data from?

Various data sources

What is the modeling approach of Flow.BI for data warehousing?

Data-driven modeling

What is the benefit of Flow.BI's data-driven data models?

They allow for a more agile approach to data warehousing

What does Flow.BI automate in the data warehouse setup process?

Data analysis and identification of shared business keys

What is the main advantage of using Flow.BI for data warehousing?

It automates the design decisions of setting up the data model

Which of the following is NOT a capability of Flow.BI?

Support for data lineage

What is one advantage of using Flow.BI for data warehousing?

Increased consistency of the overall solution

What does Flow.BI support in terms of security?

Cell-level security

What is one disadvantage of a pure data lake approach?

Redundant application of business rules

What is the main purpose of the generated logical model from Flow.BI?

To support multiple business perspectives

What does Flow.BI use to speed up the development process of the analytical data platform?

Sophisticated metadata and data profiling

Which tools turn the logical model from Flow.BI into a physical model?

Wherescape, Vaultspeed, and dbt

Which of the following best describes the purpose of a snapshot in Flow.BI?

To capture changes to the source data

What is the main advantage of using Flow.BI for data warehousing?

It provides a fully automated process

What does Flow.BI promise to build with Data Vault 2.0?

A logical model

What is the purpose of multi-tenancy in Flow.BI?

To allow multiple customers to use the same infrastructure

What is the purpose of a SQL API in Flow.BI?

To provide access to raw data for custom dashboards and ad-hoc queries

What does Flow.BI use to automate the data warehouse building process?

Data Vault 2.0

How does Flow.BI model the data in the Data Vault 2.0 model?

Based on the source data

Which approach does Flow.BI use to automate the data warehouse setup process?

Extract, Transform, Load (ETL)

What terms does Flow.BI hide from the user interface for business users?

Hubs, links, and satellites

What is the analogy used to explain the process of applying business rules in data warehousing?

Painting ships red

What is the purpose of multi-tenancy in Flow.BI?

To support different clients on a shared infrastructure

What does Flow.BI promise to build with Data Vault 2.0?

A fully automated data analytics platform

How does Flow.BI refer to the hidden terms in the user interface for business users?

Business terms

What is the main advantage of using Flow.BI for data warehousing?

Agility

What is the underlying concept for the data warehouse automation in Flow.BI?

Data Vault 2.0

Which article from the technical user documentation describes the Flow.BI architecture by comparing it to the Data Vault 2.0 reference architecture?

Flow.BI Architecture

Flow.BI is a data warehouse solution.

False

Flow.BI automates the design decisions of setting up the data model for data warehouse solutions.

True

Flow.BI delivers the metadata for the automated data warehouse model to data warehouse automation tools like Wherescape, Vaultspeed, and dbt.

True

Flow.BI models data-driven data models, allowing for multiple business perspectives and integration with Big Data concepts.

True

Flow.BI requires the user to manually analyze data sources and define security and privacy levels.

False

Flow.BI offers more automation and flexibility compared to traditional conceptual data warehouse solutions.

True

Flow.BI is not compatible with schema-on-read, real-time processing, and NoSQL databases.

False

True or false: Data lakes are used to avoid the overhead and non-agility of traditional data warehouse solutions.

True

True or false: Organizations that leverage a pure data lake approach often face inconsistencies in information delivery.

True

True or false: Flow.BI integrates data warehousing and data lakes to provide a middle ground solution.

True

True or false: Flow.BI allows the application of multiple different business perspectives to the data model.

True

True or false: Flow.BI supports cell-level security to meet the highest security standards.

True

True or false: Flow.BI supports data models that allow the reduction or deletion of personal data to comply with regulations.

True

True or false: Flow.BI drastically speeds up the overall development process of the analytical data platform.

True

Flow.BI uses Data Vault 2.0 as a tool to build the data analytics platform.

True

Flow.BI hides terms like hubs, links, and satellites in the user interface for business users.

True

Flow.BI can be switched to a Data Vault 2.0 tool for technical users.

True

The Flow.BI architecture is compared to the Data Vault 2.0 reference architecture in one of the articles from the technical user documentation.

True

Data Vault 2.0 is a fully automated process in Flow.BI.

True

Flow.BI uses business-like terms like business keys, relationships, and descriptive data instead of hubs, links, and satellites.

True

Flow.BI builds new ships for all incoming models from all kids in the neighborhood.

True

Flow.BI offers a user interface specifically designed for business users.

True

Data Vault 2.0 is the main tool used by Flow.BI to build the data analytics platform.

True

The SQL API in Flow.BI allows users to access raw data from the repository for custom dashboards and ad-hoc queries.

True

Multi-tenancy in Flow.BI is implemented using a client and an instance.

True

Each client in Flow.BI is globally identified by a UUID.

True

An instance in Flow.BI represents a data warehouse solution that is completely separated from other instances.

True

A snapshot in Flow.BI represents a version of an instance that has been deployed for a while.

True

Flow.BI follows a data-driven modeling style of Data Vault 2.0.

True

Data Vault 2.0 captures three fundamental components of data: business keys, relationships, and descriptive data.

True

Flow.BI is a data warehouse solution that automates the design decisions of setting up the data model for such solutions.

False

Flow.BI delivers the metadata for the automated data warehouse model to data warehouse automation tools like Wherescape, Vaultspeed, and dbt.

True

Flow.BI models data-driven data models, allowing for multiple business perspectives and integration with Big Data concepts.

True

Flow.BI requires the user to manually analyze data sources and define security and privacy levels.

False

Flow.BI uses business-like terms like business keys, relationships, and descriptive data instead of hubs, links, and satellites.

True

Flow.BI offers a user interface specifically designed for business users.

True

Data lakes are used to avoid the overhead and non-agility of traditional data warehouse solutions.

True

True or false: Data lakes are often used to avoid the overhead and non-agility of traditional data warehouse solutions.

True

True or false: Flow.BI integrates data warehousing and data lakes to provide a versatile information production.

True

True or false: The resulting data model from Flow.BI allows the application of multiple different business perspectives.

True

True or false: Flow.BI supports cell-level security to meet the highest security standards.

True

True or false: The generated data model from Flow.BI supports data models that allow the reduction or deletion of personal data, in compliance with regulations like GDPR and HIPAA.

True

True or false: Flow.BI drastically speeds up the overall development process of the analytical data platform.

True

True or false: Flow.BI includes the loading scripts from Flow.BI's repository to the Data Vault automation tools.

False

Flow.BI uses Data Vault 2.0 as a tool to build the data analytics platform.

True

Flow.BI can be switched to a Data Vault 2.0 tool for technical users.

True

Flow.BI builds new ships for all incoming models from all kids in the neighborhood.

True

Flow.BI models data-driven data models, allowing for multiple business perspectives and integration with Big Data concepts.

True

Each client in Flow.BI is globally identified by a UUID.

False

Flow.BI supports cell-level security to meet the highest security standards.

False

A snapshot in Flow.BI represents a version of an instance that has been deployed for a while.

True

Flow.BI uses business-like terms like business keys, relationships, and descriptive data instead of hubs, links, and satellites.

True

Which tools turn the logical model from Flow.BI into a physical model?

False

True or false: A SQL API in Flow.BI allows users to access raw data from the repository for custom dashboards and ad-hoc queries.

True

True or false: Flow.BI offers multi-tenancy, which is implemented by the use of a client and an instance.

True

True or false: Each client in Flow.BI is globally identified by a UUID.

True

True or false: An instance in Flow.BI represents one data warehouse solution to be produced and is globally identified by a UUID.

True

True or false: A snapshot in Flow.BI represents a version of an instance, which has been deployed for a while and is identified by the snapshot timestamp.

True

True or false: Flow.BI is based on Data Vault 2.0 as the underlying concept for data warehouse automation.

True

True or false: The Data Vault 2.0 model in Flow.BI is based on how the data is stored in the source systems, not the business.

True

True or false: Flow.BI is a data warehouse solution.

False

True or false: Flow.BI models data-driven data models, allowing for multiple business perspectives and integration with Big Data concepts.

True

True or false: Each client in Flow.BI is globally identified by a UUID.

True

True or false: A snapshot in Flow.BI represents a version of an instance, which has been deployed for a while and is identified by the snapshot timestamp.

True

True or false: The generated data model from Flow.BI supports data models that allow the reduction or deletion of personal data, in compliance with regulations like GDPR and HIPAA.

True

True or false: The resulting data model from Flow.BI allows the application of multiple different business perspectives.

True

True or false: The SQL API in Flow.BI allows users to access raw data from the repository for custom dashboards and ad-hoc queries.

True

True or false: Data lakes are used to avoid the overhead and non-agility of traditional data warehouse solutions.

True

True or false: The resulting data model from Flow.BI allows the application of multiple different business perspectives.

True

True or false: Flow.BI offers a user interface specifically designed for business users.

True

True or false: Flow.BI automates the design decisions of setting up the data model for data warehouse solutions.

True

True or false: A SQL API in Flow.BI allows users to access raw data from the repository for custom dashboards and ad-hoc queries.

True

True or false: The Data Vault 2.0 model in Flow.BI is based on how the data is stored in the source systems, not the business.

True

True or false: A pure data lake approach is a disadvantage in terms of information delivery consistency.

True

True or false: Flow.BI's multi-tenancy is implemented by the use of a client and an instance.

True

True or false: Each client in Flow.BI is globally identified by a UUID.

True

True or false: An instance in Flow.BI represents one data warehouse solution and is globally identified by a UUID.

True

True or false: A snapshot in Flow.BI represents a version of an instance that has been deployed for a while.

True

True or false: Flow.BI follows a data-driven modeling style of Data Vault 2.0.

True

True or false: Data Vault 2.0 is based on the fact that all data, including enterprise data, consists of four fundamental components.

False

True or false: Flow.BI integrates business-like terms like hubs, links, and satellites in its user interface.

False

True or false: Flow.BI uses Data Vault 2.0 as a tool to build the data analytics platform.

True

True or false: Flow.BI hides terms like hubs, links, and satellites in the user interface for business users.

True

True or false: Flow.BI offers a user interface specifically designed for business users.

True

True or false: Flow.BI drastically speeds up the overall development process of the analytical data platform.

True

True or false: Flow.BI integrates data warehousing and data lakes to provide a middle ground solution.

True

True or false: The resulting data model from Flow.BI allows the application of multiple different business perspectives.

False

True or false: Flow.BI supports data models that allow the reduction or deletion of personal data to comply with regulations.

True

True or false: Each client in Flow.BI is globally identified by a UUID.

True

True or false: Flow.BI supports cell-level security to meet the highest security standards.

True

Match the following terms from Flow.BI with their correct definitions:

Client = A legal entity who is performing business with Flow.BI Instance = Represents one data warehouse solution to be produced Snapshot = A version of an instance which has been deployed for a while Data Vault 2.0 = Based on the fact that all data consists of three fundamental components: business keys, relationships, and descriptive data

Match the following concepts with their descriptions in the context of Flow.BI:

Multi-tenancy = Implemented by the use of a client and an instance Data-driven modelling style of Data Vault 2.0 = Modelling the data as it is stored in the source systems but in the way the business is using it Business keys = Used to identify business objects in the Data Vault 2.0 model Hubs, Links, and Satellites = Fundamental components of the Data Vault 2.0 model

Match the following concepts to their correct statements in the context of Flow.BI:

Client = Globally identified by a UUID Instance = Organized in a simple list, not a hierarchy Snapshot = Identified within the instance by the snapshot timestamp on a linear timeline Data Vault 2.0 = Modelling the source data, not the business initially

Match the following terms to their correct descriptions in the context of Flow.BI:

Business keys = Used by business users to identify business objects in the Data Vault 2.0 model Links = Capture a distinct list of relationships in the Data Vault 2.0 model Satellites = Capture the descriptive data in the Data Vault 2.0 model Instance = Represents one data warehouse solution to be produced in Flow.BI

Match the following terms to their correct definitions in the context of Flow.BI:

Client = A legal entity who is performing business with Flow.BI and is globally identified by a UUID Instance = A data warehouse solution in Flow.BI that is globally identified by a UUID Snapshot = A version of an instance in Flow.BI that is identified by the snapshot timestamp on a linear timeline Business keys = Used to identify business objects in the Data Vault 2.0 model in Flow.BI

Match the following terms to their correct explanations in the context of Flow.BI:

Client = A legal entity who is performing business with Flow.BI and is globally identified by a UUID Instance = A data warehouse solution in Flow.BI that is globally identified by a UUID Snapshot = A version of an instance in Flow.BI that is identified by the snapshot timestamp on a linear timeline Data Vault 2.0 = A modeling approach in Flow.BI that captures three fundamental components: business keys, relationships, and descriptive data

Match the following terms to their correct definitions in the context of Flow.BI:

Client = A legal entity who is performing business with Flow.BI and is globally identified by a UUID Instance = A data warehouse solution in Flow.BI that is globally identified by a UUID Snapshot = A version of an instance in Flow.BI that is identified by the snapshot timestamp on a linear timeline Data Vault 2.0 = A modeling approach in Flow.BI that captures three fundamental components: business keys, relationships, and descriptive data

Match the following Flow.BI capabilities with their descriptions:

Integration of data warehousing and data lakes = Presents a middle ground between traditional data warehousing and data lakes by integrating data flows, historizing them and allowing the late application of business rules Multiple business perspectives = Allows the application of multiple different, even contradicting and infant, business perspectives Full audit-ability of the resulting data model = Allows the use of the solution in banks, insurances and government agencies where audit-ability, data lineage, and other features are required Support for cell-level security = Leverages security concepts from government-grade data warehouse solutions to provide secure solutions that can meet the highest security standards

Match the following features of Flow.BI with their descriptions:

Support for privacy = Supports data models that allow the reduction or deletion of personal data, a requirement by the General Data Protection Regulation (GDPR), Health Insurance Portability and Accountability Act (HIPAA) and other regulations Integration and versionizing of all source data at once = Achieved by sophisticated metadata and data profiling and the application of complex modeling rules Generation of the logical model = Performed by Flow.BI and used by the on-site data warehouse automation package, e.g. WhereScape, to generate the physical model Loading scripts from Flow.BI’s repository to the Data Vault automation tools = Provided directly by the provider or 3rd parties via the Flow.BI Marketplace

Match the following components of the Flow.BI architecture with their descriptions:

Web frontend = The interface through which users interact with the Flow.BI backend Data sources = Added to the Flow.BI application by users and then processed by the backend Backend = Processes the data sources and generates the logical model for data warehouse automation tools Data Warehouse automation tools = Turn the logical model from Flow.BI into a physical model

Match the following aspects of Flow.BI with their descriptions:

Data models = Generated by Flow.BI for analytical data platforms Business rules = Can be re-used in Flow.BI's approach to data warehousing, increasing the consistency of the overall solution Consistency = Increased in the overall solution by re-using existing entities and not deviating from the existing solutions Overall development process = Drastically sped up by Flow.BI, allowing the integration and versionizing of all source data at once

Match the following terms with their definitions in the context of Flow.BI:

Instance = Represents a data warehouse solution that is completely separated from other instances Snapshot = Represents a version of an instance that has been deployed for a while Client = Globally identified by a UUID in Flow.BI Cell-level security = Supported by Flow.BI to meet the highest security standards

Match the following statements about Flow.BI with their accuracy:

Flow.BI supports cell-level security = True The generated data model from Flow.BI supports data models that allow the reduction or deletion of personal data = True Flow.BI hides terms like hubs, links, and satellites in the user interface for business users = False Flow.BI drastically speeds up the overall development process of the analytical data platform = True

Match the following Flow.BI advantages with their descriptions:

Data warehousing and data lakes integration = Presents a middle ground between the two by integrating data flows, historizing them and allowing the late application of business rules Multiple business perspectives = Allows the application of multiple different, even contradicting and infant, business perspectives Full audit-ability of the resulting data model = Allows the use of the solution in banks, insurances and government agencies where audit-ability, data lineage, and other features are required Support for cell-level security = Leverages security concepts from government-grade data warehouse solutions to provide secure solutions that can meet the highest security standards

Match the following terms in Flow.BI with their corresponding descriptions:

Data Vault 2.0 = Just a tool to build the promised data analytics platform Hubs, links, and satellites = Hidden from the user interface for business users Business keys, relationships and descriptive data = More business-like terms used in the user interface for business users Flow.BI Architecture = Describes the Flow.BI architecture by comparing it to the Data Vault 2.0 reference architecture

Match the following user roles in Flow.BI with their corresponding features:

Business user = Does not see terms like hubs, links, and satellites in the user interface Technical user = Sees terms like hubs, links, and satellites throughout the user interface

Match the following data warehouse automation tools with their corresponding use in Flow.BI:

Wherescape = Receives metadata for the automated data warehouse model from Flow.BI Vaultspeed = Receives metadata for the automated data warehouse model from Flow.BI dbt = Receives metadata for the automated data warehouse model from Flow.BI

Match the following terms with their corresponding descriptions in the context of Flow.BI:

Flow.BI = A data warehouse solution that automates the design decisions of setting up the data model Data Vault 2.0 = A tool used by Flow.BI to build the promised data analytics platform Data-driven modeling = The modeling style followed by Flow.BI Cell-level security = A security feature supported by Flow.BI to meet the highest security standards

Match the following terms in Flow.BI with their corresponding descriptions:

Data Vault 2.0 = A tool used by Flow.BI to build the promised data analytics platform Hubs, links, and satellites = Terms hidden from the user interface for business users in Flow.BI Business keys, relationships and descriptive data = More business-like terms used in the user interface for business users in Flow.BI Flow.BI Architecture = An article from the technical user documentation that describes the Flow.BI architecture by comparing it to the Data Vault 2.0 reference architecture

Match the following user roles in Flow.BI with their corresponding features:

Business user = Does not see terms like hubs, links, and satellites in the user interface in Flow.BI Technical user = Sees terms like hubs, links, and satellites throughout the user interface in Flow.BI

Match the following data warehouse automation tools with their corresponding use in Flow.BI:

Wherescape = Receives metadata for the automated data warehouse model from Flow.BI in Flow.BI Vaultspeed = Receives metadata for the automated data warehouse model from Flow.BI in Flow.BI dbt = Receives metadata for the automated data warehouse model from Flow.BI in Flow.BI

Match the following terms with their corresponding descriptions in the context of Flow.BI:

Flow.BI = A data warehouse solution that automates the design decisions of setting up the data model in Flow.BI Data Vault 2.0 = A tool used by Flow.BI to build the promised data analytics platform in Flow.BI Data-driven modeling = The modeling style followed by Flow.BI in Flow.BI Cell-level security = A security feature supported by Flow.BI to meet the highest security standards in Flow.BI

Match the following terms in Flow.BI with their corresponding descriptions:

Data Vault 2.0 = Just a tool to build the promised data analytics platform in Flow.BI Hubs, links, and satellites = Hidden from the user interface for business users in Flow.BI Business keys, relationships and descriptive data = More business-like terms used in the user interface for business users in Flow.BI Flow.BI Architecture = Describes the Flow.BI architecture by comparing it to the Data Vault 2.0 reference architecture in Flow.BI

Match the following terms with their descriptions in the context of Flow.BI:

Flow.BI = A service for the automated integration and historization of data from various data sources Data Vault 2.0 = A tool used by Flow.BI to build the data analytics platform Snapshot = A version of an instance, which has been deployed for a while and is identified by the snapshot timestamp Data-driven data models = Models used by Flow.BI that allow for a more agile approach to data warehousing and application of multiple business perspectives

Match the following tools with their usage in the context of Flow.BI:

Wherescape, Vaultspeed and dbt = Tools that generate the data warehouse using the data model created by Flow.BI Data warehouse automation tools = Receive the metadata for the automated data warehouse model from Flow.BI Data warehouse modellers = Create conceptual models in traditional data warehousing solutions Flow.BI = Automates the design decisions of setting up the data model for data warehouse solutions

Match the following statements with their correctness:

Flow.BI is a data warehouse solution = False Flow.BI integrates business-like terms like hubs, links, and satellites in its user interface = False Each client in Flow.BI is globally identified by a UUID = True Flow.BI offers a user interface specifically designed for business users = True

Match the following concepts with their descriptions in the context of Flow.BI:

Data lake = A concept that Flow.BI integrates with to provide a middle ground solution Cell-level security = A security feature supported by Flow.BI to meet the highest security standards Schema-on-read = A Big Data concept that Flow.BI integrates with NoSQL databases = A type of database that Flow.BI integrates with

Match the following advantages with their descriptions in the context of Flow.BI:

Automation and flexibility = Flow.BI offers more of these compared to traditional conceptual data warehouse solutions Efficiency = Flow.BI automates the design decisions of setting up the data model, saving time and effort Integration with Big Data concepts = Flow.BI integrates much better with these compared to traditional data warehouse solutions Reduction of initial setup and customization time = Flow.BI eliminates or reduces the need for this in the data warehouse automation process

Match the following terms with their descriptions in the context of Flow.BI:

Client = In Flow.BI, each client is globally identified by a UUID Instance = In Flow.BI, each instance represents one data warehouse solution and is globally identified by a UUID Data model = Flow.BI automates the design decisions of setting up this for data warehouse solutions Metadata = Flow.BI delivers this for the automated data warehouse model to data warehouse automation tools

Match the following statements with their correctness:

Flow.BI's multi-tenancy is implemented by the use of a client and an instance = True The resulting data model from Flow.BI allows the application of multiple different business perspectives = True Organizations that leverage a pure data lake approach often face inconsistencies in information delivery = True Flow.BI uses business-like terms like business keys, relationships, and descriptive data instead of hubs, links, and satellites = False

Test your knowledge about SQL APIs, multi-tenancy, and data warehouse solutions with this quiz. Learn about how a SQL API provides access to raw data for custom dashboards and queries, and understand how multi-tenancy allows Flow.BI to serve multiple customers from the same infrastructure. Explore the implementation of multi-tenancy through the use of clients and instances for creating data warehouse solutions.

Make Your Own Quizzes and Flashcards

Convert your notes into interactive study material.