One Automation 2013 Basic Certification Exam

It is possible to have a Workflow object inside of another Workflow because a Workflow object represents a sequence of tasks or actions that can be executed. Therefore, it is possible to include a Workflow object as one of the tasks or actions within another Workflow, creating a nested or hierarchical structure. This allows for more complex and modular workflows to be created, where smaller workflows can be combined to form larger workflows.

A VARA of type MULTI allows for the merging of the contents of two other VARAs. This means that the data from both VARAs can be combined into a single VARA, providing a consolidated view of the information. This can be useful for various purposes, such as data analysis or reporting, where a unified dataset is required. Therefore, the statement "True" is correct.

An active Automation Engine requires at least one Control Processor (CP) and one Workflow Processor (WP) to function properly. The CP is responsible for managing the overall execution of workflows and coordinating the activities of the WP. The WP, on the other hand, is responsible for executing the individual tasks within the workflows. Without both the CP and WP working together, the Automation Engine would not be able to automate and execute workflows effectively. Therefore, the statement is true.

The ESC key can be used to deactivate or remove a previously invoked Search view. This means that if a user has performed a search and wants to exit or cancel the search, they can simply press the ESC key to deactivate or remove the search view. This functionality is commonly found in various software applications and websites to provide a quick and easy way for users to cancel their search and return to the previous state.

In a workflow, variables can be defined at the workflow level and then passed down to the jobs within that workflow. This allows for the sharing and reuse of variables across multiple jobs in the workflow, making it easier to manage and maintain the variables used in the workflow. By specifying variables at the workflow level, it provides a centralized location for managing and updating the variables, ensuring consistency and efficiency in the workflow execution.

A QUEUE object can be used as a "quantity limiter" or "throttle" to limit how many Jobs can run concurrently. This means that the QUEUE object can control the number of jobs that are allowed to run at the same time, ensuring that only a certain quantity of jobs are running concurrently. By setting a limit on the number of jobs that can run, it helps in managing resources effectively and preventing overload situations.

The Rollback tab is available in every executable object that can be included in a Workflow. This means that for any executable object, such as a task or a process, the Rollback tab will be present. This tab allows users to configure rollback actions that will be executed if the workflow encounters an error or fails. Therefore, the statement "The Rollback tab is an object-specific tab that is available in every executable object that can be included in a Workflow" is true.

To "turn off" or disable a JOB object in every WorkFlow, the best way is to uncheck the Active box on the Job object. This action will effectively deactivate the JOB and prevent it from being executed in any of the WorkFlows. By unchecking the Active box, the system will no longer consider the JOB as an active component in the WorkFlows, ensuring that it does not run when the WorkFlows are executed.

The magnifying glass symbol in the upper left of the GUI is used for quick access to objects. It allows users to easily and quickly navigate to specific objects within the GUI without having to search for them manually. This feature enhances user efficiency and saves time by providing a convenient shortcut for accessing frequently used objects.

The statement is true because CTRL-F is a keyboard shortcut that is commonly used to invoke the search function in many applications, including Automic. This allows users to quickly search for specific keywords or phrases within multiple places in Automic, making it easier to locate and access the desired information.

The correct answer is "All of the Above" because all of the mentioned options are correct for the properties of a task within a workflow. A task can have an earliest start time, which allows it to be scheduled to start at a specific time. It can also specify calendar criteria, which means it can be scheduled based on specific dates or days of the week. Pre-conditions can be established for a task, which means certain conditions must be met before the task can be executed. Lastly, a task can be put on hold or set a breakpoint, which means its execution can be paused or stopped temporarily.

This statement is true because in a computing system, all executable objects, such as processes or threads, need to be started within a queue object. A queue is a data structure that follows the "first-in, first-out" principle, meaning the objects are processed in the order they are added to the queue. By starting executable objects within a queue object, it ensures that they are executed in a sequential and organized manner, preventing any conflicts or concurrency issues.

Pre and Post Conditions are task properties within a Workflow. They define the conditions that must be satisfied before and after the execution of a task. These conditions help to ensure that the task is executed correctly and that any necessary dependencies or requirements are met. Therefore, the statement that Pre and Post Conditions are only available as task properties within a Workflow is true.

When a new client is created, an associated CLIENT_QUEUE object is automatically created. This suggests that the system has a mechanism in place to handle client requests and manage them in a queue. This ensures that clients are serviced in the order they arrive, allowing for efficient and organized handling of client interactions.

The explanation for the given correct answer is that in the Explorer view shown in the screenshot, the 'Search' field does not only allow for searching based on object name. It is possible to search based on other criteria such as object type, date modified, or any other relevant attribute. Hence, the statement that the 'Search' field allows for searching based on object name only is false.

Within a NOTIFICATION object, it is possible to specify a specific EMAIL recipient based on Calendar Day and Time. This means that the notification can be programmed to send an email to a specific recipient at a specific day and time. This feature allows for more customized and targeted notifications, ensuring that the right person receives the notification at the right time.

The statement is false because there are multiple ways to automate the activation of a task, not just by adding it to a SCHEDULE object. Other methods include using triggers, event-based activation, or using a workflow or automation tool.

