IBM Tivoli Netcool Omnibus multiple choice Question and Answer

Multiple Choice Q & A

1.A company is deploying a multi-tiered architecture with collection, aggregation, and display layers. Which stepsare required to create the primary and backup aggregation ObjectServers?

A) Configure the omni.dat or Server Editor and generate the interfaces file for NCOMS_P, NCOMS_B and NCOMS_V.Run nco_dbinit with the -customconfigfile option to load the aggregation.sql and initialize the ObjectServer.Start the ObjectServers NCOMS_P and NCOMS_B.
B) Configure the omni.dat or Server Editor and generate the interfaces file for AGG_P, AGG_B and AGG_V.Run nco_dbinit with the -customconfigfile option to load the primary.sql or backup.sql and initialize the ObjectServerStart the ObjectServers AGG_P and AGG_B.
C) Configure the omni.dat or Server Editor and generate the interfaces file for AGG_P, AGG_B and AGG_V.Run nco_dbinit with the -customconfigfile option to load the aggregation.sql and initialize the ObjectServer.Start the ObjectServers AGG_P and AGG_B.
D) Configure the omni.dat or Server Editor and generate the interfaces file for NCOMS_P, NCOMS_B and NCOMS_V.Run nc o_dbinit with the -customconfigfile option to load the primary.sql or backup.sql and initialize theObjectServer.Start the ObjectServers AGG_P and AGG_B

2.The command nco_store_resize -newhardlimit 500mb changes which hard limit to 500MB?

A) the memstoreoftheNCOMS ObjectServer
B) the amount of disk space available for the IBM Tivoli Netcool/OMNIbus installation
C) the memory footprint of any OMNIbus process
D) the amount of memory available to probe buffering

3.When configuring a Backup ObjectServer, what are the default property values for ActingPrimary andBackupObjectServer?
A) ActingPrimary is TRUE and BackupObjectServer TRUE
B) ActingPrimary is FALSE and BackupObjectServer FALSE
C) ActingPrimary is TRUE and BackupObjectServer FALSE
D) ActingPrimary is FALSE and BackupObjectServer TRUE
4.When upgrading probes, what does the UPGRADE.SH script do?

A) It overwrites the probe older versions with the latest versions.
B) It reinstalls the probes and migrates data to the $NCHOME/omni bus/probes/mi grated directory
C) It migrates probes data to the $NCHOME/omni bus/probes/mi grated directory.
D) It configures the probe files (rules and props) with the latest available information
5.Which combination of properties can be used to enable an ObjectServer to serve files to a HTTP client?

A) NHttpd.EnableHTTP, NHttpd.ListeningPort, NHttpd.SSLEnable, NHttpd.SSLListeningPort
B) NHttpd.AuthenticationDomain, NHttpd.SSLCertificate, NHttpd.DocumentRoot, NHttpd.EnableFileServing
C) NHttpd.DocumentRoot, NHttpd.EnableFileServing, NHttpd.AccessLog, NHttpd.EnableHTTP
D) NHttpd.EnableHTTP, NHttpd.ListeningPort, NHttpd.DocumentRoot, NHttpd.EnableFileServing

6.Which command line tool does the WebGUI administrator use to export and import portal data?

A) export.sh
B) webportal.bin
C) tipcli.sh
D) run_waapi

7.What are wires used for when developing a custom set of pages in the WebGUI portal?

A) to link portlets in different workspaces
B) to allow the communication of information between two different users using the same custom portal page
C) to create a link to publish content from one page to another
D) to route or connect client-side events between source and target portlets

8.In the multi-tiered architecture, when an event is reinserted from the collection to the aggregation layer, what is the default deduplication behavior for severity?

A) The severity is changed only if the incoming severity is higher than the existing severity.
B) Only closed events are reawakened on deduplication. The severity is changed only if the old severity is 0 (clear) and thenew severity is greater than 0 (not clear).
C) The Severity field is always updated on deduplication. The severity from the collection layer will overwrite the severity atthe aggregation layer.
D) The Severity field is never updated on deduplication. The severity from the collection layer is dropped and the severity atthe aggregation layer is kept unchanged.
9.The WAAPI host, port, username, password is configured in which file?

A) $NCHOME/omnibus_webgui/etc/waapi.init
B) $NCHOME/omnibus_webgui/waapi/etc/server.init
C) $NCHOME/omnibus_webgui/etc/server.init
D) $NCHOME/omnibus_webgui/waapi/etc/waapi.init

10.The optional nco_security section of a ProcessAgent config file is used for what?

A) to list commands/binaries that the ProcessAgent will run from a remote request
B) to configure how username/passwords are authenticated for incoming connections to that ProcessAgent
C) to configure a whitelist of all hosts that the ProcessAgent will accept incoming connections from
D) to list usernames/passwords that are required for authentication connections to other Process Agents

11.Review the output from a rules file syntaxcheck:What is the cause of this error?

