KX3-003 Online Practice Questions

Explanation:
A. Enabling the Bucket data by date checkbox and setting the Bucket Size to Day and the Number of Buckets to 730 would directly create a view that organizes daily historical data into daily buckets spanning the last two years (since there are 365 days in a year, multiplied by 2).
C. Creating calendar interval, start date, and end date variables using the CalendarDate table allows for the configuration of a custom time range in the worksheet. These variables can be referenced to display historical data for the desired period.
B is not correct because adjusting the Anchor date by 1 year would only provide data for the last year, not two. D is not correct because it suggests a method of filtering data by date without bucketing, which does not align with the requirement to show historical data in daily buckets.
References:
Kinaxis RapidResponse documentation on bucketing data by date.
Kinaxis support resources on configuring worksheets with date variables and bucketing.

Explanation:
Performance issues often stem from the complexity of calculations and the size of the data sets they are applied to. In this case, the use of a calculated field (NameAndDescription) in the hierarchy definition is the most likely cause of performance degradation. This field is calculated on the fly using a concatenation of the Name and Description, which is a more resource-intensive process compared to using static fields.
Calculated fields, especially those involving string operations like concatenation, can be significantly slower because they require runtime computation. This contrasts with static fields that are indexed and retrieved directly from the database without additional computational overhead.
References:
Kinaxis RapidResponse documentation on hierarchy design and performance considerations.
Kinaxis best practices for creating efficient hierarchies and using calculated fields.
Using a calculated field, especially one that concatenates strings like in option C, can significantly impact performance because it requires additional computation for each record. This is more resource-intensive than using a direct field value, which would explain the poorer performance when using the PartFamily hierarchy compared to the PartPlanner hierarchy.
References:
Kinaxis RapidResponse Author Level 3 training materials1.
Web search results and Kinaxis best practices2.

Explanation:
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.

Explanation:
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.

Explanation:
B. By adding a column to map the bucket dates in the spreading worksheet, you ensure that the start and end dates of the spreading are properly defined and can be utilized in the algorithm.
D. Selecting "Use same spreading worksheet values for all edits" ensures that the values entered in the buckets are consistent across the worksheet, which is necessary for the spreading functionality to work correctly.
A is incorrect because removing unmapped columns does not solve the issue related to spreading values across the buckets. C is incorrect because allowing editing only if all buckets are the same size is a constraint that does not address the mapping issue.
References:
Kinaxis RapidResponse support articles on troubleshooting and configuring spreading worksheets.
Kinaxis community discussions on common issues and solutions related to worksheet design.
To resolve the issue with the workbook designed for spreading values, it is necessary to ensure that the bucket dates are properly mapped in the spreading worksheet. This allows the system to recognize and apply the correct time horizon for the spread. Additionally, selecting the option to use the same spreading worksheet values for all edits ensures consistency across the worksheet.
References:
Kinaxis RapidResponse Author Level 3 certification materials1.
Enhanced troubleshooting skills and best practices as mentioned in the Kinaxis Certification Program2.