New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Appian ACA100 Exam - Topic 5 Question 30 Discussion

Actual exam question for Appian's ACA100 exam
Question #: 30
Topic #: 5
[All ACA100 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: A, B, D

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


Contribute your Thoughts:

0/2000 characters
Leonida
10 hours ago
A, B, and D are the clear winners. Can't drill down without role-based permissions!
upvoted 0 times
...
Adell
6 days ago
Haha, C is a classic trick answer. Everyone knows that's not what they're looking for here.
upvoted 0 times
...
Aide
11 days ago
C? Really? Test scripts? That's not a user story requirement. A, B, and D for sure.
upvoted 0 times
...
Aileen
16 days ago
I'd go with A, B, and E. Gotta have that estimation to plan the work properly.
upvoted 0 times
...
Goldie
21 days ago
A, B, and D seem like the most relevant requirements for the development team.
upvoted 0 times
...
Viva
26 days ago
I feel like estimation of story could be important, but it seems less critical than understanding the data source and report type.
upvoted 0 times
...
Kimi
1 month ago
I’m a bit confused about whether we need to include test scripts in this case. I thought those were more for validating the final product rather than gathering requirements.
upvoted 0 times
...
Alison
1 month ago
I remember a practice question where we had to identify report types for different user needs. That might be relevant here too, right?
upvoted 0 times
...
Altha
1 month ago
I think we need to focus on the data source since it’s crucial for accurate reporting. But I’m not entirely sure if we should also consider role-based permissions.
upvoted 0 times
...
Alison
2 months ago
Hmm, I'm a bit confused about the "estimation of story" option. Not sure if that's a core user story requirement or more of a project management consideration. I'd stick to the key functional needs for now.
upvoted 0 times
...
Tatum
2 months ago
This seems pretty straightforward. I'd go with A, B, and D - get the data source, report type, and role-based permissions sorted out. That should give the dev team a solid foundation to work from.
upvoted 0 times
...
Virgilio
2 months ago
I'm a little unsure about the "test script" option. Not sure if that's directly relevant to the user story requirements. I'd concentrate on nailing down the data, reporting, and permissions first.
upvoted 0 times
...
Carmela
2 months ago
I think we need to start with A) Data source. It's crucial.
upvoted 0 times
...
Adell
3 months ago
Okay, let's see. I think the main things we need to nail down are the data source, the specific report type they want, and any access controls required. Gotta make sure we get those core requirements right.
upvoted 0 times
...
Alesia
3 months ago
Hmm, this seems like a straightforward data aggregation and reporting requirement. I'd focus on gathering the key user story details like the data source, report type, and any role-based permissions needed.
upvoted 0 times
Buck
2 months ago
Definitely need to know the report type too.
upvoted 0 times
...
Felicitas
2 months ago
I agree, data source is crucial.
upvoted 0 times
...
Pilar
3 months ago
Test scripts might be useful later, but not a priority now.
upvoted 0 times
...
Johanna
3 months ago
Can we also consider the estimation of story?
upvoted 0 times
...
...

Save Cancel