Which is the possible Escalate Action for Table Errors?
Correct Answer: D
When encountering table errors in Qlik Replicate, the escalation policy is set toStop Taskand cannot be changed. This means that if the number of table errors reaches a specified threshold, the task will automatically stop, requiring manual intervention to resolve the issue. The escalation action for table errors is specifically designed to halt the task to prevent further errors or data inconsistencies from occurring.This is a safety measure to ensure that data integrity is maintained and that any issues are addressed before replication continues1. The other options listed are not escalation actions for table errors: A: Log Record to the Exceptions Table: While logging errors to the exceptions table is a common action, it is not an escalation action. B: No Escalate Action: This is not a valid option as there is a specific escalation action defined for table errors. C: Suspend Table: Suspending a table is a different action that can be taken in response to errors, but it is not the defined escalation action for table errors in Qlik Replicate. For more information on error handling and escalation actions in Qlik Replicate, you can refer to the official Qlik Replicate Help documentation, which provides detailed guidance on configuring error handling policies and actions for various types of errors1.
Question 2
Which is the default port of Qlik Replicate Server on Linux?
Correct Answer: D
The default port for Qlik Replicate Server on Linux is3552. This port is used for outbound and inbound communication unless it is overridden during the installation or configuration process. Here's a reference to the documentation that confirms this information: The official Qlik Replicate documentation states that "Port 3552 (the default rest port) needs to be opened for outbound and inbound communication, unless you override it as described below." This indicates that 3552 is the default port that needs to be considered during the installation and setup of Qlik Replicate on a Linux system1. The other options provided do not correspond to the default port for Qlik Replicate Server on Linux: A: 3550: This is not listed as the default port in the documentation. B: 443: This is commonly the default port for HTTPS traffic, but not for Qlik Replicate Server. C: 80: This is commonly the default port for HTTP traffic, but not for Qlik Replicate Server. Therefore, the verified answer isD. 3552, as it is the port designated for Qlik Replicate Server on Linux according to the official documentation1.
Question 3
Which option of permissions level in Qlik Enterprise Manager can be set?
Correct Answer: C
In Qlik Enterprise Manager, permissions can be managed in a granular way, and one of the key features is the ability to inherit permissions. Here's how it works: Inherited permissions for all functions : By default, inheritance is enabled for all objects, including users and groups.This means that permissions are automatically carried over from the parent object, ensuring consistency and ease of management across different levels of the organizational structure1. Using the same permissions as in Qlik Replicate (A)andUsing the same permissions as in Qlik Replicate and Qlik Compose (D): While Qlik Enterprise Manager may integrate with Qlik Replicate and Qlik Compose, the permissions are not directly transferred or used in the same way. Each tool has its own set of permissions and roles that need to be configured separately. Transfer rights from Qlik Replicate (B): There is no direct option to transfer rights from Qlik Replicate to Qlik Enterprise Manager. Permissions need to be set within the Enterprise Manager itself, although it may be guided by the roles and permissions defined in Qlik Replicate. Therefore, the verified answer isC. Inherited permissions for all functions, as it reflects the capability of Qlik Enterprise Manager to set permissions based on inheritance, which simplifies the management of user permissions across the system1.
Question 4
Which are the mainhardware components to run a Qlik Replicate Task in a high performance level?
Correct Answer: C
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.
Question 5
The Apply batched changes to multiple tables concurrently option in a Qlik Replicate task is enabled Which Information can be stored in the attrep_apply_exceptlon Control table?
Correct Answer: C
When the "Apply batched changes to multiple tables concurrently" option is enabled in a Qlik Replicate task, theattrep_apply_exceptioncontrol table stores specific information related to change processing errors. The details stored in this table include: TASK_NAME: The name of the Qlik Replicate task. TABLE_NAME: The name of the table. ERROR_TIME (in UTC): The time the exception (error) occurred. STATEMENT: The statement that was being executed when the error occurred. ERROR: The actual error message1. This information is crucial for troubleshooting and resolving issues that may arise during the replication process.The data in theattrep_apply_exceptiontable is never deleted, ensuring a persistent record of all exceptions1. The other options do not accurately reflect the information stored in theattrep_apply_exceptioncontrol table: AandBmention "Warning_Time," which is not a column in the table. Dis incorrect because the table does store information about errors. For more detailed information on theattrep_apply_exceptioncontrol table and its role in handling change processing errors, you can refer to the official Qlik Replicate documentation1.