The given statement is false. If a SCHEDULE object is stopped and submit times within the schedule are missed, the schedule will not automatically "catch up" and run the tasks that missed their submit windows. The schedule will only run the tasks according to their scheduled submit times, and any missed tasks will not be executed unless manually rescheduled.

The maximum amount of slots that can be defined for a QUEUE object is 999999.

It is possible to retrieve and view old messages from within the User-Interface even after they have completely scrolled off of the MESSAGE window.

The statement is false because the ECC (Enterprise Control Center) is not an alternate way to access Automic when the Automation-Engine CP & WP processes are down. The ECC is a web-based user interface that provides centralized control and monitoring of Automic processes, but it still relies on the Automation-Engine CP & WP processes to be functioning properly in order to access and manage the automation environment.

To specify the values required to run a job, the user needs to visit the ATTRIBUTES and PROCESS tabs within a JOB object. The ATTRIBUTES tab allows the user to define the specific attributes or properties of the job, such as the job name, description, and any input/output files. The PROCESS tab, on the other hand, is where the user can define the actual steps or processes that need to be executed as part of the job. By visiting both of these tabs, the user can provide all the necessary information and configurations needed to successfully run the job.

In order to schedule tasks, it is not necessary for every task to specify a Calendar and keyword. This statement is false.

The color status 'Purple' within a Workflow indicates that the task is started in Rollback mode.

A VARA of type 'Static' does not consist of a 'Key' and 4 'Values'. It is not only used to run a SQL command. It is not only available in client-0. Therefore, none of the above statements are true relative to a VARA of type 'Static'.

In the General task properties tab of a Workflow, you can define and set a "Time Checkpoint". This tab allows you to specify various general properties for the task, such as its name, description, priority, and other settings. The "Time Checkpoint" feature can be used to track the time at which the task reaches a certain milestone or checkpoint during the workflow execution.

A Connection Object is required to specify the FTP Address, Userid, and Password for a RA FTP Job. This object allows the user to establish a connection to the FTP server and provide the necessary credentials for authentication. It provides the necessary methods and properties to interact with the FTP server, such as uploading and downloading files. This object is specifically designed for managing FTP connections and is the correct choice for specifying the required information for a RA FTP Job.

The statement is false because when a Job uses a PROMPT object and is launched via a SCHEDULE object, the user will not be prompted for input at runtime. The purpose of the PROMPT object is to allow the user to provide input before the Job is executed. However, when the Job is scheduled to run automatically via the SCHEDULE object, there is no opportunity for the user to provide input at runtime. Therefore, the user will not be prompted for input in this scenario.

In a workflow, it is possible to specify an "Action" without a corresponding "Condition" when specifying conditions for a task. This means that an action can be performed without any specific condition needing to be met. This allows for flexibility in the workflow, as certain actions may not require a condition to be executed.

The given question asks about the types of workflows that can be created. The correct answer options are STANDARD, IF, and FOREACH. These are all valid types of workflows that can be created in various workflow management systems. VARA and LOOP are not mentioned as options in the question, so they are not included in the correct answer.

The given statement is false. To automatically restart a failed job within a Workflow, you cannot use the 'Result' tab. There may be other ways or features available within the Workflow system to handle failed jobs and restart them automatically, but the 'Result' tab is not one of them.

The statement that is true relative to specifying task 'Alias name' is that a script variable can be used in an Alias name. This means that instead of using a fixed name for the Alias, a dynamic value can be assigned to it using a script variable. This allows for flexibility and customization in the naming of the Alias based on the specific requirements of the task or workflow.

The value entered from a prompt can be accessed as a variable, allowing the user to input a value that can be used in the execution of the job. Selections from a prompt can also be the contents of a VARA, meaning that the user can choose from a list of options provided by the prompt, and that selection can be used as the contents of a VARA (variable array). Therefore, both statements are true.

A FILTER object is used to react to the content of the Automic report and to react to the content of an output file. It allows for filtering and processing of data based on specific criteria or conditions.

The statement is incorrect. Not all conditions are evaluated by the Automation Engine before a task is executed. In some cases, the conditions may not be evaluated at all, depending on the configuration or settings of the Automation Engine. Therefore, the correct answer is False.

Output Registration allows users to register output files generated by a job within the User Interface. Registered output files can be opened and accessed within the User Interface. Additionally, these registered files are immediately available after the job execution. Therefore, the statements "Registered output files can be opened within the User Interface" and "Registered files are immediately available after Job execution" apply to Output Registration.

The statement is false because for an EVENT object, the object to be activated is not specified on the PROCESS tab. The object to be activated is typically specified on the TRIGGER tab for an EVENT object.

The statement is false because the question states that it is possible to modify the CLIENT_QUEUE object and increase available queue slots. However, in reality, the ability to modify the object and increase the queue slots would depend on the specific implementation and design of the CLIENT_QUEUE object. Without any further information, we cannot assume that it is possible to modify the object and increase the queue slots.

In the Activities Window, if a task is "waiting for queue slot" within a stopped Queue, you cannot do "Ignore Queue limit" to get the task to run.

The given answer is correct. It states that the VARA object is of type FILELIST, which means it is a variable array that contains a list of files. Additionally, it mentions that the VARA provides a value list when it is accessed, indicating that when the VARA is used, it returns a list of values.