Question #1
The HR management team wants to aggregate data to show the number of employees across regions and to be able to drill down into the data.
Which three user story requirements should be collected to assist the development team?
- A . Data source
- B . Report type
- C . Test script
- D . Role-based permissions
- E . Estimation of story
Correct Answer: ABD
ABD
Explanation:
Data Source (A): The first step in building any report is identifying the source of the data. Understanding where the data comes from is crucial because it affects how the data will be queried, filtered, and displayed. It also impacts performance, security, and accuracy of the data. Appian reports can pull data from various sources such as Appian databases, external databases, or even from integrations with other systems. Documenting this information allows the development team to connect the report to the correct data source, ensuring that the report reflects accurate and up-to-date information.
Reference: Appian Documentation – Data Sources
Report Type (B): It is essential to define the type of report required. In this scenario, the HR management team wants an aggregate view with drill-down capabilities. The report type will determine how the data is visualized, whether it is a pie chart, bar graph, or tabular format. This user story requirement ensures that the developers design a report that meets the HR team’s needs and expectations for viewing and interacting with the data.
Reference: Appian Documentation – Creating Reports
Role-Based Permissions (D): Role-based permissions are critical for ensuring that users see only the data they are authorized to access. For instance, while an HR executive might have access to all regions’ data, a regional manager might only see data for their specific region. Defining these permissions upfront is vital for security and compliance. The development team will use this information to implement the correct access controls in the report, which is crucial for protecting
sensitive employee information.
Reference: Appian Documentation – Managing User Permissions
ABD
Explanation:
Data Source (A): The first step in building any report is identifying the source of the data. Understanding where the data comes from is crucial because it affects how the data will be queried, filtered, and displayed. It also impacts performance, security, and accuracy of the data. Appian reports can pull data from various sources such as Appian databases, external databases, or even from integrations with other systems. Documenting this information allows the development team to connect the report to the correct data source, ensuring that the report reflects accurate and up-to-date information.
Reference: Appian Documentation – Data Sources
Report Type (B): It is essential to define the type of report required. In this scenario, the HR management team wants an aggregate view with drill-down capabilities. The report type will determine how the data is visualized, whether it is a pie chart, bar graph, or tabular format. This user story requirement ensures that the developers design a report that meets the HR team’s needs and expectations for viewing and interacting with the data.
Reference: Appian Documentation – Creating Reports
Role-Based Permissions (D): Role-based permissions are critical for ensuring that users see only the data they are authorized to access. For instance, while an HR executive might have access to all regions’ data, a regional manager might only see data for their specific region. Defining these permissions upfront is vital for security and compliance. The development team will use this information to implement the correct access controls in the report, which is crucial for protecting
sensitive employee information.
Reference: Appian Documentation – Managing User Permissions
Question #2
An organization wants to automate identification of its dissatisfied customers based on the ticket description and assign the appropriate team to provide a quick resolution.
What is the best way to auto-classify the dissatisfied customers as part of processing?
- A . Using a natural language connected system
- B . Using a decision table
- C . Using an image analysis connected system
- D . Using a SAIL form
Correct Answer: A
A
Explanation:
The organization aims to automate the identification of dissatisfied customers based on the ticket description. To achieve this, leveraging natural language processing (NLP) capabilities is the most efficient method. Appian provides connected systems that allow integration with external NLP services. These services can analyze text data (such as ticket descriptions) to determine the sentiment or classify the text into predefined categories (like "dissatisfied customer").
Natural Language Connected System:
Appian can integrate with third-party NLP platforms such as Google Cloud Natural Language, AWS Comprehend, or Azure Text Analytics via connected systems.
These services analyze the text provided in the ticket description to detect sentiment, keywords, or specific categories indicating dissatisfaction.
Based on the analysis, the system can automatically assign the appropriate team to handle the case.
Why Not Other Options?
B. Decision Table: While decision tables are useful for rule-based decisions, they are not suitable for interpreting unstructured text like ticket descriptions.
C. Image Analysis Connected System: This option is irrelevant as the task involves text processing, not image analysis.
D. SAIL Form: SAIL forms are primarily used for user interface creation and are not intended for text analysis or classification.
Implementation in Appian:
Create a connected system to integrate with the chosen NLP service.
Configure the NLP service to analyze the text data and return the sentiment or classification results.
Based on the results, use process models to route the ticket to the appropriate team for resolution.
References:
Appian Documentation on Connected Systems: Appian Connected Systems
Appian Community Success Guide: Appian Delivery Methodology
Third-Party NLP Services Integration: Google Cloud NLP Documentation
A
Explanation:
The organization aims to automate the identification of dissatisfied customers based on the ticket description. To achieve this, leveraging natural language processing (NLP) capabilities is the most efficient method. Appian provides connected systems that allow integration with external NLP services. These services can analyze text data (such as ticket descriptions) to determine the sentiment or classify the text into predefined categories (like "dissatisfied customer").
Natural Language Connected System:
Appian can integrate with third-party NLP platforms such as Google Cloud Natural Language, AWS Comprehend, or Azure Text Analytics via connected systems.
These services analyze the text provided in the ticket description to detect sentiment, keywords, or specific categories indicating dissatisfaction.
Based on the analysis, the system can automatically assign the appropriate team to handle the case.
Why Not Other Options?
B. Decision Table: While decision tables are useful for rule-based decisions, they are not suitable for interpreting unstructured text like ticket descriptions.
C. Image Analysis Connected System: This option is irrelevant as the task involves text processing, not image analysis.
D. SAIL Form: SAIL forms are primarily used for user interface creation and are not intended for text analysis or classification.
Implementation in Appian:
Create a connected system to integrate with the chosen NLP service.
Configure the NLP service to analyze the text data and return the sentiment or classification results.
Based on the results, use process models to route the ticket to the appropriate team for resolution.
References:
Appian Documentation on Connected Systems: Appian Connected Systems
Appian Community Success Guide: Appian Delivery Methodology
Third-Party NLP Services Integration: Google Cloud NLP Documentation
Question #3
According to best practices, which two types of tests should be considered during user acceptance testing (UAT)?
- A . Load testing
- B . Platform security testing
- C . Regulation acceptance testing
- D . Functional testing
Correct Answer: CD
CD
Explanation:
Regulation Acceptance Testing (C): During User Acceptance Testing (UAT), it is essential to ensure that the application complies with industry regulations and standards. Regulation acceptance testing focuses on verifying that the system adheres to legal and compliance requirements specific to the industry or region where the application will be used. This ensures that the application meets all necessary regulatory guidelines before going live.
Reference: Appian Documentation – Testing and Validation
Functional Testing (D): Functional testing is a critical component of UAT as it verifies that the application’s functionality works as expected from the end-user’s perspective. This includes validating that all features, workflows, and business processes perform correctly according to the specified requirements. UAT is the final phase where end-users interact with the application to confirm that it meets their needs and performs as intended.
Reference: Appian Documentation – Functional Testing
Note: Load testing (A) and platform security testing (B) are important types of tests but are usually conducted during performance and security testing phases rather than UAT. UAT focuses more on ensuring the application meets business requirements and end-user expectations.
CD
Explanation:
Regulation Acceptance Testing (C): During User Acceptance Testing (UAT), it is essential to ensure that the application complies with industry regulations and standards. Regulation acceptance testing focuses on verifying that the system adheres to legal and compliance requirements specific to the industry or region where the application will be used. This ensures that the application meets all necessary regulatory guidelines before going live.
Reference: Appian Documentation – Testing and Validation
Functional Testing (D): Functional testing is a critical component of UAT as it verifies that the application’s functionality works as expected from the end-user’s perspective. This includes validating that all features, workflows, and business processes perform correctly according to the specified requirements. UAT is the final phase where end-users interact with the application to confirm that it meets their needs and performs as intended.
Reference: Appian Documentation – Functional Testing
Note: Load testing (A) and platform security testing (B) are important types of tests but are usually conducted during performance and security testing phases rather than UAT. UAT focuses more on ensuring the application meets business requirements and end-user expectations.
Question #4
You are designing a user interface that requires a confirmation message when the user attempts to delete a row.
Review the image with the confirmation message:
"Are you sure you want to delete the item?"
According to best practices, which button labels should you choose?
- A . Cancel, Delete
- B . Back, Next
- C . Reject, Approve
- D . False, True
Correct Answer: A
A
Explanation:
According to UI/UX best practices, the button labels in a confirmation dialog should be clear and directly related to the action the user is about to take. "Cancel" allows the user to abort the action, while "Delete" confirms the action to delete the item. This approach ensures that the user understands exactly what will happen when they click either button, reducing the risk of accidental deletion or confusion.
A
Explanation:
According to UI/UX best practices, the button labels in a confirmation dialog should be clear and directly related to the action the user is about to take. "Cancel" allows the user to abort the action, while "Delete" confirms the action to delete the item. This approach ensures that the user understands exactly what will happen when they click either button, reducing the risk of accidental deletion or confusion.
Question #5
You are an Appian Analyst.
According to best practices, which other role should you work with to create process models as a part of requirements gathering?
- A . Product Manager
- B . Product Owner
- C . Architect
- D . Scrum Master
Correct Answer: B
B
Explanation:
As an Appian Analyst, collaborating with a Product Owner during the creation of process models is considered best practice. The Product Owner is responsible for defining the requirements and ensuring that the process models align with the business goals and needs. The Product Owner has a deep understanding of the product vision and user stories, which are crucial during the requirements gathering phase.
Role of Product Owner:
The Product Owner provides detailed requirements and prioritizes them based on business needs.
They ensure that the process models being developed accurately reflect the intended business processes and user stories.
Close collaboration with the Product Owner ensures that the process models are aligned with both the technical and business aspects of the project.
Why Not Other Options?:
B
Explanation:
As an Appian Analyst, collaborating with a Product Owner during the creation of process models is considered best practice. The Product Owner is responsible for defining the requirements and ensuring that the process models align with the business goals and needs. The Product Owner has a deep understanding of the product vision and user stories, which are crucial during the requirements gathering phase.
Role of Product Owner:
The Product Owner provides detailed requirements and prioritizes them based on business needs.
They ensure that the process models being developed accurately reflect the intended business processes and user stories.
Close collaboration with the Product Owner ensures that the process models are aligned with both the technical and business aspects of the project.
Why Not Other Options?:
Question #6
Which one of the following Appian object combinations allows you to directly access and use data from the Appian database?
- A . An expression rule with an integration call
- B . An expression rule with a query
- C . A process model that uses an Export to Excel smart service
- D . An interface object with an integration call
Correct Answer: B
B
Explanation:
In Appian, the combination of an expression rule with a query allows you to directly access and use data from the Appian database. Expression rules are used to define business logic, while queries are used to retrieve data from the database.
Expression Rule with a Query:
An expression rule can be used to execute a query against the Appian database to retrieve data.
This combination allows you to filter, sort, and manipulate the data retrieved directly from the database within your application logic.
The a!queryEntity() function is commonly used within an expression rule to fetch data from a specific entity in the database.
Why Not Other Options?:
B
Explanation:
In Appian, the combination of an expression rule with a query allows you to directly access and use data from the Appian database. Expression rules are used to define business logic, while queries are used to retrieve data from the database.
Expression Rule with a Query:
An expression rule can be used to execute a query against the Appian database to retrieve data.
This combination allows you to filter, sort, and manipulate the data retrieved directly from the database within your application logic.
The a!queryEntity() function is commonly used within an expression rule to fetch data from a specific entity in the database.
Why Not Other Options?:
Question #7
As an Appian Analyst, which activity are you responsible for during the "optimize" phase of a project?
- A . Build the deployment pipeline
- B . Structure an application support team
- C . Conduct release planning
- D . Measure the impact of application release
Correct Answer: D
D
Explanation:
During the "optimize" phase of an Appian project, the focus is on evaluating and improving the performance and impact of the application after its release. As an Appian Analyst, your role in this phase involves measuring the impact of the application release, which includes gathering and analyzing data on user adoption, performance metrics, and overall business impact. This data-driven approach helps in identifying areas for improvement and optimization to ensure the application continues to meet business objectives effectively.
Reference: Appian Documentation – Application Lifecycle Management
Note: The other options (A, B, C) are typically the responsibilities of other roles in different phases of the project, such as developers or project managers, and not specific to the "optimize" phase for an Appian Analyst.
D
Explanation:
During the "optimize" phase of an Appian project, the focus is on evaluating and improving the performance and impact of the application after its release. As an Appian Analyst, your role in this phase involves measuring the impact of the application release, which includes gathering and analyzing data on user adoption, performance metrics, and overall business impact. This data-driven approach helps in identifying areas for improvement and optimization to ensure the application continues to meet business objectives effectively.
Reference: Appian Documentation – Application Lifecycle Management
Note: The other options (A, B, C) are typically the responsibilities of other roles in different phases of the project, such as developers or project managers, and not specific to the "optimize" phase for an Appian Analyst.
Question #8
You are translating a user requirement into a user story and need to ensure that the desired functionality will be delivered as expected.
What needs to be written into the user story to ensure it will meet the requirement?
- A . Estimation of effort to develop
- B . Business value
- C . Test Script
- D . Acceptance criteria
Correct Answer: D
D
Explanation:
When translating a user requirement into a user story, it is essential to include acceptance criteria to ensure that the desired functionality will be delivered as expected. Acceptance criteria provide clear, testable conditions that define when a user story is complete and meets the requirement. This ensures that the development team has a clear understanding of what needs to be built and how it will be validated, reducing the risk of miscommunication and ensuring the final product aligns with the user’s needs.
Reference: Appian Documentation – Writing Effective User Stories
Note: While business value (B) and estimation of effort (A) are important elements of a user story, they do not directly ensure that the functionality will meet the requirement. The test script (C) is typically created after the user story is developed.
D
Explanation:
When translating a user requirement into a user story, it is essential to include acceptance criteria to ensure that the desired functionality will be delivered as expected. Acceptance criteria provide clear, testable conditions that define when a user story is complete and meets the requirement. This ensures that the development team has a clear understanding of what needs to be built and how it will be validated, reducing the risk of miscommunication and ensuring the final product aligns with the user’s needs.
Reference: Appian Documentation – Writing Effective User Stories
Note: While business value (B) and estimation of effort (A) are important elements of a user story, they do not directly ensure that the functionality will meet the requirement. The test script (C) is typically created after the user story is developed.
Question #9
A partially created user story for an approval task has been added to the Product Backlog and you have been asked to review it.
So far, the user story includes acceptance criteria stating:
"Verify that the user can select approve or deny."
"Verify that the user can enter an approval comment."
What are two examples of additional content that need to be added to the user story before it can be considered complete?
- A . Condition upon selecting either "deny" or "approve"
- B . User story description
- C . UI mockup
- D . Truth table
Correct Answer: AB
AB
Explanation:
User Story Description (B): A complete user story should include a detailed description that outlines the context, goals, and specific actions the user can perform. This helps in setting a clear understanding of what needs to be developed and why. The description provides the foundation for the user story and ensures that all stakeholders have a shared understanding of the requirement.
Reference: Appian Documentation – Writing User Stories
Condition upon Selecting Either "Deny" or "Approve" (A): To ensure that the user story is complete, you must specify what happens when the user selects "deny" or "approve." This could include conditions such as sending notifications, triggering workflows, or updating statuses. Clearly defining these conditions ensures that the development team knows exactly what to implement and how the system should behave in different scenarios.
Reference: Appian Documentation – Acceptance Criteria Examples
AB
Explanation:
User Story Description (B): A complete user story should include a detailed description that outlines the context, goals, and specific actions the user can perform. This helps in setting a clear understanding of what needs to be developed and why. The description provides the foundation for the user story and ensures that all stakeholders have a shared understanding of the requirement.
Reference: Appian Documentation – Writing User Stories
Condition upon Selecting Either "Deny" or "Approve" (A): To ensure that the user story is complete, you must specify what happens when the user selects "deny" or "approve." This could include conditions such as sending notifications, triggering workflows, or updating statuses. Clearly defining these conditions ensures that the development team knows exactly what to implement and how the system should behave in different scenarios.
Reference: Appian Documentation – Acceptance Criteria Examples
Question #10
Which BPMN notation type is used to reflect the roles and associated activities within a Process Model diagram?
- A . Task
- B . Swimlane
- C . Sequence Flow
- D . Sub-Process
Correct Answer: B
B
Explanation:
In BPMN (Business Process Model and Notation), a swimlane is used to represent roles and their associated activities within a process model diagram. Each swimlane represents a different role or department, and the tasks or activities performed by that role are placed within the corresponding swimlane. This visual distinction helps in understanding who is responsible for which parts of the process.
Swimlane Overview:
Swimlanes are horizontal or vertical sections within a process model diagram.
Each lane is labeled with the name of the role, department, or entity that is responsible for the activities within that lane.
The activities (tasks, events, gateways) are placed within the appropriate swimlane to show which role is performing each action.
Why Not Other Options?:
B
Explanation:
In BPMN (Business Process Model and Notation), a swimlane is used to represent roles and their associated activities within a process model diagram. Each swimlane represents a different role or department, and the tasks or activities performed by that role are placed within the corresponding swimlane. This visual distinction helps in understanding who is responsible for which parts of the process.
Swimlane Overview:
Swimlanes are horizontal or vertical sections within a process model diagram.
Each lane is labeled with the name of the role, department, or entity that is responsible for the activities within that lane.
The activities (tasks, events, gateways) are placed within the appropriate swimlane to show which role is performing each action.
Why Not Other Options?:
Question #11
Of the choices provided, which are the three most appropriate use cases for Appian?
- A . The customer needs to perform large-scale extract, transform, and load (ETL) operations
- B . The customer needs to be able to run their application on mobile devices
- C . The customer needs to have one site tab for each of their seven personas
- D . The customer needs to be able to run their application in a browser
- E . The customer needs to be able to embed the application within their own web page
Correct Answer: BCD
BCD
Explanation:
Appian is a low-code platform designed for building enterprise applications with a focus on flexibility, user experience, and integration capabilities.
The most appropriate use cases for Appian include:
Mobile Compatibility (B):
Appian supports mobile-first design, allowing applications to be easily accessed and used on mobile devices without requiring separate development efforts.
This capability is critical for businesses that need their workforce to access applications on the go.
Multiple Site Tabs for Personas (C):
Appian allows for the creation of different site tabs for different user personas, each with a tailored user experience.
This is ideal for organizations with distinct user groups who need customized interfaces and access to specific parts of the application.
Browser-Based Application (D):
Appian applications are web-based and can be accessed directly from a browser, ensuring easy access and a consistent user experience across different platforms.
Why Not Other Options?:
BCD
Explanation:
Appian is a low-code platform designed for building enterprise applications with a focus on flexibility, user experience, and integration capabilities.
The most appropriate use cases for Appian include:
Mobile Compatibility (B):
Appian supports mobile-first design, allowing applications to be easily accessed and used on mobile devices without requiring separate development efforts.
This capability is critical for businesses that need their workforce to access applications on the go.
Multiple Site Tabs for Personas (C):
Appian allows for the creation of different site tabs for different user personas, each with a tailored user experience.
This is ideal for organizations with distinct user groups who need customized interfaces and access to specific parts of the application.
Browser-Based Application (D):
Appian applications are web-based and can be accessed directly from a browser, ensuring easy access and a consistent user experience across different platforms.
Why Not Other Options?:
Question #12
Improvements are being considered for an Expense Process, and you have been asked to capture that there is now an approval task sent to the finance manager.
As part of the approval, the process should also reflect that if the payment has not been authorized within 48 hours, a reminder message is sent to the finance manager to inform them they have an outstanding task.
Which Business Process Model and Notation (BPMN) notation type would you use to illustrate the reminder message?
- A . Data object
- B . Gateway
- C . Intermediate event
- D . Start event
Correct Answer: C
C
Explanation:
In BPMN, an intermediate event is used to indicate events that occur between the start and end of a process. To model a reminder message that is sent if the payment is not authorized within 48 hours, an intermediate event, specifically a timer intermediate event, is the appropriate notation.
Intermediate Event Overview:
An intermediate event can be used to model actions such as delays, triggers, or messages that happen during the course of a process.
A timer intermediate event would be used to trigger the reminder after a set period (in this case, 48 hours).
Why Not Other Options?:
C
Explanation:
In BPMN, an intermediate event is used to indicate events that occur between the start and end of a process. To model a reminder message that is sent if the payment is not authorized within 48 hours, an intermediate event, specifically a timer intermediate event, is the appropriate notation.
Intermediate Event Overview:
An intermediate event can be used to model actions such as delays, triggers, or messages that happen during the course of a process.
A timer intermediate event would be used to trigger the reminder after a set period (in this case, 48 hours).
Why Not Other Options?:
Question #13
Review the following project phase definition:
"A standardized agreement between Development Team and the Product Owner on what criteria a user story must meet in order for the team to consider it complete."
Which option does this definition apply to?
- A . Acceptance Criteria
- B . Value Statement
- C . Definition of Ready (DoR)
- D . Definition of Done (DoD)
Correct Answer: D
D
Explanation:
The "Definition of Done" (DoD) refers to a shared understanding between the Development Team and the Product Owner on the criteria that a user story must meet to be considered complete. This definition helps ensure that all aspects of the user story are fully developed, tested, and meet the agreed-upon standards before being marked as done.
Definition of Done Overview:
DoD includes all conditions that must be satisfied for the work to be accepted by the product owner.
It typically covers code completion, testing, documentation, and any other activities required to deliver a finished product.
Why Not Other Options?:
D
Explanation:
The "Definition of Done" (DoD) refers to a shared understanding between the Development Team and the Product Owner on the criteria that a user story must meet to be considered complete. This definition helps ensure that all aspects of the user story are fully developed, tested, and meet the agreed-upon standards before being marked as done.
Definition of Done Overview:
DoD includes all conditions that must be satisfied for the work to be accepted by the product owner.
It typically covers code completion, testing, documentation, and any other activities required to deliver a finished product.
Why Not Other Options?:
Question #14
During a development sprint, a new issue is identified and raised to the team.
What should you ask the Product Owner to do?
- A . Add the new issue to the current sprint scope
- B . Evaluate the severity of the issue and re-prioritize the sprint if needed
- C . Add the new issue in the next sprint
- D . Modify the sprint plan to swap a completed story with the new issue
Correct Answer: B
B
Explanation:
When a new issue is identified during a sprint, it is essential to evaluate its impact on the current sprint’s goals and priorities. The Product Owner should assess the severity and importance of the issue. If it is critical, they may need to re-prioritize the sprint backlog and adjust the sprint scope accordingly. This approach ensures that the development team focuses on delivering the highest value to the project. Simply adding the issue to the current sprint or the next sprint without proper evaluation could disrupt the sprint’s progress and lead to inefficiencies.
Reference: Appian Documentation – Agile Methodology in Appian Projects
B
Explanation:
When a new issue is identified during a sprint, it is essential to evaluate its impact on the current sprint’s goals and priorities. The Product Owner should assess the severity and importance of the issue. If it is critical, they may need to re-prioritize the sprint backlog and adjust the sprint scope accordingly. This approach ensures that the development team focuses on delivering the highest value to the project. Simply adding the issue to the current sprint or the next sprint without proper evaluation could disrupt the sprint’s progress and lead to inefficiencies.
Reference: Appian Documentation – Agile Methodology in Appian Projects
Question #15
You are trying to decide between using a side-by-side layout or a column layout.
Which resource should be referred to in order to make sure that best practices are followed?
- A . Appian UX Design Guide
- B . Appian Tutorials
- C . Appian Discussion Board
- D . Appian SAIL Recipes
Correct Answer: A
A
Explanation:
The Appian UX Design Guide is the appropriate resource to consult when making decisions about layout choices like side-by-side versus column layouts. This guide provides best practices for designing user interfaces in Appian applications, ensuring that the UI is intuitive, responsive, and consistent with Appian’s design principles. Referring to the UX Design Guide helps in making informed design decisions that enhance user experience.
Reference: Appian UX Design Guide
Note: While other resources like Appian Tutorials, Discussion Boards, and SAIL Recipes are useful for specific cases, the UX Design Guide is the primary reference for best practices in UI design.
A
Explanation:
The Appian UX Design Guide is the appropriate resource to consult when making decisions about layout choices like side-by-side versus column layouts. This guide provides best practices for designing user interfaces in Appian applications, ensuring that the UI is intuitive, responsive, and consistent with Appian’s design principles. Referring to the UX Design Guide helps in making informed design decisions that enhance user experience.
Reference: Appian UX Design Guide
Note: While other resources like Appian Tutorials, Discussion Boards, and SAIL Recipes are useful for specific cases, the UX Design Guide is the primary reference for best practices in UI design.