The BEGIN QUERY LOGGING WITH ALL ON ALL; command enables comprehensive logging, which includes data on utility jobs. The QryLogUtilityV view is specifically designed to provide detailed information about the execution of Teradata utilities such as FastLoad and MultiLoad. This view contains data on utility phases, row counts, and resource consumption, which is exactly what the administrator needs to analyze past usage patterns and project future resource requirements for these specific jobs.

A. AMPUsageV: This view provides aggregated AMP-level resource usage (CPU/IO) but does not attribute this usage to specific utility jobs like FastLoad or MultiLoad.

B. LogOnOffV: This view only contains records of user session logon and logoff events. It does not provide any details about the activities or utilities run during those sessions.

D. QryLogV: This view logs details about SQL queries submitted to the system. While utilities generate SQL, this view does not provide the specific, consolidated summary of the utility job itself.

1. Teradata Vantage™ - Data Dictionary, Release 17.20, B035-1092-172K.

Section: Chapter 2: Data Dictionary Views, "QryLogUtilityV"

Content: "The QryLogUtilityV view... provides information from the QryLogUtilityTbl. The QryLogUtilityTbl contains one row for each phase of a Teradata utility job." This directly supports that utility-specific data is found in this view.

2. Teradata Vantage™ - SQL Data Definition Language Syntax and Examples, Release 17.20, B035-1144-172K.

Section: Chapter 2: SQL Data Definition Language, "BEGIN QUERY LOGGING"

Content: The WITH ALL option in the BEGIN QUERY LOGGING statement is a comprehensive setting that includes the functionality of WITH UTILITYINFO. The UTILITYINFO option explicitly "Logs a row to DBC.QryLogUtilityTbl for each utility phase." This confirms the logging was enabled for the required view.

3. Teradata Vantage™ - Database Administration, Release 17.20, B035-1093-172K.

Section: Chapter 12: Logging Query, Error, and Event Information, "Utility Logging"

Content: "DBQL logs information on the following Teradata utilities... FastLoad... MultiLoad... The information is logged in the DBC.QryLogUtilityTbl table and can be accessed through the QryLogUtilityV view." This explicitly links the required utilities to the correct view.

The Teradata Viewpoint Data Mover portlet is the designated interface for managing and monitoring Data Mover jobs. When a job is selected within this portlet, several tabs become available to provide detailed information. The 'Log' tab specifically displays the contents of the job's log file. This log contains a comprehensive record of the job's execution, including the number of rows processed and the total data volume (bytes) read and written, thereby allowing an administrator to monitor the amount of data transferred.

A. The Completed Queries portlet tracks executed SQL queries. A Data Mover job is a utility process, not a single query, so its specific transfer volume statistics are not found here.

C. The Performance Data Collection portlet is used for analyzing historical system performance data (PDCR), not for monitoring the specific, real-time metrics of an individual Data Mover job.

D. The datamove status command is a command-line interface (CLI) utility. The question explicitly requires a method to monitor the job via Viewpoint, making this option incorrect.

1. Teradata® Viewpoint User Guide, Release 16.20. In the chapter "Standard Portlets," the section on the "Data Mover" portlet describes its functionality. It details that after selecting a job, the "Log" tab can be used to view the job's log file, which contains detailed execution statistics. (Reference: B035-2206-162K, Chapter 10: Standard Portlets, "Data Mover," Page 315).

2. Teradata® Data Mover User Guide, 16.20. This guide explains the contents of the job log files. It specifies that the log file contains detailed information about the job execution, including "Total bytes read" and "Total bytes written," which represent the data volume transferred. The Viewpoint portlet provides a direct view of this log. (Reference: B035-2034-162K, Chapter 5: Monitoring Data Mover Jobs, "Job Log Files," Page 78).

In the Teradata security model, the database or user that contains an object is considered its immediate owner. This ownership confers all privileges on that object automatically and implicitly. For example, the Sales database inherently has all privileges (SELECT, INSERT, etc.) on the Sales.Products table. These ownership privileges are fundamental to the system and do not require an explicit GRANT statement to be issued. The system automatically recognizes the owner's rights to the objects within its space.

A. Granting a privilege at any level is an explicit action that is always recorded as a new row in the DBC.AccessRights system table.

B. A database-level grant creates a single entry in DBC.AccessRights for the database itself; this privilege is then implicitly applied to all objects within it, not by creating separate rows for each object.

D. Users who create objects are the owners of those objects and, by virtue of ownership, automatically possess all privileges on them without needing separate grants.

