Free IBM C1000-174 Exam Practice Questions & Explanations
Prepared & Reviewed by the ValidExamDumps Editorial Team
At ValidExamDumps, we consistently monitor updates to the IBM C1000-174 exam questions by IBM. Whenever our team identifies changes in the exam questions, objectives, focus areas or requirements, We immediately update our exam questions for both PDF and online practice exams. This commitment ensures our customers always have access to the most current and accurate questions. By preparing with these up to date and 100% exam domain coverage questions, our customers can successfully pass the IBM WebSphere Application Server Network Deployment v9.0.5 Administrator exam on their first attempt without needing additional materials or study guides.
Other certification materials providers often include outdated or removed questions by IBM in their C1000-174 exam. These outdated questions lead to customers failing their IBM WebSphere Application Server Network Deployment v9.0.5 Administrator exam. In contrast, we ensure our questions bank includes only precise and up-to-date questions. Our main priority is your success in the IBM C1000-174 exam, not profiting from selling obsolete exam questions in PDF or Online Practice Test.
What is the proper sequence for setting up LTPA SSO between two WebSphere cells?
Lightweight Third Party Authentication tokens are encrypted and signed with keys held in each cell's configuration. A token generated in one cell can only be accepted by another cell if both cells share the same LTPA keys, along with the same password and a compatible realm configuration. Single sign-on between two cells is therefore set up by taking the keys from one cell and placing them in the other. The sequence is to export the LTPA key from the first cell to a file, using the console's LTPA page or the exportLTPAKeys wsadmin task, and then to import that file into the second cell. Option A describes this: export from Cell A and import to Cell B. The other sequences are not workable. Option B proposes importing the key to a text file, which is not an import into a cell and so does not share the key. Option C generates a key in Cell A, exports from Cell B, and imports to Cell A, which mixes the cells' roles and ends with Cell B's key unchanged, so the cells do not end up holding the same key. Option D exports from both cells, and neither cell receives the other's key. After importing, the administrator saves the configuration, and generally restarts servers so that the new keys take effect. The user registries of the cells should resolve users to the same identities, and the domain name for the SSO cookie should be common to both.
An administrator configured database session persistence for an application deployed to a WebSphere Application Server ND cluster. Application users have begun reporting data loss in HTTP session objects. How can the administrator resolve the issue with database session persistence?
Database session persistence stores HTTP session data in a table of a relational database, so that sessions survive a server failure and can be shared among cluster members. The product offers two layouts. In the single-row schema, all of the session's data is held in one row, and the size of that row is limited by the database's row size, so large sessions can exceed the limit and be truncated or lost. In the multi-row schema, a session's data is spread across several rows, which removes the limit on session size and allows large sessions to be saved without loss. When users report data loss in session objects, the likely cause is large session data exceeding the single-row limit. The remedy is to select the multi-row schema on the session data source, drop the existing session table, and let the product recreate it with the new layout. Option B is correct. Option A, periodic writing, would raise the risk of loss between writes because data changed since the last write is lost on failure. Option C, switching to memory-to-memory replication, changes the persistence mechanism altogether and does not correct the cause. Option D, enlarging the buffer pool and page size, may help the database performance but does not address a limit on the session's data in a row. Dropping the table discards existing sessions, so the change should be scheduled for a quiet period, with users informed of the need to log in again.
Which wsadmin command generates migration reports for one or more enterprise applications in WebSphere Application Server ND?
Migration reports for enterprise applications are produced through administrative tasks. In wsadmin the AdminTask object provides createMigrationReport, which analyses one or more installed applications against a target, identifies issues, and stores the report with the application. Option A is correct. The task accepts parameters that identify the application or applications and the target of the analysis, and the resulting report can then be viewed in the console or with getMigrationReport. The matching console action is the Analyze button on the enterprise applications page. The other commands do not exist or belong to a different object. AdminConfig.getMigrationReport, option B, combines a real task name with the wrong object, since AdminConfig deals with configuration objects and does not provide migration report functions. AdminConfig.getMigrationSummary, option C, is not a command in the product. AdminTask.createMigrationRecord, option D, uses a made-up command name, since the term used is "report". Because the report depends on the application files, administrators must regenerate it after any redeployment, which removes the earlier version automatically. When many applications are to be assessed, a script that loops through the installed applications and calls createMigrationReport for each is an effective way to produce the whole set, and the reports can be examined together to plan the order of migration.
An administrator attempted to install an interim fix with Installation Manager, but the installation failed with this error: CRIMA1228E ERROR: Cannot find profile: null.
Investigation showed that the Installation Manager agent data location was set to a location other than the default. Which parameter must be provided to the imcl install command to set the correct agent data location and install the interim fix successfully?
Installation Manager keeps its record of installed products and its working state in an agent data location. If the installation was performed with a non-default data location, any later operation, such as installing an interim fix, has to be pointed at the same place, otherwise Installation Manager looks at the default registry, cannot find the installation, and reports an error such as "Cannot find profile: null". The parameter that tells imcl which data location to use is -dataLocation, so option D is correct. The command might look like imcl install with the fix identifier, the -installationDirectory option, the -repositories option, and -dataLocation followed by the path used originally. The other parameters are not imcl options. -appdataLocation and -agentdataLocation are plausible labels, but they do not exist as arguments. The -sharedResourcesDirectory option governs the shared resources directory, which is a different concept from the agent data location, and the name shareddataLocation in option B is not used. Because the same location must be used consistently, administrators who use non-default data locations should record the value in their procedures. The imcl listInstalledPackages command with -dataLocation can also be used to confirm that the registry in that location holds the installation before the fix is applied.
An administrator installed WebSphere Application Server ND, an IBM HTTP Server, and the IHS web server plug-in by using Installation Manager as a non-root user on a VM.
Which two statements are true when setting up a local web server based on this configuration?
Choose two
Installing the application server, IBM HTTP Server, and the plug-in with Installation Manager on one virtual machine produces a local web server whose plug-in configuration can be created with the Web Server Plug-ins Configuration Tool. Two statements about such a setup are true. Propagation of the plugin-cfg.xml file is supported: when the web server is defined as a node in the cell, the deployment manager or node can copy the generated plug-in file to the web server's configuration directory, so changes to applications and clusters reach the plug-in. And the installation was performed by a non-root user, so the web server cannot bind to a port below 1024; the default HTTP port 80 is privileged on Linux, and the administrator must change the port to a value above 1024, such as 8080. Options B and E are correct. Option A is incorrect because automatic generation of the plug-in configuration remains available when the web server is defined as a managed or unmanaged node. Option C is incorrect because the configuration tool, or an equivalent definition, is still needed to establish the web server definition for the unmanaged node. Option D is incorrect because an unmanaged IHS server cannot be controlled through the administrative console, whereas administration through the IHS administration server requires a managed arrangement. After the port change, the plug-in is regenerated and propagated, and the web server is restarted.
