You're designing a file upload process that integrates with an external document management system.
Part of this process is to develop a start form with a file upload component, so that the user can upload multiple files.
The business has requested that the maximum file size that can be uploaded through this process is 1GB. Additionally, you're aware that the integration's API can accept files with a maximum file size of 3GB, but recommends no larger than 1GB.
Can the process be more performant without straining the application or integration?

• A. No. The file upload component is capable of accepting 1 GB files and the integration can handle this.
• B. Yes. Request the business allows for these files to be uploaded as an overnight process by storing large files in a staging table, so that adequate resources are available.
• C. Yes. Request the business reconsiders its requirements and find manual workarounds as it is not recommended to upload files of this size in both Appian and the integration.

The synced record Task has a self-referential relationship defined in the column parentTaskId. There is a many-to- one record relationship between the id and parentTaskId called parentTask.
For a given task ID, you need to return the task name and the parent task name.
What should you do?

• A. Create a sync-time custom record field on the Task record called parentName. Specify this field to return in the query field selection.
• B. Use a!queryRecordType() filtered on the task id once to return the task name and parent task ID. Query the record again to return the parent task name.
• C. Use a!queryRecordType() With a filter on the task id, with fields specified to return recordType!Task.name and recordType!Task.parentTask.name.

You're creating a new entity-backed record type without data sync enabled. Users in the "ACME Supervisors" group must be able to access the Delete Case related action on the record summary view.
What are two valid steps that you should perform to grant users the appropriate access?

• A. Add the "ACME Supervisors" group as a Viewer to the data store mapped to the record.
• B. Grant Viewer permissions to the underlying interface object for the Summary view.
• C. Add the "ACME Supervisors" group as a member of the "Database Editors" group and grant DELETE privileges.
• D. Update the record action security for "Delete Case" and include the "ACME Supervisors" group within the visibility settings.

You're creating an interface to display all the employees of a company on a staff list.
You decide to use a!gridField() to create a user grid to display information from the company's AAA_Employee record, which has 42 fields relating to various employee information. To avoid cluttering the grid, you want to show six (6) fields on the grid.
How should you optimize the interface?

• A. Call the function a!forEach() in a local variable and query the AAA_Employee for each employee separately by using a!queryRecordType() to loop through all employees as defined by a constant to be used in the data parameter of a!gridFieid().
• B. Query the AAA_Employee record using a!queryRecordType(), defining the six (6) fields you require to show in the "fields" parameterto be used in the data parameter of a!gridFieid().
• C. Using a local variable, query the AAA_Employee record using a!queryRecordType(), without defining the six (6) fields you require to show in the "fields" parameter to be used in the data parameter of a!gridFieid().