The three options that are application layers in the Situational Layer Cake architecture are implementation, division, and organization. The implementation layer contains the case types and data types that are specific to a single implementation of an application. The division layer contains the rules and data that are shared by multiple implementations within a division or a business unit. The organization layer contains the rules and data that are common across the entire organization or enterprise. Reference: https://community.pega.com/knowledgebase/articles/application-development/86/application-layers

it routes an assignment so that any available member of the Finance department can perform the task. A work queue is a shared list of assignments that can be accessed by multiple users who have the same role or skill. By routing the assignment to a work queue, you can ensure that any qualified user can pick up and complete the task. Reference: https://academy.pega.com/library/87/pega-certified-business-architect-pcba-87v1 (Module 8: Routing)

These two options are examples of configurations that you can perform for a mobile app channel. A mobile app channel defines how a case type is displayed and processed on a mobile device. You can configure security behavior such as biometric identifiers, encryption, or offline authentication for a mobile app channel. You can also manage administrative functions such as access to log files, crash reports, or feedback forms for a mobile app channel. The other options are either incorrect or irrelevant for this question. Reference: https://docs-previous.pega.com/mobile/87/configuring-mobile-app-channels

These answers are correct because they achieve the behavior of creating a case ID only when the customer chooses to make changes to their membership. Temporary cases are cases that are not stored in the database until a Persist case step is reached in the case life cycle. This way, the case can be abandoned without creating any records or consuming any resources. Reference: https://academy.pega.com/library/87/pega-certified-business-architect-pcba-87v1 (Module 4: Case Design)

This scenario is a use case for the Wait step because it involves pausing a case until another case reaches a certain status. The salary increase case can be configured to wait for the approval case to reach a Resolved-Approved status before continuing to process the increase. The other scenarios do not involve pausing a case based on a timer or a case dependency, but rather on user actions or inputs. Reference: https://academy.pega.com/topic/case-workflow-dependency/v1