Appian ACD301 : Appian Lead Developer

You are on a call with a new client, and their program lead is concerned about how their legacy systems will integrate with Appian. The lead wants to know what authentication methods are supported by Appian. Which three authentication methods are supported?

• A. OAuth
• B. SAML
• C. CAC
• D. API Keys
• E. Active Directory
• F. Biometrics

You add an index on the searched field of a MySQL table with many rows (>100k). The field would benefit greatly from the index in which three scenarios?

• A. The field contains big integers, above and below 0.
• B. The field contains a structured JSON.
• C. The field contains a textual short business code.
• D. The field contains long unstructured text such as a hash.
• E. The field contains many datetimes, covering a large range.

While working on an application, you have identified oddities and breaks in some of your components. How can you guarantee that this mistake does not happen again in the future?

• A. Create a best practice that enforces a peer review of the deletion of any components within the application.
• B. Ensure that the application administrator group only has designers from that application's team.
• C. Design and communicate a best practice that dictates designers only work within the confines of their own application.
• D. Provide Appian developers with the "Designer" permissions role within Appian. Ensure that they have only basic user rights and assign them the permissions to administer their application.

On the latest Health Check report from your Cloud TEST environment utilizing a MongoDB add-on, you note the following findings:
Category: User Experience, Description: # of slow query rules, Risk: High Category: User Experience, Description: # of slow write to data store nodes, Risk: High Which three things might you do to address this, without consulting the business?

• A. Optimize the database execution using standard database performance troubleshooting methods and tools (such as query execution plans).
• B. Optimize the database execution. Replace the view with a materialized view.
• C. Reduce the size and complexity of the inputs. If you are passing in a list, consider whether the data model can be redesigned to pass single values instead.
• D. Use smaller CDTs or limit the fields selected in a!queryEntity().
• E. Reduce the batch size for database queues to 10.

You have an active development team (Team A) building enhancements for an application (App X) and are currently using the TEST environment for User Acceptance Testing (UAT).
A separate operations team (Team B) discovers a critical error in the Production instance of App X that they must remediate. However, Team B does not have a hotfix stream for which to accomplish this. The available environments are DEV, TEST, and PROD.
Which risk mitigation effort should both teams employ to ensure Team A's capital project is only minorly interrupted, and Team B's critical fix can be completed and deployed quickly to end users?

• A. Team B must address the changes directly in PROD. As there is no hotfix stream, and DEV and TEST are being utilized for active development, it is best to avoid a conflict of components. Once Team A has completed their enhancements work, Team B can update DEV and TEST accordingly.
• B. Team A must analyze their current codebase in DEV to merge the hotfix changes into their latest enhancements. Team B is then required to wait for the hotfix to follow regular deployment protocols from DEV to the PROD environment.
• C. Team B must communicate to Team A which component will be addressed in the hotfix to avoid overlap of changes. If overlap exists, the component must be versioned to its PROD state before being remediated and deployed, and then versioned back to its latest development state. If overlap does not exist, the component may be remediated and deployed without any version changes.
• D. Team B must address changes in the TEST environment. These changes can then be tested and deployed directly to PROD. Once the deployment is complete, Team B can then communicate their changes to Team A to ensure they are incorporated as part of the next release.