[2024年08月]更新のACD300試験事前練習テスト試験問題と解答Appian Certification Program学習ガイド [Q20-Q36]

20、For each scenario outlined, match the best tool to use to meet expectations. Each tool will be used once Note: To change your responses, you may deselected your response by clicking the blank space at the top of the selection list.

21、You are running an inspection as a part of the first deployment process from TEST to PROD. You receive a notice that one of your objects will not deploy because it is dependent on an object from an application owned by a separate team.
What should be your next step?

Create your own object with the same code base, replace (he dependent object in the application. and deploy to PROO.

Halt the production deployment and contact the other team tor guidance on promoting the object to PROD

Check the dependencies of the necessary object Deploy w PROO if there are few dependencies and it is low risk

Push a functionally viable package to PROD without the dependencies, and plan the rest o! the deployment accordingly with the other team’s constraints

22、You are presented with the following application requirement:
Users must be able to navigate throughout the application while maintaining complete visibility in the application structure, and easily navigate to previous locations.” Which Appian Interface Pattern would you recommend?

Use Bullous as Cards pattern on the home page lo prominently display application choices.

Implement an Activity History pattern to track an organizations activity measures.

implement a drilldown report pattern to show detailed information about report data.

Include a breadcrumbs pattern on applicable inert aces to show the organizational hierarchy

23、Your application contains a process model that Is scheduled to run daily at a certain time, which kicks off a user input task to a specified user on the 1ST time zone for morning data collection The time zone is set to the (default) pm!timezone.
In this situation, what does the pm!tinezone reflect?

The time zone of the server where Applan is intuited

The line zone of the user who most recently published the process model

The default time zone for the environment as specified in the Administration Console

The time zone of the user who is completing the input task.

24、You ate in a backlog refinement meeting with the development team and the product owner. You review a story for an integration Involving a third-party system. A payload will be sent from the Appian system through the integration to the third-party system. The story is 21 points on a Fibonacci scale, and requires development from your Appian learn, as well as the technical resources from the third-party system. This item is crucial to your project s success.
What are the two recommended steps to ensure this story can be developed effectively?

Acquire testing steps from QA resources

Identify subject matter experts (SMEs) to perform user acceptance testing (UAT)

Maintain a communication schedule with the third-party resources

Break down the item into smaller stones

25、You are asked to design a case management system for a client in addition to storing some basic metadata about a case, one of the client s requirements Is the ability for users to update a case The client would like any user in their organization of 500 people to be able to make these updates The users are all based in the company’s headquarters, and there will be frequent cases where users are attempting to edit the same case. The client wants to ensure no information Is lost when these edits occur and does not want the solution to burden their process administrators with any additional effort.
Which data locking approach should you recommend?

Allow edits without locking the case GDI

Use the database lo implement tow lewd pessimistic locking.

Add an Version annotation to the case COT to manage Vie locking

Design a process report and query to determine who opened the edit form first

26、You are on a protect with an application that has been deployed to Production and is live with users. The client wishes to increase the number of active users.
You need to conduct load testing to ensure Production can handle the increased usage Review the specs for four environments in the following image.

Which environment should you use for load testing7

acmeuat

acmedev

acme

acmetest

27、Your Agile Scrum project requires you to manage two teams, with three developers per team. Both teams are to work on the same application In parallel.
How should the work be divided between the teams, avoiding issues caused by cross-dependency?

Have each team choose the stones they would like to work on based on personal preference

Group epics and stones by technical difficulty, and allocate one team the more challenging stories

Group epics and stones by feature, and allocate work between each team by feature.

Allocate stories to each team based on the cumulative years of experience of the team members.

28、You are required to create an integration from your Appian cloud instance to an application hosted within a customers self-managed environment.
The customers IT team has provided you with a REST API endpoint to test with; httpsV/lnternal networkVapi/api /ping Which recommendation should you make to progress this integration?

Expose the API as a SOAP-basedweb service.

Deploy the API / service into Appian Cloud

Add Appian Cloud’s IP address ranges lo the customer network’s allowed IP listing

Set up a VPN tunnel

29、You are planning a strategy around data volume testing for an Appian application that queries and writes to MySQL database.
You have administrator access to the Appian application and to the database.
What are two key considerations when designing a data volume testing strategy?

Data from previous tests needs to remain in the testing environment prior to loading prepopulated data

large datasets must be loaded via Applan processes

The amount of data that needs to be populated should be determined by the project sponsor and the stakeholders based on their estimation

Testing with the correct amount of data should be in the definition of done as part of each sprint.

Data model changes must wait until towards the end of the protect.

Explanation
When designing a data volume testing strategy for an Appian application that queries and writes to MySQL database, you should consider two key considerations:
* Testing with the correct amount of data should be in the definition of done as part of each sprint. Data volume testing is a type of testing that verifies how well an application performs when handling large amounts of data. Data volume testing is important to ensure that the application meets the performance and quality requirements of the users and stakeholders. By including data volume testing in the definition of done as part of each sprint, you can ensure that each feature or functionality of your application is tested with realistic data volumes before being delivered to production. This way, you can identify and resolve any potential issues or bottlenecks early in the development cycle, and avoid any surprises or delays later on.
* Data model changes must wait until towards the end of the project. Data model changes are changes that affect the structure or schema of your database, such as adding, modifying, or deleting tables, columns, indexes, or constraints. Data model changes are risky and costly to make, especially when dealing with large amounts of data. Data model changes can affect the performance, functionality, or integrity of your
* application and database. Therefore, data model changes must wait until towards the end of the project, when you have finalized your requirements and design decisions, and have minimized your data volume testing efforts. By waiting until towards the end of the project to make data model changes, you can reduce the impact and complexity of those changes, and avoid any unnecessary rework or regression.
The other options are not as effective. Option A, data from previous tests needs to remain in the testing environment prior to loading prepopulated data, is not a key consideration for designing a data volume testing strategy, but rather a best practice for preparing your testing environment. Option B, large datasets must be loaded via Appian processes, is not a key consideration for designing a data volume testing strategy, but rather a technical implementation detail that may or may not be suitable for your application. Option C, the amount of data that needs to be populated should be determined by the project sponsor and the stakeholders based on their estimation, is not a key consideration for designing a data volume testing strategy, but rather an input or assumption that you need to validate before conducting your data volume testing.

30、As part of an upcoming release of an application, a new nullable field is added to a table that contains customer dataThe new field is used by a reportin the upcoming release, and is calculated using data from another table.
Which two actions should you consider when creating the script to add the new field?

Create a script thatadds the held and leaves it null.

Create a rollback script that removes the field.

Create a script that adds the field and then populate it

Create a rollback script that clears the data from the field

Add a view that joins the customer data to the data used in calculation

31、You need to design a complex Appian integration to call a RESTful API. The RESTful API will be used to update a case in a customer’s legacy system.
What are three prerequisites for designing the integration?

Define the HTTP method that the integration will use.

Understand the content of the expected body. Deluding each field type and their limits

Understand whether this integration will be used in an interface or in a process model

Understand the different error codes managed by the API and the process of error handing m Appall

Understand the business rules to be applied to ensure the business logic of the data

Explanation
To design a complex Appian integration to call a RESTful API, you need to have some prerequisites, such as:
* Define the HTTP method that the integration will use. The HTTP method is the action that the integration will perform on the API, such as GET, POST, PUT, PATCH, or DELETE. The HTTP method determines how the data will be sent and received by the API, and what kind of response will be expected.
* Understand the content of the expected body, including each field type and their limits. The body is the data that the integration will send to the API, or receive from the API, depending on the HTTP method.
The body can be in different formats, such as JSON, XML, or form data. You need to understand how to structure the body according to the API specification, and what kind of data types and values are allowed for each field.
* Understand the different error codes managed by the API and the process of error handling in Appian.
The error codes are the status codes that indicate whether the API request was successful or not, and what kind of problem occurred if not. The error codes can range from 200 (OK) to 500 (Internal Server Error), and each code has a different meaning and implication. You need to understand how to handle different error codes in Appian, and how to display meaningful messages to the user or log them for debugging purposes.
The other two options are not prerequisites for designing the integration, but rather considerations for implementing it.
* Understand whether this integration will be used in an interface or in a process model. This is not a prerequisite, but rather a decision that you need to make based on your application requirements and design. You can use an integration either in an interface or in a process model, depending on where you need to call the API and how you want to handle the response. For example, if you need to update a case in real-time based on user input, you may want to use an integration in an interface. If you need to update a case periodically based on a schedule or an event, you may want to use an integration in a process model.
* Understand the business rules to be applied to ensure the business logic of the data. This is not a prerequisite, but rather a part of your application logic that you need to implement after designing the integration. You need to apply business rules to validate, transform, or enrich the data that you send or
* receive from the API, according to your business requirements and logic. For example, you may need to check if the case status is valid before updating it in the legacy system, or you may need to add some additional information to the case data before displaying it in Appian.

32、You are deciding the appropriate process model data management strategy.
For each requirement. match the appropriate strategies to implement. Each strategy will be used once.
Note: To change your responses, you may deselect your response by clicking the blank space at the top of the selection list.

Explanation

Requirement: Archive processes 2 days after completion or cancellation. Correct match: A. Processes that need to be available for 2 days after completion or cancellation, after which are no longer required nor accessible Exact explanation of correct match taken from Appian Documentation: This strategy is called
“Archive after 2 days” and it is one of the options for process model data management in Appian. This strategy means that processes that complete or cancel will remain available for 2 days, after which they will be archived and no longer accessible. This strategy can help reduce the size of the process database and improve the performance of process reporting.
Requirement: Use system default (currently auto-archive processes 7 days after completion or cancellation).
Correct match: C. Processes that remain available for 7 days after completion or cancellation, after which are archived when accessed Exact explanation of correct match taken from Appian Documentation: This strategy is called “Use system default” and it is one of the options for process model data management in Appian. This strategy means that processes that complete or cancel will remain available for 7 days, after which they will be archived when accessed. This strategy can help balance the availability and performance of process data, as it allows processes to be archived on demand rather than on a fixed schedule.
Requirement: Delete processes 2 days after completion or cancellation. Correct match: B. Processes that need to be available for 2 days after completion or cancellation, after which remain accessible Exact explanation of correct match taken from Appian Documentation: This strategy is called “Delete after 2 days” and it is one of the options for process model data management in Appian. This strategy means that processes that complete or cancel will remain available for 2 days, after which they will be deleted and no longer accessible. This strategy can help reduce the size of the process database and improve the performance of process reporting, but it also means that process data will be permanently lost.
Requirement: Do not automatically clean-up processes. Correct match: D. Processes that need to remain available without the need to unarchive Exact explanation of correct match taken from Appian Documentation: This strategy is called “Do not automatically clean-up” and it is one of the options for process model data management in Appian. This strategy means that processes that complete or cancel will remain available indefinitely without being archived or deleted. This strategy can help ensure the availability and integrity of process data, but it also means that the process database will grow over time and affect the performance of process reporting.

33、You are taking your package from the source environment and importing it into the target environment.
Review the errors encountered during inspection:
Whatis the first action you should take to Investigate the issue?

Check whether the object(UUIDending in 18028821) is included in this package

Check whether the object(UUD ending in 7t00000i4e7a)is included in this package

Check whether the object (UUID ending in 25606) is included in this package

Check whether the object (UUID ending in 18028931) is included in this package

34、You have 5 applications on your Appian platform in production. Users are now beginning to use multiple applications across the platform, and the client wants to ensure a consistent user experience across all applications You notice that some applications use rich text some use section layouts, and others use box layouts. The result is that each application has a different color and size for the header.
What would you recommend to ensure consistency across the platform?

Create constants for text size and color, and update each section lo reference these values.

In the common application, create a rule that can be used across the platform for section headers, and update each application to reference this new rule

In the common application, create one rule for each application, and update each application to reference its respective rule

In each individual application, create a rule that can be used lot tot section headers, and update each application lo reference its respective rule