ACD301 practice question 2 of 10

As part of your implementation workflow, users need to retrieve data stored in a third-party Oracle database on an interface. You need to design a way to query this information. How should you set up this connection and query the data?

Full set: 45 questions
Answer options
A: Configure a Query Database node within the process model. Then, type in the connection information, as well as a SQL query to execute and return the data in process variables.
B: Configure a timed utility process that queries data from the third-party database daily, and stores it in the Appian business database. Then use a!queryEntity using the Appian data source to retrieve the data.
C: Configure an expression-backed record type, calling an API to retrieve the data from the third- party database. Then, use a!queryRecordType to retrieve the data.
D: In the Administration Console, configure the third-party database as a “New Data Source.” Then, use a!queryEntity to retrieve the data. Correct answer
Correct Answer:
D. In the Administration Console, configure the third-party database as a “New Data Source.” Then, use a!queryEntity to retrieve the data.
Explanation

The standard and most direct Appian method for connecting to an external relational database, such as Oracle, is to configure it as a data source in the Administration Console. This establishes the JDBC connection. Once the data source is configured, you can create a data store that points to it and define data store entities that map to the database tables or views. The a!queryEntity() function can then be used directly within an interface expression to query this data in real-time, providing an efficient and scalable solution for displaying external data to users.

Why Incorrect

A. The Query Database smart service in a process model is primarily for workflow automation, not for populating user interfaces. Using it for UI data retrieval introduces unnecessary latency and complexity.
B. This describes a data synchronization or caching pattern. It does not provide a real-time query of the third-party database and introduces data staleness, which may not meet user requirements.
C. This approach is incorrect because it suggests using an API to connect to a database. The standard and more direct method is a JDBC connection configured via a data source, not an expression-backed record calling a web API.

References

1. Appian Documentation

Data Sources: "To connect to an external database

you must first create a data source in the Admin Console. A data source contains the connection information for a database." This establishes the first step outlined in the correct answer. (Appian 23.4 Documentation

"Data Sources" section).

2. Appian Documentation

Data Stores: "A data store is a reference to an external relational database... Each data store contains a reference to a data source... Once you have a data store and at least one data store entity

you can use the Query entity smart service or the a!queryEntity() function to query your data." This confirms the second part of the correct answer's workflow. (Appian 23.4 Documentation

"Data Store" object page).

3. Appian Documentation

a!queryEntity(): "The a!queryEntity() function is used to query a data store entity and return the result." This function is the standard mechanism for retrieving data from a configured data store for use in expressions

such as those that define an interface. (Appian 23.4 Documentation

"Querying Data From a Data Store Entity" page).

Scroll to Top