2024年最新の有効なQREP試験最新問題で2024年最新の学習ガイド
QREP認定で究極のガイド [2024年更新]
Qlik QREP 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
質問 # 11
Which two components are responsible for reading data from the source endpoint and writing it to the target endpoint in Full Load replication? (Select two.)
- A. TARGET_UNLOAD
- B. TARGET_LOAD
- C. TARGET_APPLY
- D. SOURCE_UNLOAD
- E. SOURCE_CAPTURE
正解：B、D
解説：
The SOURCE_UNLOAD component is responsible for reading data from the source endpoint.
The TARGET_LOAD component is responsible for writing the data to the target endpoint.
These components work in tandem during the Full Load replication process to move data from the source to the target. According to Qlik Replicate documentation, these two components are crucial in handling the extraction and loading phases of Full Load replication.
In the context of Full Load replication with Qlik Replicate, the components responsible for reading data from the source and writing it to the target are:
SOURCE_UNLOAD: This component is responsible for unloading data from the source endpoint.It extracts the data that needs to be replicated to the target system1.
TARGET_LOAD: This component is in charge of loading the data into the target endpoint.After the data is extracted by the SOURCE_UNLOAD, the TARGET_LOAD component ensures that the data is properly inserted into the target system1.
The other options provided do not align with the Full Load replication process:
B; TARGET_APPLYandD. SOURCE_CAPTUREare typically associated with the Change Data Capture (CDC) process, not the Full Load process2.
C: TARGET_UNLOADis not a recognized component in the context of Qlik Replicate's Full Load replication.
Therefore, the correct answers areA. SOURCE_UNLOADandE. TARGET_LOAD, as they are the components that handle the reading and writing of data during the Full Load replication process12.
質問 # 12
Which types of notifications can be set up in Qlik Replicate?
- A. Task Events and Endpoint Events
- B. Server Events and Endpoint Events
- C. Server Events. Endpoint Events, and Task Events
- D. Task Events and Server Events
正解：C
解説：
In Qlik Replicate, notifications can be set up for various events related to tasks, endpoints, and the server itself. The types of notifications that can be configured include:
Task Events: Notifications for task-based events, such as when a task starts or stops, when latency is too high, or when specific errors occur1.
Endpoint Events: While the search results did not explicitly mention "Endpoint Events," it is common in replication tools to have notifications related to endpoints, such as connectivity issues or endpoint-specific errors.
Server Events: Notifications related to the server, which could include system state changes, performance issues, or server-level errors2.
Therefore, the correct answer isC. Server Events, Endpoint Events, and Task Events, as Qlik Replicate allows setting up notifications for all these types of events. This ensures that administrators are alerted to a wide range of potential issues, allowing for prompt response and resolution.
For detailed instructions on how to set up each type of notification in Qlik Replicate, you can refer to the official Qlik documentation, which provides step-by-step guidance on defining and managing notifications for task events, server events, and other significant occurrences within the replication environment132.
質問 # 13
What is the directory for the ODBC drivers in Qlik Replicate?
- A. \Replicate\drivers
- B. \Replicate\users
- C. \Replicate\bin
- D. \Replicate\data
正解：C
解説：
The ODBC drivers in Qlik Replicate are located in the\Replicate\bindirectory.This is supported by the documentation from Qlik, which indicates that when installing required clients such as the Microsoft ODBC Driver for SQL Server, the working directory should be changed to<product_dir>/bin1.Additionally, for other prerequisites involving driver locations, the instructions also refer to changing the working directory to<Replicate-Install-Dir>/bin23. This consistent reference to the\bindirectory across different parts of the Qlik Replicate documentation verifies that the ODBC drivers are indeed located in the\Replicate\bindirectory.
質問 # 14
An operative database can only commit two engines to Qlik Replicate (or initial loads at any given time. How should the task settings be modified?
- A. Apply Change Processing Tuning and increase the Apply batched changes intervals to 60 seconds
- B. Apply Full Load Settings to limit the number of engines to two.
- C. Apply Full Load Tuning to read a maximum number of tables not greater than two.
- D. Qlik Replicate tasks only load one table at a time by default, so the task settings do not need to be modified.
正解：B
解説：
In a scenario where an operative database can commit only two engines to Qlik Replicate for initial loads, the task settings should be modified to ensure that no more than two tables are loaded at any given time. This can be achieved by:
C: Apply Full Load Settings to limit the number of engines to two: This setting allows you to specify the maximum number of concurrent table loads during the Full Load operation.By limiting this number to two, you ensure that the operative database's capacity is not exceeded1.
The other options are not suitable because:
A: Apply Change Processing Tuning: This option is related to the CDC (Change Data Capture) phase and not the initial Full Load phase. Increasing the apply batched changes interval would not limit the number of engines used during the Full Load.
B: Qlik Replicate tasks only load one table at a time by default: This statement is not accurate as Qlik Replicate can be configured to load multiple tables concurrently, depending on the task settings.
D: Apply Full Load Tuning to read a maximum number of tables not greater than two: While this option seems similar to the correct answer, it is not a recognized setting in Qlik Replicate's configuration options.
For detailed guidance on configuring task settings in Qlik Replicate, particularly for managing the number of concurrent loads, you can refer to the official Qlik community articles onQlik Replicate Task Configuration Options.
質問 # 15
A Qlik Replicate administrator will use Parallel load during full load Which three ways does Qlik Replicate offer? (Select three.)
- A. User chooses a list of columns and set of values that define ranges
- B. Select specific tables and columns
- C. Use Time and Date Ranges in the date and time columns
- D. Use Partitions - Specify partitions\sub-partitions
- E. Use Data Ranges
- F. Use Partitions - Use all partitions - Use main\sub-partitions
正解：D、E、F
解説：
Qlik Replicate offers several methods for parallel load during a full load process to accelerate the replication of large tables by splitting the table into segments and loading these segments in parallel. The three primary ways Qlik Replicate allows parallel loading are:
Use Data Ranges:
This method involves defining segment boundaries based on data ranges within the columns.
You can select segment columns and then specify the data ranges to define how the table should be segmented and loaded in parallel.
Use Partitions - Use all partitions - Use main/sub-partitions:
For tables that are already partitioned, you can choose to load all partitions or use main/sub-partitions to parallelize the data load process. This method ensures that the load is divided based on the existing partitions in the source database.
Use Partitions - Specify partitions/sub-partitions:
This method allows you to specify exactly which partitions or sub-partitions to use for the parallel load. This provides greater control over how the data is segmented and loaded, allowing for optimization based on the specific partitioning scheme of the source table.
These methods are designed to enhance the performance and efficiency of the full load process by leveraging the structure of the source data to enable parallel processing
質問 # 16
Which are the mainhardware components to run a Qlik Replicate Task in a high performance level?
- A. RAM. Network bandwidth
- B. Cores.RAM
- C. SSD. RAM
- D. Cores. SSD. Network bandwidth
正解：D
解説：
To run a Qlik Replicate Task at a high-performance level, the main hardware components that are recommended include:
Cores: A higher number of cores is beneficial for handling many tasks running in parallel and for prioritizing full-load performance1.
SSD (Solid State Drive): SSDs are recommended for optimal performance, especially when using a file-based target or dealing with long-running source transactions that may not fit into memory1.
Network bandwidth: Adequate network bandwidth is crucial to handle the data transfer requirements, with 1 Gbps for basic systems and 10 Gbps for larger systems being recommended1.
The other options do not encompass all the recommended hardware components for high-performance levels in Qlik Replicate tasks:
A: SSD, RAM: While these are important, they do not include the network bandwidth component.
B: Cores, RAM: This option omits the SSD, which is important for disk performance.
D: RAM, Network bandwidth: This option leaves out the cores, which are essential for processing power.
For detailed hardware recommendations for different scales of Qlik Replicate systems, you can refer to the official Qlik documentation onRecommended Hardware Configuration.
質問 # 17
Which three task types does Qlik Replicate support? (Select three.)
- A. LogStream full load
- B. Full load, apply, and store change
- C. Store changes bidirectional
- D. LogStream store changes
- E. Scheduled full loads
- F. LogStream to Staging Folder
正解：A、B、F
解説：
Qlik Replicate supports a variety of task types to accommodate different data replication needs. The three task types supported are:
LogStream to Staging Folder (A): This task type allows Qlik Replicate to save data changes from the source database transaction log to a staging folder.These changes can then be applied to multiple targets1.
Full load, apply, and store change (E): This is a comprehensive task type that includes a full load of the source database, applying changes to the target, and storing changes in an audit table on the target side1.
LogStream full load (F): Similar to the LogStream to Staging Folder, this task type involves saving data changes from the source database transaction log.However, it also includes a full load of the data to the target database1.
The other options provided do not align with the task types supported by Qlik Replicate:
B: Store changes bidirectional: While Qlik Replicate supports bidirectional tasks, the option as stated does not accurately describe a supported task type.
C: LogStream store changes: This option is not clearly defined as a supported task type in the documentation.
D: Scheduled full loads: Although Qlik Replicate can perform full loads, "Scheduled full loads" as a specific task type is not mentioned in the documentation.
Therefore, the verified answers areA,E, andF, as they represent the task types that Qlik Replicate supports according to the official documentation1.
質問 # 18
Which is the command to export the task, task name Oracle_2_SS_Target1 using REPCTL?
- A. repct1 exportrepository task=Oracle_2_SS_Target1
- B. repct1 exporttask task=0racle_2_SS_Target1
- C. repct1 export task-Oracle_2_SS_Target1
- D. repct1 export_task task=Oracle_2_SS_Target1
正解：C
解説：
To export a task using REPCTL in Qlik Replicate, the correct command isrepctlexportrepository task=task_name. Here's how you would use it for the task named Oracle_2_SS_Target1:
Open the command-line console on the machine where Qlik Replicate is installed.
Use the REPCTL utility with theexportrepositorycommand followed by thetaskparameter and the name of the task you want to export.
The correct syntax for the command is:
repctl exportrepository task=Oracle_2_SS_Target1
This command will create a JSON file containing the exported task settings1.
The other options provided have either incorrect syntax or misspellings:
Ahas a typo in the command (repct1instead ofrepctl).
Buses an incorrect command (export_taskis not a valid REPCTL command).
Dhas a typo in the task name (0racle_2_SS_Target1instead ofOracle_2_SS_Target1) and an incorrect command (exporttaskis not a valid REPCTL command).
Therefore, the verified answer isC, as it correctly specifies the REPCTL command to export the task named Oracle_2_SS_Target11.
質問 # 19
Which logging level should be used to identify the internal command that Qlik Replicate Is executing prior to an error?
- A. Verbose
- B. Trace
- C. Errors
- D. Warnings
正解：B
解説：
To identify the internal commands that Qlik Replicate is executing prior to an error, theTracelogging level should be used.This level provides detailed information about the operations being performed by Qlik Replicate, including the internal commands executed before an error occurs1.
Here's how the Trace logging level works in Qlik Replicate:
When logging is set toTrace, the log lines are identified with]T:.This indicates that the log will include detailed trace information about the internal workings of Qlik Replicate, such as sending control records to components or waiting for termination of threads1.
The Trace level is more detailed than Warnings (]W:) and Errors (]E:), which only show warning and error messages without the detailed context of the operations leading up to them1.
The Trace level is also distinct from Verbose (]V:), which provides even more detailed logging information but may not be necessary for identifying the commands leading up to an error1.
Therefore, the correct answer isC. Trace, as it is the appropriate logging level to use when you need to analyze the actions performed by Qlik Replicate just before an error occurs1.
質問 # 20
Which is the minimum level of permissions required for a user to delete tasks?
- A. Admin
- B. Viewer
- C. Designer
- D. Operator
正解：C
解説：
According to the Qlik Replicate documentation, the minimum level of permissions required for a user to delete tasks is the Designer role. The predefined roles in Qlik Replicate come with different sets of permissions. The Admin and Designer roles have the permission to delete tasks, while the Operator and Viewer roles do not1.
Here's a breakdown of the permissions for each role related to task management:
Admin: Can create, design, and delete tasks.
Designer: Can create, design, and delete tasks.
Operator: Can perform runtime operations like start, stop, or reload targets but cannot delete tasks.
Viewer: Can view task history and other details but cannot perform task management operations like deleting tasks.
質問 # 21
The Qlik Replicate developer notices that errors occur about the duplicate key when applying INSERT.
Which should be done in order to identify this Issue?
- A. Stop task and enable the Apply Exceptions control table
- B. Stop and reload the task
- C. Check the error message in the Apply Exceptions control table
- D. Stop and resume the task
正解：C
解説：
When a Qlik Replicate developer encounters errors about a duplicate key when applying INSERT, the first step to identify and resolve the issue is to:
A: Check the error message in the Apply Exceptions control table: This control table contains detailed information about any exceptions that occur during the apply process, including duplicate key errors.By examining the error messages, the developer can understand the cause of the issue and take appropriate action to resolve it1.
The process involves:
Accessing the Qlik Replicate Console.
Navigating to the task that is experiencing the issue.
Opening the Apply Exceptions control table to review the error messages related to the duplicate key issue.
Analyzing the error details to determine the cause, such as whether it's due to a source data problem or a target schema constraint.
The other options are not the correct initial steps for identifying the issue:
B: Stop and reload the task: This action might temporarily bypass the error but does not address the root cause of the duplicate key issue.
C: Stop task and enable the Apply Exceptions control table: The Apply Exceptions control table should already be enabled and checked for errors as the first step.
D: Stop and resume the task: Resuming the task without identifying the cause of the error will likely result in the error reoccurring.
For more information on how to troubleshoot and handle duplicate key errors in Qlik Replicate, you can refer to the official Qlik community articles and support resources that provide guidance on error handling and the use of the Apply Exceptions control table2.
質問 # 22
A Qlik Replicate administrator needs to configure Oracle as a source endpoint before running a task in Qlik Replicate Which are three key prerequisites? (Select three.)
- A. Enable supplemental logging
- B. Enable ARCHIVELOG mode
- C. Complete a full backup of the source
- D. Install the Oracle Instant Client
- E. Configure Oracle Recovery Model
- F. Provide Oracle read-only privileges
正解：A、B、D
解説：
When configuring Oracle as a source endpoint for Qlik Replicate, there are several key prerequisites that need to be met:
Enable supplemental logging (A): Supplemental logging is crucial for capturing the changes in the Oracle database accurately, especially for Change Data Capture (CDC) operations.It ensures that all necessary column data is logged for replication purposes1.
Install the Oracle Instant Client (B): The Oracle Instant Client provides the necessary libraries for Qlik Replicate to connect to and interact with the Oracle database.It's required for the proper functioning of Qlik Replicate2.
Enable ARCHIVELOG mode (D): ARCHIVELOG mode is necessary for the Oracle database to archive redo logs, which Qlik Replicate uses to capture changes.This mode allows the database to continue functioning and preserve the logs even after a log switch, which is essential for CDC1.
The other options provided are not listed as key prerequisites for configuring Oracle as a source endpoint in Qlik Replicate:
C: Complete a full backup of the source: While it's a good practice to have a backup, it's not a prerequisite for configuring the source endpoint.
E: Provide Oracle read-only privileges: Read-only privileges might be necessary for certain operations, but they are not listed as a key prerequisite.
F: Configure Oracle Recovery Model: This is not mentioned as a prerequisite in the Qlik Replicate documentation.
Therefore, the verified answers areA,B, andD, as they represent the necessary steps to configure Oracle as a source endpoint in Qlik Replicate12.
質問 # 23
When working with Qlik Enterprise Manager, which component must be installed to run Analytics under Enterprise Manager?
- A. Qlik Compose and Replicate
- B. Qlik Replicate
- C. Qlik Compose
- D. PostgreSQL Database
正解：D
解説：
To run Analytics under Qlik Enterprise Manager, it is required to have aPostgreSQL Databaseinstalled.
This is because the Analytics data for Qlik Enterprise Manager is stored in a PostgreSQL database.Before using the Analytics feature, you must ensure that PostgreSQL (version 12.16 or later) is installed either on the Enterprise Manager machine or on a machine that is accessible from Enterprise Manager1.
Here are the steps and prerequisites for setting up Analytics in Qlik Enterprise Manager:
Install PostgreSQL: The setup file for PostgreSQL is included with Enterprise Manager, and it must be installed to store the Analytics data1.
Create a dedicated database and user: A dedicated database and user in PostgreSQL should be created, which will own the tables accessed by the Enterprise Manager Analytics module1.
Configure connectivity: Connectivity to the PostgreSQL repository must be configured as described in the Repository connection settings1.
Data collection and purging: Configure data collection and purging settings as described in the Analytics - Data collection and purge settings1.
Register a license: A Replication Analytics license is required to use Analytics.If you have a license, you can register it by following the procedure described in Registering a license1.
The other options provided, such as Qlik Replicate (A), Qlik Compose (B), and both Qlik Compose and Replicate (D), are not components that must be installed to run Analytics under Enterprise Manager.The essential component is the PostgreSQL Database , which serves as the backend for storing the Analytics data1.
Therefore, the verified answer isC. PostgreSQL Database, as it is the required component to run Analytics under Qlik Enterprise Manager1.
質問 # 24
In Qlik Enterprise Manager Analytics, which messages can be seen in the GUI?
- A. Task-specific trends, specify to a task
- B. Server and task trends
- C. Server settings
- D. Server-specific trends, specify to a task
正解：B
解説：
In the Qlik Enterprise Manager Analytics GUI, users can view messages related to both server and task trends. This includes:
Server-specific trends: These are metrics and trends related to the performance and usage of the servers, such as memory consumption and disk usage1.
Task-specific trends: These include metrics and trends specific to individual tasks, such as the number of tables and records processed, throughput, and the number of changes applied1.
Therefore, the correct answer isD. Server and task trends, as the Analytics tab in Qlik Enterprise Manager allows users to review trends over a specific time period for both servers and tasks.Users can filter the data to show information for a particular timeframe and for particular tasks, Replicate servers, source databases, and target databases2.
For more detailed information on the types of messages and trends that can be viewed in the Qlik Enterprise Manager Analytics GUI, you can refer to the official Qlik documentation onAnalytics dashboardsandAnalytics.
質問 # 25
Where are the three options in Qlik Replicate used to read the log files located? (Select three.)
- A. In Data directory of Installation
- B. In Windows Event log
- C. In Monitor of Qlik Replicate
- D. In Diagnostic package
- E. In External monitoring tool
- F. In Enterprise Manager
正解：A、C、D
解説：
In Qlik Replicate, the options to read the log files are located in the following places:
In Diagnostic package (B): The diagnostic package in Qlik Replicate includes various log files that can be used for troubleshooting and analysis purposes1.
In Data directory of Installation (D): The log files are written to the log directory within the data directory.This is the primary location where Qlik Replicate writes its log files, and it is not possible to change this location2.
In Monitor of Qlik Replicate (E): The Monitor feature of Qlik Replicate allows users to view and manage log files.Users can access the Log Viewer from the Server Logging Levels or File Transfer Service Logging Level sub-tabs1.
The other options provided do not align with the locations where log files can be read in Qlik Replicate:
A: In Windows Event log: This is not a location where Qlik Replicate log files are stored.
C: In External monitoring tool: While external monitoring tools can be used to read log files, they are not a direct feature of Qlik Replicate for reading log files.
F: In Enterprise Manager: The Enterprise Manager is a separate component that may manage and monitor multiple Qlik Replicate instances, but it is not where log files are directly read.
Therefore, the verified answers areB,D, andE, as they represent the locations within Qlik Replicate where log files can be accessed and read21.
質問 # 26
Which are valid source endpoint types for Qlik Replicate change processing (CDC)? (Select two )
- A. Classic Relational RDBMS
- B. Generic REST APIs Data Lake file formats
- C. SAP ECC and Extractors
- D. MS Dynamics direct access
正解：A、C
解説：
For Qlik Replicate's Change Data Capture (CDC) process, the valid source endpoint types include:
A: Classic Relational RDBMS: These are traditional relational database management systems that support CDC.Qlik Replicate can capture changes from these systems using log-based CDC tools which are integrated to work with most ETL tools1.
C: SAP ECC and Extractors: SAP ECC (ERP Central Component) and its extractors are also supported as source endpoints for CDC in Qlik Replicate.This allows for the replication of data changes from SAP's complex data structures1.
The other options provided are not typically associated with CDC in Qlik Replicate:
B: MS Dynamics direct access: While Qlik Replicate can connect to various data sources, MS Dynamics is not commonly listed as a direct source for CDC.
D: Generic REST APIs Data Lake file formats: REST APIs and Data Lake file formats are not standard sources for CDC as they do not maintain transaction logs, which are essential for CDC to track changes.
For detailed information on setting up source endpoints and enabling CDC, you can refer to the official Qlik documentation and community articles that discuss the prerequisites and configurations needed for various source endpoints2345.
質問 # 27
Where should Qlik Replicate be set up in an on-premises environment?
- A. In a cloud environment
- B. In the "middle" between the source and target
- C. As close as possible to the source system
- D. As close as possible to the target system
正解：C
解説：
Questions no:21Verified answer: = C. As close as possible to the source system Step by Step Comprehensive and Detailed Explanation with all References: =In an on-premises environment, Qlik Replicate should be set up as close as possible to the source system. This is because the source system is where the initial capture of data changes occurs, and having Qlik Replicate close to the source helps to minimize latency and maximize the efficiency of data capture.
C: As close as possible to the source system: Positioning Qlik Replicate near the source system reduces the time it takes to capture and process changes, which is critical for maintaining low latency in replication tasks1.
The other options are not recommended because:
A: As close as possible to the target system: While proximity to the target system can be beneficial for the apply phase, it is more crucial to have minimal latency during the capture phase, which is closer to the source.
B: In the "middle" between the source and target: This does not provide the optimal configuration for either the capture or apply phases and could introduce unnecessary complexity and potential latency.
D: In a cloud environment: This option is not relevant to the question as it specifies an on-premises setup. Additionally, whether to use a cloud environment depends on the specific architecture and requirements of the replication scenario.
For detailed guidance on setting up Qlik Replicate in an on-premises environment, including considerations for placement and configuration to optimize performance and reduce latency, you can refer to the official Qlik Replicate Setup and User Guide1.
質問 # 28
In the CDC mode of a Qlik Replicate task, which option can be set for Batch optimized apply mode?
- A. Source connection processes
- B. Time and/or volume
- C. Number of changed records
- D. Maximum time to batch transactions
正解：B
解説：
In Change Data Capture (CDC) mode, Batch optimized apply mode can be set based on time and/or volume.
This means that the batching of transactions can be controlled by specifying time intervals or the volume of data changes to be batched together.
This optimization helps improve performance by reducing the frequency of writes to the target system and handling large volumes of changes efficiently. The Qlik Replicate documentation outlines this option as a method to enhance the efficiency of data replication in CDC mode by batching transactions based on specific criteria.
In the Change Data Capture (CDC) mode of a Qlik Replicate task, when using the Batch optimized apply mode, the system allows for tuning based on time and/or volume. This setting is designed to optimize the application of changes in batches to the target system. Here's how it works:
Time: You can set intervals at which batched changes are applied.This includes setting a minimum amount of time to wait between each application of batch changes, as well as a maximum time to wait before declaring a timeout1.
Volume: The system can be configured to force apply a batch when the processing memory exceeds a certain threshold.This allows for the consolidation of operations on the same row, reducing the number of operations on the target to a single transaction2.
The other options provided do not align with the settings for Batch optimized apply mode in CDC tasks:
A: Source connection processes: This is not a setting related to the batch apply mode.
B: Number of changed records: While the number of changed records might affect the batch size, it is not a setting that can be directly configured in this context.
D: Maximum time to batch transactions: This option is related to the time aspect but does not fully capture the essence of the setting, which includes both time and volume considerations.
Therefore, the verified answer isC. Time and/or volume, as it accurately represents the options that can be set for Batch optimized apply mode in the CDC tasks of Qlik Replicate21.
質問 # 29
How can a source be batch-loaded automatically on a daily basis?
- A. Set trigger through Advanced Run options
- B. Enable task on full load and apply changes
- C. Set trigger through Task Designer
- D. Set trigger through server scheduler
正解：D
解説：
To batch-load a source automatically on a daily basis in Qlik Replicate, you would typically use a server scheduler. Here's how it can be done:
Set trigger through server scheduler (A): You can configure a scheduler on the server where Qlik Replicate is running to trigger the batch load process at a specified time each day.This could be done using the operating system's built-in task scheduler, such as Windows Task Scheduler or cron jobs on Linux systems1.
The scheduler would execute a command or script that starts the Qlik Replicate task configured for batch loading.The command would utilize Qlik Replicate's command-line interface or API to initiate the task1.
This approach allows for precise control over the timing of the batch load and can be adjusted to meet the specific scheduling requirements of the data replication process1.
The other options provided are not typically used for setting up an automatic daily batch load:
B: Set trigger through Advanced Run options: While Advanced Run options provide various ways to run tasks, they do not include a scheduling function for daily automation.
C: Set trigger through Task Designer: Task Designer is used for designing and configuring tasks, not for scheduling them.
D: Enable task on full load and apply changes: This option would start the task immediately and is not related to scheduling the task on a daily basis.
Therefore, the verified answer isA. Set trigger through server scheduler, as it is the method that allows for the automation of batch loading on a daily schedule1.
質問 # 30
Which is the path to add a new column to a single table in a task?
- A. Table Selection -> Schemas -> Add Column
- B. Table Settings -> General -> Add New Column
- C. New Transformation -> Column -> Add Column
- D. Select Table -> Transform -> Add New
正解：B
解説：
To add a new column to a single table in a Qlik Replicate task, the correct path is throughTable Settings.
Here's the process you would typically follow:
Navigate to theTable Settingsof the table you wish to modify within your task.
Go to theGeneralsection.
Use the option toAdd New Column.
This process allows you to add a column directly to the table's schema as part of the task configuration. It's important to note that this action is part of the task's design phase, where you can specify the schema changes that should be applied to the data as it is replicated.
The other options listed, such asNew TransformationorSelect Table -> Transform, are not the direct paths for adding a new column to a table's schema within a task.They are related to different aspects of task configuration and transformation1.
質問 # 31
Which open API methods are supported in Qlik Enterprise Manager?
- A. JavaScript. REST SDK. NET SDK
- B. gcloud. NET SDK. Python SDK
- C. HTTP APIs. REST SDK. Python SDK
- D. REST SDK. NET SDK. Python SDK
正解：D
解説：
Qlik Enterprise Manager supports a range of open API methods that allow for programmatic interaction with the system. The supported API methods are:
REST SDK: This provides a RESTful interface for interacting with Qlik Enterprise Manager, allowing for operations such as viewing task details, running tasks, and exporting or importing task definitions12.
.NET SDK: The .NET SDK enables developers to use .NET languages to interact with Qlik Enterprise Manager, facilitating integration with other .NET applications3.
Python SDK: The Python SDK allows for scripting and automation of tasks in Qlik Enterprise Manager using Python, which is particularly useful for data scientists and analysts who prefer Python for data-related tasks3.
These API methods enable automation, integration with enterprise dashboards, and the ability to perform batch operations, among other tasks3.Therefore, the correct answer isC. REST SDK, .NET SDK, Python SDK, as these are the open API methods supported by Qlik Enterprise Manager3.
質問 # 32
How can the task diagnostic package be downloaded?
- A. Download diagnostic package Go to server settings -> Logging -> Right-click task -> Support -> Download diagnostic package
- B. Open task from overview -> Monitor -> Tools -> Support -> Download diagnostic package
- C. Right-click task from overview -> Download diagnostic package
- D. Open task from overview -> Run -> Tools -?
正解：B
解説：
To download the task diagnostic package in Qlik Replicate, you need to follow these steps:
Open the task from the overview in the Qlik Replicate Console.
Switch to theMonitorview.
Click on theToolstoolbar button.
Navigate toSupport.
SelectDownload Diagnostic Package1.
This process will generate a task-specific diagnostics package that contains the task log files and various debugging data that may assist in troubleshooting task-related issues. Depending on your browser settings, the file will either be automatically downloaded to your designated download folder, or you will be prompted to download it.The file will be named in the format<task_name>__diagnostics__<timestamp>.zip12.
The other options provided do not accurately describe the process for downloading a diagnostic package in Qlik Replicate:
Bis incomplete and does not provide a valid path.
Cincorrectly suggests going to server settings and logging, which is not the correct procedure.
Dsuggests a method that is not documented in the official Qlik Replicate help resources.
Therefore, the verified answer isA, as it correctly outlines the steps to download a diagnostic package in Qlik Replicate12.
質問 # 33
The designer creates a replication task with the source schema name 'HR' and renames the schema in the following areas:
1. In Global Transformation, create a rule to rename schema to 'USER1'
2. In Task Settings -> Target Metadata, enter the Target table schema as 'USER2'
3. In Global Transformation, add a new column named 'SCHEMA' and expression as 'USER3' Which is the final target schema name?
- A. USER3
- B. HR
- C. USER1
- D. USER2
正解：D
解説：
In Qlik Replicate, when multiple schema rename rules are applied, the final schema name isdetermined by the last applied setting that affects the schema name directly. Here's how the process works:
Global Transformationto rename schema to 'USER1': This rule will initially rename the schema from
'HR' to 'USER1'.However, this is not the final schema name as further changes are applied later in the task settings1.
Task Settings -> Target Metadatato enter the Target table schema as 'USER2': This setting overrides the previous global transformation rule and sets the target schema name to 'USER2'.This is because the Target Metadata settings are applied after the Global Transformations and directly affect the target schema name1.
Global Transformationto add a new column named 'SCHEMA' with expression as 'USER3': While this rule adds a new column with a value of 'USER3', it does not change the schema name itself.It only affects the content of a column within the tables1.
Therefore, the final target schema name, after considering all the applied settings, isD. USER2.This is because the Target Metadata setting in the task settings has the final say on the target schema name, and it is set to 'USER2'1.
質問 # 34
......
QREP練習試験と学習ガイドは厳密検証されたにはFast2test：https://jp.fast2test.com/QREP-premium-file.html