Pass the IBM IBM Certified Administrator C1000-174 Questions and answers with CertsForce

WebSphere Application Server 9.0.5 on distributed platforms uses the IBM SDK, Java Technology Edition, and the product is designed so that the Java SDK is serviced separately from the application server's own code. The SDK can be installed and updated as a package in its own right through Installation Manager, and the managesdk command lets administrators choose which installed SDK a profile uses. That separation means a new SDK service release can be applied without waiting for an application server fix pack, which supports option D, that the Java SDK version can be updated independently.

The other statements are less accurate for this release. Option A claims that both 32-bit and 64-bit SDKs are supported, but the product now runs on 64-bit platforms only, so a 32-bit SDK is not supported. Option B says the SDK is embedded with the product, whereas it is delivered as a separate package that Installation Manager installs alongside the server. Option C suggests that SDKs used with version 8.5.5 are supported, but each release supports the SDK levels that IBM certifies for it, and the earlier release's Java 6 and 7 levels are not.

After updating an SDK, administrators should use managesdk to verify and, where required, change the default or per-profile SDK, restart the servers, and check the Java level from the startup messages.

Resource bindings connect the resource references declared in an application, such as data sources, EJB references, and message destinations, to actual resources defined in the server's JNDI namespace. During installation the application must receive those bindings, and the different installation paths vary in how much control they give over them. The administrative console installation wizard presents binding panels for each module and reference. The wsadmin scripting interface, using AdminApp.install, accepts binding options and binding files, so bindings can be supplied programmatically. Rapid deployment tools, through their annotation-driven approach, can generate bindings as part of the deployment package, which supports resource binding in those packages.

The monitored directory is the exception. When an application archive is copied into the monitored directory, the server installs it automatically, applying default bindings and without presenting any opportunity to adjust them. Because the deployment happens unattended, the administrator cannot specify the resource bindings at that time, and any adjustment has to be made afterward through the console or wsadmin. Option B is therefore the one that does not offer resource binding.

This limitation makes the monitored directory best suited to development and test environments, in which defaults are acceptable. For production releases, an installation method that permits explicit bindings is preferable because it avoids a corrective step after deployment and reduces the risk of an application starting against a wrong resource.

Application migration reports in the administrative console classify each finding by severity, and the categories are shown with distinct icons on the enterprise application collection page. Severe issues identify APIs that are unavailable on the target runtime, or behavioural changes that can break the application. Warning issues identify behavioural changes that might break the application and that deserve evaluation. Recommendations are informational findings: they cover deprecated APIs or minor behavioural changes that do not affect most applications. Option C is therefore correct.

Option A, Fatal, is not a category used by the migration report, so it can be dismissed on terminology alone. Option B, Severe, is the opposite end of the scale and is reserved for items that must be resolved before the application can run correctly on the target. Option D, Warnings, applies to changes that could break an application depending on how it uses the affected behaviour; those findings call for review rather than being merely advisory.

In practice, a reviewer should work through Severe items first, assess each Warning against actual application usage, and treat Recommendations as optional clean-up that reduces future migration effort. Recommendations alone should not block a move to the target environment, which is why they are labelled informational rather than as a defect.