[02/Vitim/05]

<p>True</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>SQL Repository SQL API = Gives access to the backend Flow.BI repository Row-level security = Can be based on client in the Flow.BI repository Data Vault style enterprise data warehouse = Type of data warehouse used by the Flow.BI repository Worst case scenario = User reads data from an instance due to wrongly configured permissions</p> Signup and view all the answers

<p>RDV = Abbreviation for one of the components in the Flow.BI repository BV = Abbreviation for one of the components in the Flow.BI repository Info marts = One of the components in the Flow.BI repository Interface marts = One of the components in the Flow.BI repository</p> Signup and view all the answers

<p>It is possible to 'break out' of client tenant in the Flow.BI repository = False Row-level security in the Flow.BI repository is always based on client = False The worst case scenario in the Flow.BI repository is data leakage = True The SQL Repository SQL API provides access to the frontend of Flow.BI repository = False</p> Signup and view all the answers

<p>Security = Feature that protects SQL objects from unauthorized access Version control = Feature that tracks changes to SQL objects over time Backup and restore = Feature that protects SQL objects from data loss Performance tuning = Feature that optimizes the performance of SQL queries</p> Signup and view all the answers

<p>SQL repository = A database used to store and manage SQL objects RDBMS = A type of database management system that can be used to implement SQL repositories NoSQL database = Another type of database that can be used to implement SQL repositories Data warehousing = One of the applications where SQL repositories are used</p> Signup and view all the answers

<p>Tables = SQL objects used to store data in a structured format Views = Virtual tables that are based on the result of an SQL query Stored procedures = Prepared SQL code that can be executed multiple times Functions = SQL code that can be called with specific parameters to perform a specific task</p> Signup and view all the answers

<p>Security = To prevent unauthorized access to SQL objects Version control = To track changes made to SQL objects Backup and restore = To protect SQL objects from data loss Performance tuning = To optimize the performance of SQL queries</p> Signup and view all the answers

<p>RDBMS = A type of database management system commonly used to implement SQL repositories NoSQL database = Another type of database that can be used to implement SQL repositories Relational database = A type of database that organizes data into tables Data warehouse = A specialized database used for data analysis and reporting</p> Signup and view all the answers

<p>Tables = Structured representation of data in a database Views = Virtual tables that are based on the result of an SQL query Stored procedures = Prepared SQL code that can be executed multiple times Functions = Reusable SQL code that performs a specific task</p> Signup and view all the answers

<p>Security = To protect SQL objects from unauthorized access Version control = To track changes to SQL objects over time Backup and restore = To protect SQL objects from data loss Performance tuning = To optimize the performance of SQL queries</p> Signup and view all the answers

<p>Data mining</p> Signup and view all the answers

<p>To track changes to SQL objects over time</p> Signup and view all the answers

<p>Using a relational database management system (RDBMS) or a NoSQL database</p> Signup and view all the answers

<p>To protect SQL objects from data loss</p> Signup and view all the answers

<p>Data warehousing, data mining, and business intelligence</p> Signup and view all the answers

<p>To optimize the performance of SQL queries</p> Signup and view all the answers

<p>Relational database management system (RDBMS) or NoSQL database</p> Signup and view all the answers

<p>False</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>False</p> Signup and view all the answers

<p>False</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>False</p> Signup and view all the answers

<p>False</p> Signup and view all the answers

<p>PostgreSQL v13.4</p> Signup and view all the answers

<p>Leverage basic PostgreSQL commands</p> Signup and view all the answers

<p>SQL API</p> Signup and view all the answers

<p>To connect to the repository</p> Signup and view all the answers

<p>REST API is more reliable</p> Signup and view all the answers

<p>Managed cloud edition</p> Signup and view all the answers

<p>To connect to the repository</p> Signup and view all the answers

<p>To provide a reliable API</p> Signup and view all the answers

<p>REST API</p> Signup and view all the answers

<p>Leverage basic PostgreSQL commands</p> Signup and view all the answers

<p>Performing ad-hoc queries and debugging</p> Signup and view all the answers

<p>Access to the full history of metadata</p> Signup and view all the answers

<p>Interface schemas and raw metadata</p> Signup and view all the answers

<p>Data Vault 2.0</p> Signup and view all the answers

<p>Limited to the current metadata</p> Signup and view all the answers

<p>Existing entities are frequently modified or removed</p> Signup and view all the answers

<p>Performing ad-hoc queries and debugging</p> Signup and view all the answers

<p>More stable interface for modifying data</p> Signup and view all the answers

<p>Designed for ad-hoc querying</p> Signup and view all the answers

<p>Read-only access</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>False</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>False</p> Signup and view all the answers

<p>True</p> Signup and view all the answers

<p>False</p> Signup and view all the answers

<p>False</p> Signup and view all the answers

<p>False</p> Signup and view all the answers