A) CustomerD is not a valid parameter.
B) A call to an undefined variable CustomerD was made on line 39 in the rules file.
C) CustomerD was not set properly in the rulesfile.
D) The CustomerD field does not exist in the ObjectServer NCOMS_P.
12.An ObjectServer has been set up to create checkpoint files, and a utility is available to check the validity of the checkpoint files. Which command checks the files?

A) nco_storepoint
B) nco check_store
C) nco_check_file
D) nco_checkpoint

13.A consultant is working on an IBM Tivoli Netcool/OMNIbus V7.2.1 ObjectServer upgrade to V7.4.Which high level steps migrate the key database?

A) move the omni.kdb file to a temporary location, create a new key database with nc_gskcmd, import the certificates
B) move the omni.kdb file to a temporary location /nc_gskcmd withthe-load //omni.kbd
C) export the omni.kdb file to a flat file with nco_g_crypt -d, create a new key database with nc_gskcmd, import thecertificates
D) move the omni.kdb to a temporary location, perform the upgrade, move the omni.kdb into the$NCHOME/ etc/security/keys directory

14.A company is deploying a multi-tiered architecture with a collection, aggregation, and display layers. Which steps are required to create a pair of collection layer ObjectServers?

A) Configure the omni.dat or Server Editor and generate the interfaces file for COL_P_1, COL_B_1 and COL_V_1Edit the properties file for COL_P_1 and COL_B_1 to specify the ObjectServers as collection ObjectServers.Start the ObjectServers COL_P_1 and COL_B_1.
B) Configure the omni.dat or Server Editor and generate the interfaces file for COL_P_1, COL_B_1 and COL_V_1Run nco_dbinit with the -customconfigfile option to load the collection.sql to initialize the ObjectServers.Start the ObjectServers COL_P_1 and COL_B_1.
C) Configure the omni.dat or Server Editor and generate the interfaces file for COL_P_1, COL_B_1 and COL_V_1Run nco_dbinit with the -customconfigfile option to load the collection.sql.Start the ObjectServers COL_P_1, COL_B_1 and COL_V_1.
D) Configure the omni.dat or Server Editor and generate the interfaces file for COL_P_1, COL_B_1 and COL_V_1Start the ObjectServers COL_P_1 and COL_B_1.
15.What is the default location of the ObjectServer, probe, and gateway log files?

A) $NCHOME/log
B) $OMNIHOME/omnibus/log
C) $NCHOME/probes/log
D) $NCHOME/omnibus/log
Answers :-
1-C 2-D 3-C 4-C 5-D 6-C 7-D 8-C 9-D 10-C 11-D
12-B 13-A 14-B 15-D

SQL Constraint

Constraint

Constraint :- Constraints are set of rules that are applied on column/columns.

The Constraints always enforce the rules and prevent invalid data in a table. If Constraint not satisfy it’ll be violated, that means if Constraint condition does not satisfy for the DML operations then operations will not permitted.

Type of Constraints:-

1) Primary Key
2) Unique Key
3) Check Constraint
4) Not Null
5) Foreign Key

Primary Key :- Primary key is a combination of NOT NULL and UNIQUE Key Constraint, Primary key never allow duplicate values and null values in the column.

Unique Key : – Unique Key does not allow duplicate value but it accept NULL value many times (As every null is unique and never equal to another null).

Check Constraint : – Check constraint check the condition which is specify on the column that must be TRUE.

Not Null Constraint : – NOT NULL Constraint never allow null values in column.

Foreign Key : – Foreign Key is a key in a table which is already defined as a primary/unique key in another/same table . Foreign Key create Parent-Child relationship. It accept values of reference column from master table or null values

Note :– Constraint can be defined at 2 levels

1) Column Level

2) Table Level

Composite Constraints :- If any constraint defined for more than one column then it called composite constraint.

Composite constraint can be defined in table level definition only.

Note :- Constraint can be created at the time of table creation or by alter command (After table creation).

CLASS PRACTICLE :-

Examples :- At the Table Creation

--------------------------PRIMARY KEY -----------------------------

1) Primary Key (Column Level) :-

a) With System defined name

SQL>create table student(regno number(10) primary key, name varchar2(10),dob date,course varchar2(10));

b) With User defined name

SQL>create table student(regno number(10) constraint pk_regno primary key,name varchar2(10),dob date,course varchar2(10));

2) Primary Key (Table Level) :-

a) With System defined name

SQL>create table student(regno number(10),name varchar2(10),dob date,course varchar2(10), primary key(regno));

b) With User defined name

SQL>create table student(regno number(10),name varchar2(10),dob date,course varchar2(10),constraint pk_regno primary key(regno));

3) Composite Primary Key :- Key, that is created for more that one column is called composite key. If Primary Key is created for more than one column then that Primary Key is called Composite Primary Key.

a) With System defined name

SQL>create table student(regno number(10),name varchar2(10),dob date,course varchar2(10), primary key(regno,name));

b) With User defined name

SQL>create table student(regno number(10),name varchar2(10),dob date,course varchar2(10),constraint pk_regno primary key(regno,name));

--------------------------UNIQUE KEY -----------------------------

