For the High risk Regular changes closed in September, what…

For the High risk Regular changes closed in September, what was the average number of days those changes had from the date the change was opened to the date the change was closed in the change management workflow system? The Senior Consultant on the engagement informs you that a calculation of DATEDIFF(‘day’,[Change Opened],[Regular Change Closed Date],’sunday’) can be helpful in addressing the question. (Round your answer to the nearest whole number)

Potpourri_6 TS-Linux Consider that a system running TS-Linux…

Potpourri_6 TS-Linux Consider that a system running TS-Linux has a periodic timer starting at t = 0ms with a period of 25ms. A firm timer with a system-wide overshoot parameter of 5ms is also available for use. A user schedules an event A with firm timer expiry at t = 47ms.  The user also schedules another event B with firm timer expiry at t = 155ms. Remember that when a user schedules a firm timer expiry at t = x on a system with an overshoot parameter y, the one-shot timer interrupt will be scheduled for t = (x + y). Ignore any system calls/external interrupts. Assume that the kernel is never executing a critical section and that there are no other tasks to be scheduled. What would the duration between fielding the two timer events A and B be? Explain succinctly.

Potpourri_7 LRVM Consider an application using the LRVM libr…

Potpourri_7 LRVM Consider an application using the LRVM library.  A first transaction in the application uses multiple set_range calls and commits with the “no_flush” mode in its end_transaction. A second transaction in the same application modifies the *same data blocks* modified by the first transaction and commits with a “flush” mode in its end_transaction.  (Answer True/False with justification; no credit without justification): The above scenario will result in LRVM doing redundant I/O for the first transaction followed by the I/Os for the same data blocks for the second transaction.