<p>SQL API = Provides access to the full history of all available metadata extracted from the sources REST API = Limited to the current metadata and provides no history Interface Schemas = Simplify the access to the various frontend and backend components of Flow.BI Data Vault 2.0 model = Fully integrated and versionized raw metadata from the client’s source applications and pre-processed data</p> Signup and view all the answers

<p>SQL API = Less stable than the REST API REST API = Limited to the current metadata and not designed for ad-hoc querying</p> Signup and view all the answers

<p>The SQL API is an alternative to the REST API = True The SQL API is primarily used for ad-hoc queries and debugging = True The REST API is a more stable interface into the Flow.BI metadata = True The SQL API provides SQL capabilities on the underlying database of the Flow.BI service = True</p> Signup and view all the answers

<p>SQL API = Ad-hoc queries and debugging REST API = Performing certain actions on the Flow.BI backend, including modifying the underlying data</p> Signup and view all the answers

<p>SQL API = Less stable than the REST API REST API = More stable than the SQL API</p> Signup and view all the answers

<p>The SQL API provides full access to the underlying metadata repository of the Flow.BI service = True The REST API is limited to the current metadata and therefore provides no history = True The SQL API provides SQL capabilities on the underlying database = True The REST API is not designed for ad-hoc querying = True</p> Signup and view all the answers

<p>Interface Schemas = Simplify the access to the various frontend and backend components of Flow.BI Data Vault 2.0 model = Contains fully integrated and versionized raw metadata from the client’s source applications and pre-processed data</p> Signup and view all the answers

<p>SQL API = Provides remote read-only access to the underlying database and is less stable than the REST API REST API = Limited to the current metadata and provides no history, not designed for ad-hoc querying</p> Signup and view all the answers

<p>SQL API = Ad-hoc queries and debugging, integration with certain projects REST API = Performing certain actions on the Flow.BI backend</p> Signup and view all the answers

<p>The SQL API provides access to the full history of all available metadata extracted from the sources = True The REST API is limited to the current metadata and therefore provides no history = True The SQL API provides SQL capabilities on the underlying database of the Flow.BI service = True The REST API is not designed for ad-hoc querying = True</p> Signup and view all the answers

<p>The SQL API in Flow.BI is provided as part of the service fees. = False Entities in the REST API are more likely to change than interface changes in the API. = True The SQL API is primarily used for ad-hoc queries and debugging. = True The REST API is limited to the current metadata and provides no history. = True</p> Signup and view all the answers

<p>SQL API = Provides SQL capabilities on the underlying database of the Flow.BI service REST API = Better option for integrating data-driven applications with Flow.BI Database engine = May be changed to another PostgreSQL compatible database in the future Greenplum = Hot candidate for the managed cloud edition in the future</p> Signup and view all the answers

<p>Amazon Aurora = Currently being used for PostgreSQL v13.4 PostgreSQL = Will most probably be used for on premises deployment Amazon Redshift = Potential future option for the underlying database engine H2 database = Can be used with PostgreSQL compatibility</p> Signup and view all the answers

<p>The SQL API in Flow.BI is provided under the expectation that the system is not overloaded. = True The SQL API is an alternative to the REST API. = True The REST API is a better option for integrating data-driven applications with Flow.BI. = True The SQL API provides a more reliable API compared to the REST API. = False</p> Signup and view all the answers

<p>SQL repositories are used to store and manage non-SQL objects. = False The SQL API is the better option for integrating data-driven applications with Flow.BI. = False The REST API provides access to function calls to perform certain actions on the Flow.BI backend. = True SQL repositories can only be used in data warehousing applications. = False</p> Signup and view all the answers

<p>The SQL API key is provided under API keys in the web interface. = True The SQL API key is provided in your profile in the web interface. = False The SQL API key is a random, yet static value. = True The SQL API key is the same as the user name provided in your profile. = False</p> Signup and view all the answers

<p>Host = The server where the repository is hosted Port = The network port on which the repository is listening Database = The specific repository instance being accessed User Name = The identity used to access the repository</p> Signup and view all the answers

<p>The REST API is limited to the current metadata and provides no history. = True The REST API is a better option for integrating data-driven applications with Flow.BI. = True The SQL API is primarily used for ad-hoc queries and debugging. = False The SQL API in Flow.BI is provided as part of the service fees. = False</p> Signup and view all the answers

<p>The underlying database engine in the Flow.BI repository may be changed to another PostgreSQL compatible database. = True Greenplum is a hot candidate for the managed cloud edition in the future. = True On Premises will most probably keep using PostgreSQL. = True The SQL API in Flow.BI provides a more reliable API compared to the REST API. = False</p> Signup and view all the answers

<p>The SQL API is experimental and only provided under the expectation that the system is not overloaded. = True Individual access to the SQL API may be revoked at any time, without warning, notice and reason. = True The SQL API is provided as part of any service fees. = False The SQL API is just a test and not guaranteed to be available. = True</p> Signup and view all the answers