1) Unique Key (Column Level) :-

a) With System defined name

SQL>create table student(regno number(10) unique, name varchar2(10),dob date,course varchar2(10));

b) With User defined name

SQL>create table student(regno number(10) constraint uk_regno unique,
name varchar2(10),dob date,course varchar2(10));

2) Unique Key (Table Level) :-

a) With System defined name

SQL>create table student(regno number(10),name varchar2(10),dob date,course varchar2(10), unique(regno));

b) With User defined name

SQL>create table student(regno number(10),name varchar2(10),dob date,course varchar2(10),constraint uk_regno unique(regno));

3) Composite Unique Key :- Unique Key created for more than one column is called Composite Unique Key.

a) With System defined name

SQL>create table student(regno number(10),name varchar2(10),dob date,course varchar2(10), unique(regno,name));

b) With User defined name

SQL>create table student(regno number(10),name varchar2(10),dob date,course varchar2(10),constraint uk_regno unique(regno,name));

--------------------------CHECK CONSTRAINT -----------------------------

1) Check Constraint (Column Level) :-

a) With System defined name

SQL>create table student(regno number(10), name varchar2(10),dob date,course varchar2(10) check (course in ('MCA','BCA')));

b) With User defined name

SQL>create table student(regno number(10), name varchar2(10),dob date,course varchar2(10) constraint ck_course check (course in ('MCA','BCA')));

2) Check Constraint (Table Level) :-

a) With System defined name

SQL>create table student(regno number(10),name varchar2(10),dob date,course varchar2(10), check (course in ('MCA','BCA')));

b) With User defined name

SQL>create table student(regno number(10),name varchar2(10),dob date,course varchar2(10),constraint ck_course check (course in ('MCA','BCA')));

3) Composite Check Constraint :-Check constraint defined for more than one column is called Composite Check Constraint.

a) With System defined name

SQL>create table student(regno number(10),name varchar2(10),dob date,course varchar2(10),check (course in ('MCA','BCA') and regno>1000));

b) With User defined name

SQL>create table student(regno number(10),name varchar2(10),dob date,course varchar2(10), constraint ck_regno check (course in ('MCA','BCA') and regno>1000));

--------------------------NOT NULL CONSTRAINT -----------------------------

1) Not Null Constraint :- (Only Column Level definition is possible)

a) With System defined name

SQL>create table student(regno number(10), name varchar2(10) not null,dob date,course varchar2(10) not null));

b) With User defined name

SQL>create table student(regno number(10), name varchar2(10) constraint nn_name not null,dob date,course varchar2(10));

--------------------------FOREIGN KEY -----------------------------

1) Foreign Key (Column Level) :-

a) With System defined name

SQL>create table courses (course_id number primary key,course_name varchar2(20));

SQL>create table student(regno number(10) primary key, name varchar2(10),dob date,course_id number
references courses(course_id));

b) With User defined name

SQL>create table courses (course_id number constraint pk_course_id primary key,course_name varchar2(20));

SQL>create table student (regno number(10) constraint pk_regno primary key, name varchar2(10),dob date,course_id number constraint fk_course_id references courses(course_id));

2) Foreign Key (Table Level) :-

a) With System defined name

SQL>create table courses (course_id number primary key,course_name varchar2(20));

SQL>create table student(regno number(10) primary key, name varchar2(10),dob date,course_id number, foreign key (course_id) references courses(course_id));

b) With User defined name

SQL>create table courses (course_id number constraint pk_course_id primary key,course_name varchar2(20));

SQL>create table student (regno number(10) constraint pk_regno primary key, name varchar2(10),dob date,course_id number, constraint fk_course_id foreign key(course_id) references courses(course_id));

3) Composite Foreign Key :-

a) With System defined name

SQL>create table courses (course_id number,course_name varchar2(20),primary key (course_id,course_name));

SQL>create table student(regno number(10) primary key, name varchar2(10),dob date,course_id number, foreign key (course_id) references courses(course_id));

b) With User defined name

SQL>create table courses (course_id number constraint pk_course_id primary key,course_name varchar2(20));

SQL>create table courses (course_id number primary key,course_name varchar2(20));

SQL>create table student(regno number(10) primary key, name varchar2(10),dob date,course_id number,foreign key (course_id) references courses(course_id) on delete set null);

b) With User defined name

SQL>create table courses (course_id number constraint pk_course_id primary key,course_name varchar2(20));

SQL>create table courses (course_id number primary key,course_name varchar2(20));

SQL>create table student(regno number(10) primary key, name varchar2(10),dob date,course_id number, foreign key (course_id) references courses(course_id) on delete cascade);

b) With User defined name

SQL>create table courses (course_id number constraint pk_course_id primary key,course_name varchar2(20));

SQL>create table student (regno number(10) constraint pk_regno primary key, name varchar2(10),dob date,course_id number,constraint fk_course_id foreign key(course_id) references courses(course_id) on delete cascade);

--------------------------HAPPY LEARNING -----------------------------

**THANK YOU**