Siebel CRM Fundamentals

A loyal customer demonstrates commitment by preferring to purchase from your company even when competitors offer slightly lower prices. This price tolerance is a key indicator of true loyalty. Option A is incorrect because loyal customers will eventually leave after repeated poor service. Option B understates the impact - loyal customers actually tell MORE people. Option D is incorrect because loyalty percentages vary widely by industry and company.

The Database Extract (Dbxtract) server task creates the specialized Docking\User directory on the Siebel Server and populates it with the initial database extract files for a new Mobile Client. Synchronization Manager, Transaction Router, and GenDb serve other parts of the synchronization process.

A regional Sales Manager who needs to see opportunities created by their Sales representatives should use 'My Team's View', which shows data for the manager's entire team hierarchy. 'My View' only shows the user's own data, while 'All Organization' and 'All Across Organization' would show opportunities from everyone in the organization, not just the manager's team.

When a Siebel URL is requested, the Web Server (with the Siebel Web Server Extension) recognizes the URL and forwards it to the Siebel Web Engine (SWE) on the application server. The SWE then compiles the templates and data into HTML to send back to the user.

For the Siebel Mobile Client to function properly, 'Docking Transaction Logging' must be set to TRUE. This enables the mobile client to log transactions during synchronization docking operations. Setting Transaction Docking to FALSE would disable the docking process, and EXEC settings are unrelated to mobile client functionality.

The 'Generate New Database' component in Siebel Tools creates a template for the current database schema, not an actual new database. This template can be used for documentation or as a starting point for schema modifications. It does not create a new database instance (A), import repository data (C), or migrate repository objects (D).

CRM On Demand refers to customer relationship management delivered via web-based hosting, integrated systems, and real-time data access - all characteristics of on-demand/SaaS solutions. 'On premises' (A) is the traditional model opposite to on-demand. The three correct answers represent the key characteristics: Web Hosted (accessed via browser), Integrated (connects with other systems), and Real Time (immediate data updates).

A good CRM product facilitates better customer relations, improves employee satisfaction by streamlining tasks, lowers service times, and increases overall productivity. It does not directly focus on or guarantee changing employee attitudes, which is a behavioral/cultural concern.

To limit catalog visibility to only specific groups, you set the 'Private' flag for the catalog on the Catalog screen. This ensures only users in access groups associated with that catalog can view it. The 'Visible' flag controls general visibility, not group-specific access. Adjusting responsibilities or positions affects user permissions but doesn't directly limit catalog visibility to specific groups.

In Siebel applications, a logged-in user with multiple positions can dynamically change their active position by navigating to Tools -> User Preferences -> Change Position. Changing the profile flag requires administration, and position selection at login doesn't help change it after login.

In Siebel's access control model, users with the same Responsibility can see different data on the same view due to visibility controls like organization-based access, position-based filtering, and access groups. View access is consistent across organizations for a given responsibility (B is false), visibility is not determined by Responsibility + ID + Position combination (C is wrong), and users with different access levels CAN view the same data if they have appropriate permissions (D is false).

Views are registered in Siebel through the path Administration - Application -> Views, where you can create and manage view definitions. Responsibilities are managed separately under Administration - Application -> Responsibilities. The Utilities submenu contains additional tools but the primary view registration is under the main Views menu item.

In Siebel, when a user has multiple positions, they always log in using their PRIMARY position (Account Manager in this case). The primary position is set in the user's employee record and determines default access and visibility. Secondary positions like Sales Manager or Supervisor can be switched to during the session, but the login always uses the primary position.

Siebel CRM applications are built on a common architecture (A), are designed for minimal configuration (C), and provide consistent customer/company views (D). However, they do NOT share a database between applications - each Siebel application typically has its own database.

Adapting the client's business processes to match the default software package configurations minimizes custom programming work. This reduces overall implementation time and increases productivity by avoiding complex custom code maintenance.

In Siebel Tools, the Types tab in the Object Explorer displays the hierarchical parent-child relationships among all object definitions, allowing developers to see how objects are structured relative to one another. The Detail and Flat tabs display object instances or a flat list rather than schema hierarchies.

In Siebel database naming conventions, foreign key columns reference the primary key of another table and are suffixed with _ID (for example, ACCNT_ID). Suffixes like _FK, _PK, or _UK are not the standard naming convention for foreign key columns in Siebel.

A static picklist selects a value from a predefined list and copies it into a destination field. It can be configured as bounded (restricting entries to the list) or unbounded (allowing custom values). It does not update joined fields, which is typically a feature of dynamic picklists.

In Siebel Workflow, correctly connected connectors show red endpoints at both connection points. Additionally, running the 'validate' command checks the entire process configuration and reports any connectivity issues. White connector ends (option A) are incorrect, and right-clicking (option C) does not validate connections.