ACD201 practice question 5 of 15
You're developing a record view for a case management system that enables users to upload files to a specific location within an external records…
Full set: 99 questionsTo develop the specified record view and its associated action, the developer must gather two key pieces of information from the business stakeholders. First, the technical destination for the file upload within the external application (A) is required to configure the underlying integration object. Second, the developer needs to understand the user's desired presentation and interaction model for the files on the record view (D), as this directly informs the UI design and component selection (e.g., a document grid or a card layout). These requirements define the backend functionality and the frontend user experience, respectively.
B. The email of the system administrator so that an email can be sent to them if the integration fails. This is an implementation detail for error handling, not a core user-facing requirement for the primary functionality described in the prompt.
C. The time of file upload if the file is less than 250MB. This is system-generated data captured after the process runs; it is not a requirement the developer needs from the user to build the interface.
1. For Answer A (Location of upload): The configuration of an integration object
which is necessary to connect to an external system
requires specific endpoint details. The developer must know the target location to build the integration that the record action will call.
Source: Appian Documentation
"Integration Object
" Section: "Create an Integration." This section details the required configurations
such as the URL and request body
which would contain the destination path or folder ID in the external system.
2. For Answer D (How the user wishes to interact): Designing a useful and intuitive record view is a primary goal in Appian development. The choice of display components directly impacts the user experience.
Source: Appian Documentation
"Design a Record View
" Section: "Record View Components." This guide explains that developers must "choose from a variety of templates and components to display record data
" underscoring that the layout (grid
cards
etc.) is a fundamental design decision based on user requirements.
3. General Principle (Gathering Requirements): The Appian Delivery Methodology emphasizes gathering clear business and user requirements before development begins. This includes both functional requirements (what the system does
like uploading to a specific location) and user experience requirements (how the user interacts with the system).
Source: Appian Documentation
"The Appian Delivery Methodology." The "Initiate" phase of this methodology focuses on defining the project scope and capturing high-level requirements
which would include both A and D.
Keep practicing
Take the free ACD201 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other ACD201 practice questions
- Question 1Your client reported that a form in the application is very slow to load. You investigate…
- Question 2You're designing an expression rule that needs to retrieve employees from a database for …
- Question 3You run a report on different employee transactions by using a View. You encounter the fo…
- Question 15You're developing a user input form for a government services application that includes a…
