DEV01 Practice Questions

The Session Log in Control Room is the primary tool for post-mortem analysis of a process run. It provides a detailed, step-by-step record of the execution. When a process terminates due to an exception, the log will highlight the exact stage that failed, show the exception details, and display the values of all data items at the time of the failure. This allows for precise and efficient troubleshooting without needing to re-run the process.

This is false. A core best practice is the separation of concerns. Business Objects should be responsible only for interacting with a specific application's user interface. They should be 'dumb' components that click buttons, read text, etc. All business logic, decision-making, and process orchestration should reside in the Process Layer (Process Studio). This makes the Business Object highly reusable across different processes and centralizes the business rules where they are easier to manage and update.

The 'Web Href' attribute specifically captures the URL target of a hyperlink (the href property in HTML). Since the target URL '/products/special-offer' is unique on the page, using this attribute provides a very stable and specific identifier for the element, even if its visible text or position changes.

When an unhandled exception occurs within a sub-page, control is passed up to the calling page (the main page in this case). The exception is caught by the Recovery Block on the main page. Execution then proceeds to the Resume stage. The Resume stage directs the flow to the next stage immediately following the block on the main page, which would be the 'Step 3: Generate Report' Page stage. It does not re-enter the failed sub-page.

The Blue Prism Scheduler provides advanced options for monthly schedules. The correct and most direct way to configure this is to use the built-in functionality. By selecting the 'Monthly' frequency and then choosing the specific options for 'The last' 'Friday' of the month, the developer can create a precise schedule without requiring any complex logic within the process itself. This is the most efficient and maintainable approach.

This is the most robust solution. Using a wildcard on the dynamic part of the ID attribute ('submit-btn-*') allows Blue Prism to match the element regardless of the session-specific suffix. Combining this with a static attribute like the button's text ('Value') ensures a unique and reliable match, preventing accidental interaction with other elements that might share a similar partial ID.

Each interactive stage in Object Studio (like Read, Write, Navigate) has its own Timeout property. Setting a reasonable timeout (e.g., 30 seconds) on the specific stage that interacts with the thick-client application will cause the stage to throw an exception if the application does not respond within that period. This prevents the process from hanging and allows for structured exception handling.

Work Queues are essential for managing the new orders. They provide a scalable and resilient way to distribute work items (orders) to multiple Digital Workers, ensuring each order is processed exactly once.

Environment Locks are required to ensure exclusive access to the inventory system. By acquiring a lock before interacting with the desktop app and releasing it after, the process prevents other concurrent sessions from interfering, thus maintaining data integrity.

Excessive stage logging, especially within high-frequency loops, creates a significant performance overhead. Each logged stage requires a write operation to the Blue Prism database. In a loop with thousands of iterations, this results in thousands of database writes, which drastically slows down process execution and increases the load on the database server. Disabling logging for non-critical, repetitive stages is a key best practice for production performance.

This is false. The best practice is to separate 'Launch' and 'Attach' logic into distinct actions. The 'Launch' action should only start the application. A separate 'Attach' action should be created to connect to an already running instance. This allows a single running application instance to be shared across multiple processes without each process attempting to launch a new instance, which is crucial for efficiency and resource management.