매달, 우리는 1000명 이상의 사람들이 시험 준비를 잘하고 시험을 잘 통과할 수 있도록 도와줍니다.
Vantage Administration Exam 온라인 연습
최종 업데이트 시간: 2024년11월13일
당신은 온라인 연습 문제를 통해 NCR Teradata TDVAN5 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 TDVAN5 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 72개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
The table contains about two billion records and is exhibiting poor response time for range-based queries on the order date column, along with frequently projecting only 10 out of 100 columns. These factors indicate that the I/O (Input/Output) subsystem is under strain, as large amounts of data are being scanned and retrieved unnecessarily for each query.
Row and column partitioning can significantly reduce the amount of data that needs to be read from disk by limiting I/O to only the necessary partitions (rows) and columns, thus improving performance.
CPU might also be involved, but in this case, the primary concern appears to be I/O due to the large volume of data being retrieved and processed inefficiently.
AWT (AMP Worker Tasks) and Space are less likely to be the primary issues based on the problem description, as there is no mention of concurrency issues (AWT) or running out of space.
정답:
Explanation:
When using the NOS_READ function in Teradata to read data in CSV and JSON formats based on the LATIN character set, the maximum payload size that can be read is 32 MB. This limit ensures efficient processing and handling of large datasets, while also maintaining performance.
정답:
Explanation:
Filters in Teradata workload management allow the Administrator to define rules that restrict or block certain types of queries or connections based on specific criteria, such as the username, query client, or other attributes. In this case, the Administrator can use a filter to prevent queries from specific clients using the application's username, enforcing the security policy.
Option A (Flex Throttle) is used to manage query concurrency and system resources dynamically but is not designed to enforce security policies like user restrictions.
Option B (Utility Session) controls the number of utility sessions but does not help with filtering query clients based on usernames.
Option C (Exception) handles query workload exceptions based on certain thresholds or behaviors
but doesn't directly enforce user or client restrictions.
정답:
Explanation:
The Data Mover portlet in Viewpoint provides specific functionality for managing and monitoring Data Mover jobs. By accessing the log tab within the Data Mover portlet, the Administrator can review detailed logs, including the data volume that was transferred during the job execution.
Option A (Completed Queries portlet) focuses on monitoring and analyzing completed queries but does not provide detailed insights into Data Mover jobs.
Option C (Performance Data Collection portlet) is used for monitoring system performance but is not directly related to Data Mover job details or data transfer volumes.
Option D (datamove status command) is a CLI (Command-Line Interface) method to check job status, but it is not related to monitoring the data volume within the Viewpoint environment.
정답:
Explanation:
Inherited privileges are those that a user acquires based on their membership in a profile or role. In this case, the user has been assigned a profile that grants access to sensitive data, meaning the privilege to access that data is inherited through the profile.
Option B (Ownership) refers to the privileges that the creator (owner) of a database object has over that object, but in this case, the user is accessing data through a profile, not ownership.
Option C (Automatic) would suggest that the privilege is granted automatically without the need for an explicit assignment or inheritance, which doesn't apply here because the privileges are coming from a profile.
Option D (Assigned) refers to direct privileges granted to a user individually, but in this scenario, the user is accessing data through a profile, which means the privileges are inherited rather than directly assigned.
정답: 
정답:
Explanation:
TOTALIOCOUNT represents the total number of I/O operations a query performs, which is crucial when trying to identify queries consuming excessive I/O (in this case, more than 100 million IOs). This directly indicates the amount of I/O a query is generating.
PJI (Product Join Index) measures whether a product join is being performed in the query, which is often associated with inefficient joins that result in large redistributions of data. A high PJI value
indicates that the query might be performing a product join, leading to a significant performance hit due to large redistributions.
Option A (MAXAMPIO and PJI): MAXAMPIO refers to the maximum I/O performed by a single AMP, but TOTALIOCOUNT is a more direct indicator of the total I/O performed by a query across all AMPs. Option C (I/O SKEW % and UII): I/O SKEW % indicates uneven distribution of I/O, which can cause performance issues, but it does not directly measure the total I/O consumption like TOTALIOCOUNT does. UII (Utility Impact Index) is relevant but not as important for identifying large I/O queries. Option D (REQPHYSIO and UII): REQPHYSIO refers to the number of physical I/Os, but it is not as comprehensive as TOTALIOCOUNT, which includes both logical and physical I/O.
Thus, TOTALIOCOUNT (for total I/O) and PJI (to detect potential large redistributions due to product joins) are the key metrics to identify queries with high I/O and large redistributions.
정답:
Explanation:
In this scenario, the issue arises due to high concurrency of stored procedure calls, which are exhausting AWTs (AMP Worker Tasks). To address this, the administrator needs to throttle the specific stored procedure calls made by BATCH_USER. The most effective way to do this is to create a new workload that specifically targets those calls (statement type = CALL) from BATCH_USER and then applies a throttle to limit concurrency. This helps manage the system's AWTs by controlling how many stored procedures can be run concurrently.
Other options are less suitable as they either do not target stored procedures specifically or may not provide the necessary granularity in controlling AWT usage for stored procedure calls.
정답:
Explanation:
IO SKEW refers to an uneven distribution of I/O operations across AMPs, which can occur during large redistributions or full table scans, as data needs to be read from or written to the entire table. High IO skew indicates that some AMPs are handling significantly more I/O than others, which is often a sign of inefficient data distribution or full table scanning.
QRY_B has an IO SKEW value of 2.76, which is much higher than the other queries, suggesting that it is likely performing a full table scan or large redistribution, as this would result in uneven I/O across AMPs.
CPU SKEW (as seen in QRY_D) could indicate an issue with CPU load balancing, but it doesn't necessarily suggest a full table scan or redistribution.
UII (Utility Impact Index) and PJI (Product Join Index) are also metrics that might indicate query inefficiencies, but the high IO SKEW in QRY_B is the most direct indicator of a full table scan or large redistribution.
QRY_B is the query suspected of causing the full table scan or large redistribution due to its high IO SKEW value.
정답:
Explanation:
In Teradata's Native Object Store, the AUTHORIZATION object stores shared credentials (such as an S3 IAM role, Azure SAS token, or other cloud storage credentials). By granting users access to this shared authorization object, the administrator can allow multiple users to access the object store using the same set of credentials. This simplifies credential management and ensures secure access to the external data source.
Option A (Define a FOREIGN TABLE with DEFINER TRUSTED security) refers to defining a foreign table with a specific security model but does not handle shared credentials directly.
Option B (Define a FUNCTION MAPPING with INVOKER TRUSTED security) relates to function mappings and security contexts for user-defined functions, not directly to shared credentials for accessing an object store.
Option C (Use an S3 IAM role or Azure SAS token rather than User and Password) is a part of how credentials might be managed, but it does not address the mechanism for sharing these credentials among users. The AUTHORIZATION object is the correct method for managing and sharing these credentials securely.
정답:
Explanation:
The GRANT CONNECT THROUGH statement allows the TrustedUser to act on behalf of multiple end users while securely connecting to the database. By granting both roles (Finance and Human Resources) in this statement, you allow the ProxyUser to switch between roles depending on the query band's ProxyRole value.
Using the ProxyRole query band, the application can specify which role (Finance or Human Resources) should be used for each specific request. This approach provides flexibility, as the application can dynamically assign the appropriate role to the user based on the query context. Option A (Defining roles as external and using ProxyRole) wouldn't fully address the need to manage multiple roles dynamically for a shared server.
Option B (Granting both roles to TrustedUser) doesn't allow for flexible role switching on a per-request basis without the use of GRANT CONNECT THROUGH and could lead to over-granting of permissions.
Option C (Specifying a role for each end user in GRANT CONNECT THROUGH) isn't as flexible as allowing both roles to be used and dynamically selected through the query band.
Thus, Option D is the most appropriate solution, as it provides both security and flexibility, enabling the application to use the correct role based on the ProxyRole query band for each query submitted.
정답:
Explanation:
QryLogUtilityV is a specific DBQL (Database Query Logging) view that provides information about utility usage (such as Multiload and FastLoad) on the system. Since the BEGIN QUERY LOGGING WITH ALL ON ALL command was issued two years ago, the DBQL (Database Query Logging) has been tracking various events, including utility usage, which is stored in QryLogUtilityV.
Option A (AMPUsageV) contains AMP (Access Module Processor) level statistics and usage data but not detailed information about utility jobs.
Option B (LogOnOffV) tracks user logon and logoff activities but does not provide information about utility usage.
Option D (QryLogV) logs general query execution data but is not specifically focused on utility usage.
정답:
Explanation:
In the given CREATE USER statement, the SKEW = 10 PERCENT parameter applies to Perm space and allows some AMPs (Access Module Processors) to use up to 10% more space than the average allocation across the AMPs.
The user is allocated 100 GB of Perm space across a 10-AMP system, meaning the average space per AMP is 10 GB.
With a 10% skew allowed, this means that an AMP can use up to 10% more than the average allocation, which is 10 GB + 1 GB = 11 GB.
정답:
Explanation:
The Flex Throttle option allows the system to temporarily adjust workload concurrency limits based on system conditions. This provides more flexibility when handling spikes in query concurrency, without permanently modifying the established workload limits. Flex Throttle is ideal for handling temporary peaks in activity, helping to smooth out delays while keeping the core concurrency limits intact.
Option A (Use a system throttle) would enforce strict concurrency limits but doesn't provide the flexibility needed in this scenario, where the client is trying to avoid modifying existing limits. Option B (Use Query Group Viewpoint portlet to change the throttle limit temporarily) suggests manually adjusting the throttle limit, which is not desirable in this case as the limits have been carefully chosen.
Option D (Use Query Monitor Viewpoint portlet to change query workloads) would involve changing the way queries are handled or prioritized but does not address the need to keep concurrency limits unchanged while still dealing with temporary delays.
Thus, Flex Throttle (Option C) provides the best solution to assist the client without altering the concurrency limits permanently.
정답:
Explanation:
DBC.USERSV contains information about users, including the passwordlastmodified column, which records the date and time the user last changed their password. By querying this view, the Administrator can identify users who have not updated their password within the specified time frame (in this case, 90 days).
Option A (DBC.LOGONOFFV) logs user logon and logoff events, but it does not track password changes.
Option C (DBC.SECURITYDEFAULTSV) contains system-wide security defaults, but it does not track individual user password activity.
Option D (DBC.ACCESSLOGV) logs access control events, like who accessed which database objects, but it doesn't track password changes either.
Therefore, DBC.USERSV is the appropriate view to use for this task.