Free C1000-004 sample questions

Correct answer: In a `.ctx` file within the `codetable` directory and loaded via a `.dmx` file in the `data/initial` directory.

For system codes and other configuration data, the standard Cúram approach is to define them in code tables (`.ctx` files) and load them into the database using Data Manager Exchange (`.dmx`) files. Placing the `.dmx` file in the `data/initial` directory of the component ensures the data is loaded when the database is built or updated. This method makes the data database-resident, manageable, and part of the component's deployable assets, which is superior to using properties files or hard-coding values.

Correct answers: A custom UIM page (`.uim` file) defining the widget's internal structure.; A Java class that implements a custom Renderer.

A custom widget in Cúram often uses a UIM page to define its own layout and data connections, making it a self-contained UI component.

The Renderer class is the core of a custom widget. It contains the Java logic responsible for generating the final HTML, CSS, and JavaScript that will be rendered in the browser.

Correct answer: False

This statement is false. Directly modifying any file in the `gen` (generated) directory is a non-compliant customization. The Cúram generator overwrites these files during a build. The correct, compliant approach is to create a new, custom façade class in a custom component that extends the OOTB façade's interface and implementation, and then add the new method there.

Correct answer: Using the `WIZARD_STATE` page parameter automatically managed by the wizard framework.

The Cúram wizard framework provides a built-in state management mechanism. It automatically serializes the page data into a `WIZARD_STATE` page parameter, which is passed from one page to the next. Developers can access and modify this state object on each page of the wizard. This is the standard, compliant, and most efficient method, avoiding direct session manipulation or custom database tables for temporary wizard data.

Correct answer: A Deferred Process that is enqueued by the evidence creation logic.

A Deferred Process is the ideal solution for this scenario. It allows the main transaction (creating the evidence) to complete quickly and return control to the user, while the potentially long-running task (sending the email) is handled asynchronously in the background. The evidence creation logic would enqueue the deferred process, which then executes in a separate transaction. A standard method call would be synchronous and block the UI. A batch job is for scheduled, bulk processing, not immediate, event-driven tasks. A custom event could be used to trigger the deferred process, but the deferred process itself is the mechanism for the asynchronous execution.

Correct answer: In the `Application.prx` file.

The `Application.prx` file is the central location for defining application-wide properties, including localization settings like date and number formats. By setting the `curam.environment.default.dateformat` property in this file, a developer can enforce a consistent date format across the entire application for a specific locale. Modifying individual UIM files is inefficient, CSS cannot control date formatting logic, and `messages.xml` is for translatable text strings, not formatting rules.

Correct answer: Add an Index association from the entity to itself, selecting `accountNumber` and `routingNumber` as the indexed attributes.

The correct way to model a database index in Cúram is to create an Index association. This is a UML association stereotyped as ` >` that typically originates from and targets the same entity. In the properties of this association, the developer specifies which attributes of the entity are part of the index. The Cúram generator will then create the corresponding DDL for a unique or non-unique index during the database build. The other options do not result in the creation of a database index.

Correct answer: Façade

A Façade class is the ideal choice for this purpose. The Façade design pattern in Cúram is intended to provide a simplified, high-level interface to a complex subsystem. It is the standard place to aggregate calls to multiple Process or Entity objects to construct a data transfer object (DTO) or, in this case, the JSON response for a REST API. This keeps the JAX-RS resource class clean and focused on HTTP concerns, while the Façade handles the complex business logic.

Correct answer: Copy the entire new OOTB `.nav` file to the custom component folder and then merge the custom tab configuration into it.

The compliant approach for customizing artifacts like `.nav` files, especially after an upgrade, is to take the new version of the OOTB file, copy it to your custom component directory (maintaining the same folder structure), and then re-apply your specific customizations to this new copy. This ensures that all the new structural changes and features from the upgraded version are preserved, and your custom logic is correctly integrated. Simply overwriting the file or editing the OOTB file directly are non-compliant actions that will cause issues and be lost on subsequent builds or upgrades.

Correct answer: `EJBServer/build/svr/gen/ddl`

When the `build database` target runs, the Cúram generator creates the DDL scripts based on the UML models and places them in the `EJBServer/build/svr/gen/ddl` directory. This is the primary location for developers to find and inspect the SQL scripts that define the database schema, which is essential for troubleshooting database build failures.