KX3-003 Practice Exam Questions with Answers Certified RapidResponse Author Level 3 Exam Certification

The script is performing a data import operation into a worksheet that is configured to allow importing data for the purpose of inserting records, as shown in the worksheet properties exhibit. The JSON object in the console output would reflect the result of this import operation. The object details the number of records deleted, modified, and inserted. Since the worksheet is set up only to allow insertion, and the script is importing data for insertion, the "inserted" key would have a value of 1, and"deleted" and "modified" would have a value of 0, indicating a successful insert without any deletions or modifications.

ReferencesKinaxis RapidResponse documentation for data importing and console operations would support this behavior, outlining how the importData method interacts with worksheet configurations.

In the context of creating a metric worksheet for calculating the number of late orders, you want to group by DueDate to consolidate orders that are due on the same day, and then sum the Count for each of these groups to get the total number of late orders per day. Therefore, DueDate should be the grouping column, and Count should use the Sum function to add up all instances of late orders for each DueDate.

References:

• Kinaxis RapidResponse documentation on creating metric worksheets.
• Kinaxis learning resources on the use of expressions and functions for grouping and aggregation in worksheets.

To optimize performance when creating a worksheet that contains fields from four tables, the worksheet should be based on:

• Table 1

Table 1 is connected to Table 3 with a one-way arrow, indicating a one-to-many relationship where Table 1 is the primary table. This setup typically allows for more efficient data retrieval and better performance.

• References

The decision is supported by the diagram showing the relationships between the tables, where “Arrow Head = 1” and “Arrow Base = Many” indicates the direction of the relationship and the primary table.

To optimize performance, the worksheet should be based on the top-level table from which you can access related data via references. This is because starting from the top level allows you to utilize indexed lookups, which are faster than traversing from many-to-one relationships. Given the data model design, Table 1 is the topmost table with one-to-many relationships to Table 3, which in turn links to Table 4, and it can also indirectly access data from Table 2 through the many-to-one relationship back to Table 1.

References:

• Kinaxis RapidResponse documentation on worksheet creation and data model traversal.
• Kinaxis guidelines on optimizing worksheets for better performance.

The ListAsSet function in Kinaxis RapidResponse expects a set of elements as input, typically in the format of a string with elements enclosed in single quotes and separated by commas. For a user that should see data for suppliers A, B, and C, you need to format the string to match this expected input format.

References:

• Kinaxis RapidResponse documentation on the ListAsSet function and profile variables.
• Kinaxis community discussions or support articles on configuring profile variables for user-specific views.

References: The information is based on the Kinaxis RapidResponse documentation and learning resources, which provide guidelines on how to properly format expressions and variables for worksheets.

The expression that calculates the difference between the future EffectiveUnitTransferCost and the cost to transfer today would take the future cost and subtract the current cost converted to today's date, considering the transfer quantity. The CONVERTONDATE function is used to convert the historical TransferCost to its value as of today, and then this value is divided by Quantity to get the unit cost as of today. This unit cost is then subtracted from the EffectiveUnitTransferCost to find the difference.

ReferencesThis uses the CONVERTONDATE function in Kinaxis RapidResponse, which is designed to adjust historical cost figures to their equivalent value on a different date, accounting for factors such as currency fluctuation, as outlined in the Kinaxis formula and functions documentation.

A. In the ItemDetail table, making Name plus Site a compound reference to the Item table aligns with relational database principles where a foreign key references a primary key in another table.

C. In the TransactionDetail table, making ID, Owner, and Type a reference to the TransactionHeader table follows the foreign key to primary key relationship as well, where TransactionDetail refers to its header record.

E. In the TransactionDetail table, making ItemName plus ItemSite a reference to the Item table ensures that each transaction detail record is linked to an existing item record, enforcing referential integrity.

B is incorrect because the TransactionHeader table should not reference the TransactionDetail table; it should be the other way around. D is incorrect because the Item table should not reference the ItemDetail table; this too should be the other way around.

References:

• Kinaxis RapidResponse documentation on data modeling and relationships between tables.
• Standard SQL database design principles as they apply within the RapidResponse environment.

