General Computing and Siebel CRM Technical Quiz

The question asks which statement is false. Option C claims MVG 'requires dedicated space on a view' - this is FALSE because MVGs display inline within the parent applet using a multi-value field and query/mvlc buttons, taking minimal space. Options A and B are true: MVGs show one child record initially (the primary if set, or first child) and the MVG applet opens on demand to show all children. Option D 'None' would mean no false statements exist, which contradicts C being the answer.

The statement 'Join must exist between parent and child business components in the MVG' is FALSE. MVGs use the implicit relationship defined in the MVG definition itself (which specifies the child BC and the link), not an explicit join object. The MVG mechanism handles the relationship through its own configuration - the link and relationship are defined at the MVG level, not through a separate Join object. Therefore, the answer 'False' (option B) is correct.

The question asks which statement is false. Option B states 'A primary FK creates a one-to-many relationship between the parent and the child' - this is FALSE. A Primary Foreign Key points from the CHILD side to the PARENT (one child has one primary parent), creating a many-to-one relationship from child perspective, not one-to-many. The one-to-many exists from parent to child, but the FK itself doesn't create it - the relationship exists first, then FK identifies which child is primary. Options A and C correctly describe primary FKs.

With 4 MVGs without primaries and 10 parent records displayed: 1 initial query fetches the 10 parent records. Each MVG field requires one query per parent record to fetch its child records (no primary means no optimized join). Total = 1 + (10 parents × 4 MVGs) = 1 + 40 = 41 queries. If MVGs had primaries, all 4 primary children would join in the initial query, reducing to just 1 query total.

Picklists allow users to select a single value from a predefined list to populate a single-value field. When a user clicks on a picklist-enabled field, Siebel displays a list of valid values, and selecting one populates the field. Drilldown navigates to detail views, Toggles switch between applets, and MVGs handle multiple child records - none of these select single values from lists.

The S_LST_OF_VAL table (Siebel List of Values) stores all static picklist values in Siebel. Each row represents one picklist value with columns like VAL (display value), TYPE (picklist name), LANG (language), and ACTIVE/SORT order. S_CONTACT stores contact records, S_USERS stores user accounts - neither holds picklist data. Option D 'None' would imply no dedicated table exists, which is false.

If S_LST_OF_VAL table has no values for a picklist's TYPE, the picklist appears empty to users. Siebel doesn't show an error or default values - it simply renders the picklist control with no options to select. This is normal behavior; the picklist framework exists but has no data to display. Option A correctly describes this, while B (defaults) and C (error) are incorrect.

In Sort Specification property, field names are listed as comma-separated values (e.g., 'Name, City, State'). This is the correct syntax. Option B is false because descending requires (DESCENDING) not just (DESC) - Siebel requires the full word. Option C is false because field names are NOT in square brackets - that syntax is for business component fields in other contexts. Option D 'None' is false because A is true.

The Force Case property on Business Component Fields accepts three valid values: UPPER (converts to uppercase), LOWER (converts to lowercase), and FIRSTUPPER (capitalizes first letter, rest lowercase). These are the only valid options for forcing case on field values. Options A, B, and C list individual valid values, and option E correctly combines all three. 'None' is not a valid value for this property.

Thread bar in Siebel applications displays the navigation path and updates dynamically when users navigate between different business objects or views, showing the current context in the application hierarchy. This breadcrumb navigation helps users understand where they are in the application.

PostDefault property in Siebel Business Components automatically assigns a value to a field only if the user hasn't entered one, and this assignment happens during the PreWrite event before the record is inserted into the database. PreDefault assigns values before UI rendering, while PostDefault works after user interaction but before database commit.

Dynamic Drilldown in Siebel enables hyperlink navigation to multiple views from the same hyperlink field based on the value of a field in the Applet's current record. Unlike static drilldowns that always go to the same view, dynamic drilldowns can route to different destinations depending on runtime conditions.

Configuring Dynamic Drilldown in Siebel requires both steps: creating drilldown objects for each target view, and creating dynamic drilldown destination definitions for each condition that determines which view to navigate to. Both components are necessary for the feature to work.

A Drilldown Object definition in Siebel can have multiple Dynamic Drilldown Destination (DDD) objects associated with it, each representing a different navigation target based on different conditions. This allows the same drilldown to route to various views depending on runtime criteria.

The Owner Delete property in Siebel Business Components, when set to TRUE, restricts record deletion to only the owner (creator) of that record. This security feature ensures that users cannot delete records owned by other users, protecting data integrity and ownership rights.

The Colossus computer was a British code-breaking machine used during World War II to decrypt German Lorenz cipher messages. It was the world's first programmable electronic digital computer and played a crucial role in Allied intelligence efforts.

In classic versions of Excel (Excel 2003 and earlier), there were exactly 256 columns labeled A through IV. Modern Excel versions have significantly more columns (16,384), but the question refers to the traditional column count.

In binary systems, 1 MB equals 1024 KB, following the pattern where each unit is 1024 times the previous unit. This is the standard conversion in computing, where KB = 1024 bytes, MB = 1024 KB, and so on. Option B incorrectly states 1024 bytes, which is actually 1 KB.

Lindows was a Linux distribution created in 2001 that aimed to combine Linux with Windows-like interface and application compatibility. It was designed as a Windows clone before being renamed Linspire due to legal issues with Microsoft.