Explanation/Reference:
Level-based Hierarchy
Level-based hierarchy is the first type of hierarchy in OBIEE.
Consists of an ordered set of two or more levels. For example, a Time hierarchy might have three levels for Year, Quarter, and Month. Level-based hierarchies can also contain parent-child relationships.
Dimension hierarchy levels allow :
* to perform aggregate navigation,
* to configure level-based measure calculations,
* users from Dashboard and Answers to drill down from one parent to a child level.
Special type of level-based dimension are supported:
* Unbalanced (or ragged) and Skip-level hierarchy
* time dimension to provides special functionality for modeling time series data.

Explanation/Reference:
The "Edit Column Formula" dialog box has a second,
very tiny tab called, "Bins." You can use this tab to have OBIEE
build a CASE statement for you in a formula (you can also create
a CASE statement yourself by using one of the functions that
appears under "Expressions" if you want). A CASE statement is a
lot like an IF-THEN-ELSE statement, except that it's a little easier
to read when you have multiple options. Basically, it puts values
in different buckets that you define.
Note:
Figure:

Incorrect answers:
C: The "Conditional Format" tab lets you set formatting when specific conditions are met.

Explanation
A: OBIEE 11g is centred on WebLogic Server as the underlying application server architecture.
B: If you want to scale out this infrastructure, you would typically run the OBIEE 11g installer on a second server, and instead of choosing to do a new install, you'd choose to instead scale out the existing BI domain.

Node2-2
C: OBIEE Clustering - Approach of Oracle BI Server Load balancing/Failover

Explanation
A:
* Combining Relational and OLAP Data Sources: Oracle's Common Enterprise Information Model allows users to combine data from a relational system and an OLAP source in a single calculation. For example, a user can compare sales forecasts from an Oracle CRM System with budget data from an Oracle Essbase planning application. To clients of the Common Enterprise Information Model, the forecast and budget data appear to be from the same logical source.
* The Essbase server provides advanced multi-user read and write capabilities, including data update and multi-user recalculation. Business users with front-end tools can write data back to a server and recalculate the data on a server using calculation scripts-key functionality to support sophisticated modeling and planning applications.
* Using aggregate storage, Essbase serves a wide range of analytic needs-financial analysis, planning, budgeting, sales analysis, marketing analysis, supply-chain analysis, and profitability analytics-all from a single analytic infrastructure.
B:
Note: The Analytic Data Model (ADM) is an API used to access OLAP data and metadata. ADM is similar to JDBC, providing a single common API that hides most differences between OLAP data sources.
Note 2: Data model for business intelligence
The most important component of business intelligence is the concept of 'data model'. data model determinde what kind of analysis that end user could do with the data. It is also an independant concept that could span across different vendor 's product.
Unlike data model of the transaction system, the typical analytic data model is often denormalized and store extra data for analytic query and better query performance while transaction data model use is often normalized and optimized for a few data read and write, which is implemented by jointing many tables.
The most common used analytic data model in business intelligence is call the 'Star schema' data model.
With the Oracle business intelligence system, We could define star schema and dimension data model in the
'logical layer' in the admin tools. The data model in OBIEE could span different data source in physical layer, which means OBIEE have the capability of building one logical data model which is actually connect to different database in the backend