The AvailableRule control table is used to define how available dates for supply and demand are calculated in Kinaxis RapidResponse. This includes the rules for when supplies are considered available for meeting demand and vice versa, such as lead times, transit times, and other considerations that might affect when a part can realistically be expected to be available.

ReferencesThe function of the AvailableRule control table and its impact on the calculation of available dates for supplies and demands is outlined in Kinaxis RapidResponse configuration settings for supply chain planning processes.

For the automated deletion of records older than a year in the HistoricalDemandActual table, the correct approach involves:

• Statement C:Utilizing an Automation Chain. Automation Chains in RapidResponse allow the creation of sequences of actions, including data deletions, that can be scheduled or triggered based on specific events. This method is essential for implementing complex automations such as deleting records based on a date condition.
• Statement D:Creating a Scheduled Task. Scheduled Tasks are crucial for setting up the automation to run on a regular interval, such as weekly, withoutmanual intervention. This ensures that the command to delete old records is executed consistently every week.

The two violations shown in the graphic are:

A. The key field contains the table name: Best practices suggest that the name of a key field should not repeat the table name. It should be succinct and only include the necessary distinguishing characteristic to remain clear and avoid redundancy.

C. The deployment name prefix is included in the OrderId field: Including a deployment name prefix in the field name can create issues when moving between environments, as the deployment name typically changes between development,testing, and production. It's better to use generic field names that are not environment-specific.

ReferencesThis is based on Kinaxis best practices for data model design, which recommend avoiding redundancy in field naming and ensuring that field names are environment-agnostic to facilitate easier migration and understanding of the data model across different stages of the deployment process.

The worksheet properties shown in the graphic indicate how to calculate the change in theAvailableDateofIndependentDemandbetween a child and its parent scenario. Configuration II shows the expression[:AvailableDate#0 - :AvailableDate#1 Workday], where#0refers to the child scenario and#1refers to the parent scenario. This expression calculates the difference in workdays between theAvailableDateof the independent demand in the child scenario and the parent scenario.

The worksheet should be set to calculate using the final results from other columns, ensuring that it takes into consideration the latest available data from the child and parent scenarios for accurate calculation of the workday difference.

References:

• Kinaxis RapidResponse documentation on worksheet expressions and scenario comparison.
• Kinaxis training materials on configuring worksheets for scenario analysis.

Developing a cross scenario data change allows for controlled updates from child to parent scenarios, aligning with company policy on not adjusting lead times in shared scenarios.

To evaluate the impact of converting planned orders to scheduled receipts and then push changes to the parent scenario, while adhering to company policy that prohibits adjustments to lead times in shared scenarios:

• Statement B:Develop a cross scenario data change. This will allow users to make their changes in their scenarios and then push these changes to the parent scenario. This method ensures that changes are captured and transferred correctly while adhering to the company’s policy regarding lead times.

References:

Scenario planning

• Scenario planning capabilities in Kinaxis RapidResponse allow for testing changes in private scenarios before pushing them to shared ones1.

Change management

• The Engineering Change Management application in RapidResponse supports evaluating the effect of changes and determining the optimal time for implementation, which can be adapted for evaluating the impact of converting planned orders2.

• Kinaxis documentation suggests using scenarios to track changes and push them to parent scenarios without affecting system performance3.

• Best practices in Kinaxis RapidResponse include maintaining the integrity of shared scenarios by not altering critical parameters like lead times45.

To identify an automation chain and its associated resources, searching for resources based on the specific table involved in the automation (in this case, "HistoricalPartKPI") will help you find the correct automation chain. This approach ensures that you identify all the resources related to that particular table, including automation chains.

ReferencesThe Kinaxis RapidResponse documentation for administrators provides guidance on how to search for and identify resources associated with specific tables or actions within the system, which includes searching for resources based on table names.

Adding a dedicated input table with a single key reference to the Customer table and a field for the MostRecentOrderDate is the most memory-efficient approach. This design avoids adding additional fields to tables that may contain a large numberof records, which would increase memory usage. Instead, the MostRecentOrderDate is stored once per customer in a separate table, minimizing the memory footprint and optimizing query performance since only the relevant data is accessed.

References:

• Kinaxis RapidResponse documentation on data modeling and performance optimization.
• Best practices in database normalization and data model efficiency provided by Kinaxis.