Automatic wild cards can be turned off by setting in the [SWE] section of CFG File
1. AutomaticTrailingWildcards = False
2. AutoTrailingWildcards = False
3. AutocTrailWildcards = False
4. All
Which one is the low performance operation?
1. Using the wildcard “*”
2. Using IS NOT NULL
3. Both
Running a query with no criteria is like
1. Refreshing the screen
2. is using the string within “”
3. is null
4. is not null
EXISTS () Query works in
1. MVG BC
2. All BC
3. Only for MVG Fields
4. Single Value Fields in MVG BC.
Queries are by default saved as
1. Private and available to the user who created
2. Public and available to all users
3. Both
Predefined queries are published by
1. Administrator
2. User who created it
3. Both
Record counts shows
1. Total number of records in the active list
2. Total number of Records that match the criteria of the query executed.
3. Both
The View used to associate file created in other application to the Siebel Record is
1. Administration View
2. Data Control View
3. Application Administration Screen
4. Attachment View
Siebel Web Server consists of
1. Virtual Directories
2. SWSE
3. Configuration file (eApps.cfg)
4. Only 2 and 3
5. 1, 2, and 3
Which one is the correct flow of accessing the siebel application?
1. Siebel Web Client ->Web Server -> Siebel Gateway
2. Siebel dedicated clien->Web Server ->Siebel Gateway
3. Both 1 and 2
4. Siebel Mobile Client-> Webserver->Enterprise Server-> Siebel Database Server
The function of the Virtual Directory in Web Server is
1. To receive inbound Siebel Web Client Request and forward to SWSE
2. To receive inbound Siebel Web Client Request and forward to Gateway
3. To maintain a directory on behalf of the client to co-ordinate with the server
4. All
SWSE
1. Receives and parses inbound HTTP requests from Siebel Web Clients
2. Creates and manages TCP connections to the Siebel Servers or Load Balancer
3. Routes requests to the appropriate Siebel Server Components
4. All
Sessions are maintained by
1. Web Server 2. Gateway Server 3. Application Object Manager 4. Enterprise Server
SWSE connections to the Application Object Manager is
1. Stateful to maintain the session
2. Stateless
3. Stateful to maintain the session at Application Object Manager
4. All
All Applications in the Siebel Enterprise is configured under
1. Single cfg FILE
2. Separate CFG file
3. Can be done in both ways depending upon the number of WebServers
4. All
Each Siebel Server requires
1. A client to be installed in the Server
2. Either a client or Tools to be installed in the server
3. Both Client and Tools
4. None
The Connectivity, login and other security information for web clients are checked at
1. Webserver
2. Siebel Server
3. Gateway Server
4. All
Component Definitions, assignment operations, operational parameters and connectivity information are stored in (5.10)
1. siebns.dat
2. Siebens.dat
3. siebns.dat stored in gateway server
4. siebns.dat stored in siebel server
The default load balancing feature is built in
1. Gateway server
2. Object Manager
3. SWSE
4. Siebns.dat
The third party load balancing software supported by siebel 7.7
1. SWSE
2. Resonate Central Dispatch
3. All
4. None
Siebel provides the load balancing between
1. WebServers
2. Web client and Webserver
3. Webserver and Siebel Servers
4. ALL
Intra Server Load balancing is
1. Provided by a third party to load balance between Siebel Servers
2. Provided by a third party to load balance between Siebel Gateway Servers
3. Provided by siebel for load balancing between siebel servers using SC Broker
4. Provided by siebel for load balancing between instances of the Application Object Manager in a single server.
Siebel Servers can access
1. Only Single Database server
2. Multiple Database Servers
3. Both
1. AutomaticTrailingWildcards = False
2. AutoTrailingWildcards = False
3. AutocTrailWildcards = False
4. All
Which one is the low performance operation?
1. Using the wildcard “*”
2. Using IS NOT NULL
3. Both
Running a query with no criteria is like
1. Refreshing the screen
2. is using the string within “”
3. is null
4. is not null
EXISTS () Query works in
1. MVG BC
2. All BC
3. Only for MVG Fields
4. Single Value Fields in MVG BC.
Queries are by default saved as
1. Private and available to the user who created
2. Public and available to all users
3. Both
Predefined queries are published by
1. Administrator
2. User who created it
3. Both
Record counts shows
1. Total number of records in the active list
2. Total number of Records that match the criteria of the query executed.
3. Both
The View used to associate file created in other application to the Siebel Record is
1. Administration View
2. Data Control View
3. Application Administration Screen
4. Attachment View
Siebel Web Server consists of
1. Virtual Directories
2. SWSE
3. Configuration file (eApps.cfg)
4. Only 2 and 3
5. 1, 2, and 3
Which one is the correct flow of accessing the siebel application?
1. Siebel Web Client ->Web Server -> Siebel Gateway
2. Siebel dedicated clien->Web Server ->Siebel Gateway
3. Both 1 and 2
4. Siebel Mobile Client-> Webserver->Enterprise Server-> Siebel Database Server
The function of the Virtual Directory in Web Server is
1. To receive inbound Siebel Web Client Request and forward to SWSE
2. To receive inbound Siebel Web Client Request and forward to Gateway
3. To maintain a directory on behalf of the client to co-ordinate with the server
4. All
SWSE
1. Receives and parses inbound HTTP requests from Siebel Web Clients
2. Creates and manages TCP connections to the Siebel Servers or Load Balancer
3. Routes requests to the appropriate Siebel Server Components
4. All
Sessions are maintained by
1. Web Server 2. Gateway Server 3. Application Object Manager 4. Enterprise Server
SWSE connections to the Application Object Manager is
1. Stateful to maintain the session
2. Stateless
3. Stateful to maintain the session at Application Object Manager
4. All
All Applications in the Siebel Enterprise is configured under
1. Single cfg FILE
2. Separate CFG file
3. Can be done in both ways depending upon the number of WebServers
4. All
Each Siebel Server requires
1. A client to be installed in the Server
2. Either a client or Tools to be installed in the server
3. Both Client and Tools
4. None
The Connectivity, login and other security information for web clients are checked at
1. Webserver
2. Siebel Server
3. Gateway Server
4. All
Component Definitions, assignment operations, operational parameters and connectivity information are stored in (5.10)
1. siebns.dat
2. Siebens.dat
3. siebns.dat stored in gateway server
4. siebns.dat stored in siebel server
The default load balancing feature is built in
1. Gateway server
2. Object Manager
3. SWSE
4. Siebns.dat
The third party load balancing software supported by siebel 7.7
1. SWSE
2. Resonate Central Dispatch
3. All
4. None
Siebel provides the load balancing between
1. WebServers
2. Web client and Webserver
3. Webserver and Siebel Servers
4. ALL
Intra Server Load balancing is
1. Provided by a third party to load balance between Siebel Servers
2. Provided by a third party to load balance between Siebel Gateway Servers
3. Provided by siebel for load balancing between siebel servers using SC Broker
4. Provided by siebel for load balancing between instances of the Application Object Manager in a single server.
Siebel Servers can access
1. Only Single Database server
2. Multiple Database Servers
3. Both
Related Posts
No comments :