Cisco®
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
Scrum
All Vendors
  2. Home
  3. Exams
  4. TeraData
  5. TDVAN5

Free TDVAN5 Exam Braindumps (page: 2)

Page 1 of 19
PDF with 72 Questions

There is a call center application that repetitively sends tactical queries to Vantage These queries use a few small tables that are joined on the primary index column.
The following maps are defined in the system:
* TD_GlobalMap
* TD_Map1
* TD_DataDictionaryMap
* TD_1AmpSparseMap_1Node
What can be done to optimize these queries?

  1. Assign these tables to TD_1AmpSparseMap_1Node using different colocation names for each table.
  2. Assign these tables to TD_1AmpSparseMap_1Node using the same colocation name for every table
  3. Assign these tables to TD_Map1 using the same colocation name for every table.
  4. Assign these tables to TD_Map1 using different colocation names for each table.

Answer(s): B

Explanation:

Example:

TD_1AmpSparseMap_1Node is a sparse map that assigns the data to a single AMP (or a few AMPs), and using the same colocation name ensures that the tables are collocated on the same AMP. This helps in efficient joining because no data redistribution is required between AMPs when tables are joined on the primary index.
Using different colocation names for each table (options A and D) would place the tables on different AMPs, leading to less efficient joins since data would need to be shuffled between AMPs. TD_Map1 is a predefined map in the system but does not specifically optimize small, frequently accessed tables in the same way that TD_1AmpSparseMap_1Node does, which is more suitable for these scenarios.
Thus, using the same colocation name within the TD_1AmpSparseMap_1Node ensures that the joins are AMP-local, optimizing the repetitive tactical queries.



Which workload management technique should the Administrator use to reject all QueryGrid queries during a pre-defined critical batch state?

  1. An exception that includes the following Foreign Servers:
    TD_SYSFNLIB.QGInitiatorExport
    TD_SYSFNLIB.QGInitiatorlmport
    TD_SYSFNLIB.QGRemoteExport
    TD_SYSFNLIB.QGRemotelmport
  2. A filter that includes the following functions:
    TD_SYSFNLIQGInitiatorExport
    TD_SYSFNLIQGInitiatorlmport
    TD_SYSFNLIQGRemoteExport
    TD_SYSFNLIQGRemotelmport
  3. An exception that excludes the following Foreign Servers:
    TD_SYSFNLIB.QGInitiatorExport
    TD_SYSFNLIB.QGInitiatorlmport
    TD_SYSFNLIB.QGRemoteExport
    TD_SYSFNLIB.QGRemotelmport
  4. A filter that excludes the following functions:
    TD_SYSFNLIB.QGInitiatorExport
    TD_SYSFNLIB.QGInitiatorlmport
    TD_SYSFNLIB.QGRemoteExport
    TD_SYSFNLIB.QGRemotelmport

Answer(s): A

Explanation:

In this case, using an exception with the Foreign Servers related to QueryGrid functions will prevent queries involving those foreign servers from running. This is a typical method to block or reject specific workloads during critical times, such as a batch processing window. Exceptions in workload management are used to define specific conditions under which queries or workloads should be rejected or managed differently. By including these QueryGrid-related functions in an exception, the administrator ensures that any QueryGrid queries involving the listed foreign servers will be rejected during the critical batch state. Options B and D, which mention filters, are not appropriate for rejecting queries. Filters are used for monitoring or routing purposes, not for outright rejection of workloads. Option C, which suggests excluding the foreign servers in an exception, would not achieve the goal, as this would mean those queries are not affected by the exception. The goal here is to include these functions in an exception to actively reject them.



A customer is complaining that the creation of a large table in the lab environment is getting stuck in the merge step. The customer is using the following command to create the table:
CREATE TABLE ... AS (SELECT * ...) WITH DATA
Which recommendation will help the merge step?

  1. A column that provides good distribution should be specified as PRIMARY INDEX.
  2. The MERGEBLOCKRATIO should be specified for the table to improve the data block merge operation.
  3. The table should be created with "CREATE TABLE ... AS (SELECT *...) WITH NO DATA", and afterwards, "INSERT ... SELECT *" should be used to fill the table.
  4. Users of the lab may have lower priority than other workloads, so the creation of the table should be moved to off-peak hours.

Answer(s): C

Explanation:

Merge step issues often occur when a large amount of data is being processed during the table creation, especially if the system is trying to simultaneously create the table and insert data. By using "WITH NO DATA", the table structure is created first, without the actual data being inserted during the table creation process. The *"INSERT ... SELECT " command can then be used afterwards to populate the table in a more controlled way, reducing the load on the system during the creation phase and potentially improving the efficiency of the merge step. Specifying a good distribution for the primary index can help overall performance, but it doesn't directly address the issue with the merge step in this scenario. Specifying the MERGEBLOCKRATIO isn't typically a solution for this specific problem; the merge block ratio is more about the optimization of data block merges rather than the creation of tables. Moving the creation to off-peak hours may help if the environment is busy, but it doesn't directly address the core issue of the merge step getting stuck.



Which benefit is achieved by creating profiles?

  1. Reducing the growth of the DBC.AccessRights table
  2. Managing user privileges on database objects
  3. Assigning permanent space for groups of users with similar needs
  4. Defining spool space for groups of users with similar needs

Answer(s): D

Explanation:

Profiles in Teradata are used to manage and enforce resource limits for groups of users. This includes defining spool space, temporary space, and permanent space for users who share similar needs. Spool space is important for query processing, and managing it by profile helps prevent individual users from consuming excessive resources and ensures better overall system performance. Reducing the growth of the DBC.AccessRights table is not directly related to profiles. Profiles do not reduce access rights or the growth of this table, which tracks individual user privileges. Managing user privileges on database objects is handled through roles and grants, not profiles. Profiles focus on resource management, not privileges. Assigning permanent space for groups of users is partially true since profiles can manage some space attributes, but the main focus of profiles is on managing spool space rather than permanent space.






Post your Comments and Discuss TeraData TDVAN5 exam with other Community members: