TDVAN5 Vantage Administration Exam Practice Questions

The correct syntax to establish a proxy user relationship is GRANT CONNECT THROUGH TO ;. This command grants the permanent users (Alice, Bob) the ability to have their sessions proxied by the application user (AppUser). When the application connects as AppUser, it can then issue a SET QUERY_BAND PROXYUSER='Alice'; statement, and subsequent queries will be executed with Alice's identity and privileges.

Effective management of TPT jobs in TASM involves three key steps: 1. Classification (identifying the jobs via Utility Name), 2. Concurrency Control (limiting simultaneous jobs with a Utility Throttle), and 3. Execution Control (using a Filter to enforce time windows). These three controls provide comprehensive management over utility workloads.

The Data Mover Jobs portlet in Teradata Viewpoint is the dedicated tool for monitoring and managing Data Mover. It provides a comprehensive view of all Data Mover jobs, including their current status (e.g., running, completed, failed), progress indicators, execution times, and access to detailed job logs for troubleshooting.

The native JSON data type in Teradata Vantage is highly optimized for storing and querying JSON documents. It stores the data in a binary format (UBJSON) that allows for efficient traversal and extraction of nested values using a simple dot notation syntax. This is significantly faster than parsing text-based CLOB or VARCHAR data at query time. For frequent access to specific nested fields within a flexible schema, the native JSON type provides the best balance of performance and flexibility.

A Value-Ordered Non-Unique Secondary Index (NUSI) is the best choice for low-cardinality columns that are frequently used in range-based or equality predicates. Because region has low cardinality (e.g., a few distinct values), a standard NUSI would have long rows in the index subtable, making it inefficient. A Value-Ordered NUSI stores the pointers sorted by value, allowing the database to quickly locate all rows for a specific region. A Hash Index is for high-cardinality columns. A USI is not applicable as region is not unique.

False. While PERM space can be defined directly in the CREATE USER statement, it is also common practice to have users inherit their space allocation from a parent database. The syntax CREATE USER ... FROM will cause the new user to be created within the space of the parent database, sharing that allocation. This is a fundamental concept in Teradata's hierarchical space management.

Teradata Data Mover is the enterprise tool built specifically for intelligent, robust, and manageable data movement between Teradata systems. It handles the entire process, including extracting DDL, moving data efficiently, recreating objects on the target, and providing features like job scheduling, dependency management, automatic restart on failure, and comprehensive logging. While other methods could work, they would require significant custom development to achieve the same level of robustness.

CPUServ represents the CPU seconds used by tasks for the AMP. A high value is expected on a busy system. However, the key indicator for CPU contention is the RunQ, which represents the average number of tasks waiting for CPU resources on an AMP. A consistently high RunQ value alongside high CPUServ directly indicates that more work is arriving than the CPU can process, leading to queuing and increased response times. The other options mix CPU metrics with I/O or delay metrics, which are less direct for diagnosing CPU-specific queuing.

A workload filter is the correct TASM feature to inspect and reject queries before they execute. By creating a filter that specifically classifies on the query characteristic of a product join and is active only during the specified time window (via a Planned Environment), the administrator can precisely target and reject these harmful queries. Throttles limit concurrency but don't reject specific query types. Exceptions act on running queries, which is too late to prevent resource consumption.

The primary benefits of NOS are its ability to query data-in-place and its schema inference capabilities. It allows Vantage to act as a query engine over data residing in external object stores like S3, which avoids the time and cost of ETL and reduces storage redundancy. The ability to automatically infer schema from structured file formats like Parquet (using READ_NOS) greatly simplifies the setup process. NOS does not move data into perm space, nor does it provide ACID compliance for external data. It is a native feature and does not require QueryGrid.