To satisfy the requirement where service level intervals vary according to multiple criteria (passenger status, class of service, and fare type), you would create a multivariate circumstanced rule, a circumstance definition, and a circumstance template. This allows you to create SLAs that vary based on the combination of these criteria. References: Pega official documentation on circumstancing rules.

Controlling access to an attachment category can be achieved through various configurations. Using a When condition like "IsCurrentStageTesting" (A) allows for dynamic access control based on the case's current stage, enabling attachments to be accessible only under certain conditions. Assigning privileges, such as
"DeleteOwn" (C), to users enables fine-grained control over actions users can perform on attachments, such as deleting their own attachments, thus enhancing security and compliance with business rules.References: Pega Community documentation on attachment categories and access control.

Pega Web Mashup is ideal for scenarios where minimal resources are available for updating the Pega Platform with each new release, as it allows external applications to embed Pega UI elements with minimal maintenance. Additionally, it's useful when users are expected to create cases, open assignments, and manage data privacy within an embedded Pega frame in an external web page. References: Pega Platform Help - Pega Web Mashup.

When creating a new major version of an application ruleset, you would use the Ruleset Maintenance wizard to skim the relevant ruleset versions. This process copies the highest version of existing rules to the new ruleset version, effectively creating the new major version. References: Pega official documentation on ruleset skimming.

The assignment urgency 6.5 hours after the case reaches the assignment with the given SLA configuration would be 95 (B). Here's the calculation: The initial urgency is 20. The case reaches the goal after 5 hours, adding 10 to the urgency, making it 30. Since the deadline is at 2 hours and has been exceeded by 4.5 hours, the urgency increases by 25, making it 55. Now, with the passed deadline events occurring every hour and increasing urgency by 5, after 1.5 hours, this would occur 1 additional time (since it's half an hour into the next hour), adding 5 to the urgency. Therefore, the total urgency after 6.5 hours is 20 (initial) + 10 (goal) + 25 (deadline) + 5 (passed deadline event) = 60. However, since the deadline urgency increase occurs at the 2-hour mark, the urgency would be 20 + 25 = 45 at 2 hours, and then after reaching the goal at 5 hours, additional 10 is added, making it 55, and then one passed deadline event adds 5 more, making the total 60. Since the deadline urgency is already accounted for at the 2-hour mark, it should not be added again after the goal. Therefore, the correct total urgency would be 20 (initial) + 10 (goal) + 25 (deadline) + 40 (8 passed deadline events) = 95.Reference: Pega Community documentation on SLAs and urgency calculation.