1. Teradata Vantage™ - Security Administration, B035-1100-162K, April 2021.

Page 30, "Owner Privileges": "The immediate owner of an object is the database or user in which the object is created. The immediate owner of an object automatically holds all privileges on that object. These privileges are implicit and are not recorded in the DBC.AccessRights table." (Supports correct answer C and refutes D).

2. Teradata Vantage™ - SQL Data Control Language, B035-1149-162K, April 2021.

Page 100, "Usage Notes for GRANT (SQL Form)": "When you grant a privilege on a database or user, the privilege applies to all existing and future objects in that database or user space." (Refutes B's assertion of individual row insertion for each object).

Page 21, "Access Logging": "The AccessRights table contains one row for each explicit privilege granted on a database object." (Refutes A, as any explicit grant is recorded).

The DBC.AccessLogV view provides access to the access log table (DBC.AccessLogTbl). This table records information about user requests for which access logging has been enabled via the BEGIN LOGGING statement. Each entry in this view contains details about a specific request, including the user, the object accessed, the time of the request, and, crucially, the status of the privilege check. The Status and ErrorCode columns indicate whether access was granted or denied due to insufficient privileges, making it the definitive source for reviewing privilege checks.

A. DBC.UserRightsV: This view lists the current access rights granted to users and roles. It does not contain a historical log of individual access attempts or privilege checks.

B. DBC.AccLogRulesV: This view displays the logging rules that are currently active. It shows what is being logged, not the actual log entries resulting from those rules.

C. DBC.AllRightsVX: Similar to UserRightsV, this view provides a comprehensive list of all granted rights on all database objects but does not log the checks for specific requests.

1. Teradata Vantage™ - Data Dictionary, Release 17.20, Document ID: B035-1092-172K, Chapter 2: "DBC Table and View Descriptions".

Page 51, "AccessLogV (Access Log View)": "This view provides access to the rows of DBC.AccessLogTbl... The access log table, DBC.AccessLogTbl, contains information about all requests for which access logging is enabled." The column descriptions for Status, ErrorCode, and ErrorText confirm it logs the outcome of privilege checks.

Page 49, "AccLogRulesV (Access Logging Rules View)": "This view provides user-accessible information about the access logging rules currently in effect."

Page 100, "AllRightsVX (All Rights View)": "This view lists all the rights that have been granted on all database objects."

Page 818, "UserRightsV (User Rights View)": "This view lists the rights that have been granted on all database objects."

In Teradata Vantage, the AUTHORIZATION object is the designated mechanism for storing credentials used to access external systems, including Native Object Stores (NOS). To facilitate shared access, an administrator creates a single AUTHORIZATION object containing the required credentials. Subsequently, the administrator grants the USAGE privilege on this specific AUTHORIZATION object to the relevant end-users or roles. When these users query a foreign table that references this AUTHORIZATION object, Teradata Vantage uses the stored, shared credentials to access the data in the object store. This centralizes credential management and provides a secure method for shared access.

A. Define a FOREIGN TABLE with DEFINER TRUSTED security.

A FOREIGN TABLE references an AUTHORIZATION object for credentials. The table definition itself does not store or share the credentials; the AUTHORIZATION object does.

B. Define a FUNCTION MAPPING with INVOKER TRUSTED security.

FUNCTION MAPPING is not the standard object for this purpose. Furthermore, INVOKER security uses the end-user's credentials, which contradicts the requirement for shared credentials.

C. Use an S3 IAM role or Azure SAS token rather than User and Password.

This describes types of credentials that can be stored in an AUTHORIZATION object but does not explain the Teradata mechanism for sharing them among users.

1. Teradata Vantage™ - Native Object Store Getting Started Guide, B035-1214-062K, Chapter 2: Getting Started with Native Object Store, Section: Authorization Objects. The documentation states, "The AUTHORIZATION object stores the credentials that Vantage uses to access the object store... To use an authorization object that you do not own, you must have the USAGE privilege on the object."

2. Teradata Vantage™ SQL Data Definition Language Syntax and Examples, B035-1144-162K, Chapter 4: Data Definition Statements, Section: CREATE AUTHORIZATION. This section details the syntax for creating the object that holds credentials for external servers.

3. Teradata Vantage™ SQL Data Control Language, B035-1149-162K, Chapter 2: Grant and Revoke, Section: GRANT (Object Privilege Form). This document specifies that the USAGE ON AUTHORIZATION privilege allows a user to use the specified authorization object to access external data. This is the mechanism for sharing.