Explanation/Reference:
It is a best practice to create aliases for all tables. Aliases are created in the Physical Layer of the repository. Some of the benefits of using aliases are given below:
(A) * An alias is used to avoid circular joins and to configure self joins.
* You can create a join relationship which is different than the actual foreign key relationship in the database. This helps in defining relationships to meet business model criteria.
* Aliases can function in numerous ways to define business model e.g. a table can act both as a dimension and a fact using aliases.
(B) * You can rename aliases to make physical and business model easier to understand.

Explanation/Reference:
You can define calculations in either of the following ways:
- Before the aggregation, in the logical table source. For example:
sum(col_A *( col_B))
- After the aggregation, in a logical column derived from two other logical columns. For example:
sum(col A) * sum(col B)
Incorrect answers:
A: Defining the Logical Key of a Fact Table
Foreign Key Logical Joins
If foreign key logical joins are used, the primary key of a logical fact table should then be comprised of the foreign keys. If the physical table does not have a primary key, the logical key for a fact table needs to be made up of the key columns that join to the attribute tables as follows:
1.Look at the foreign keys for the fact table and find references for all of the dimension tables that join to this fact table.
2.Create the logical key of the fact table as a combination of those foreign keys.
B: You can find this functionality in the general property of a subject area in the repository.
The goal of this definition is to guide the BI Server to make the best choice between two possibles query path.
Multiple path occurs when, if you choose two attributes of dimensions that links together to two fact tables.
For instance, this case can occurs when you create for instance a constraint dashboard prompt.
To guide OBIEE in the best choice, you need to select a fact attribute (measure) as an implicit fact column.
C: What are the benefits of using Aliases in OBIEE?
It is a best practice to create aliases for all tables. Aliases are created in the Physical Layer of the repository. Some of the benefits of using aliases are given below:
You can create a join relationship which is different than the actual foreign key relationship in the database. This helps in defining relationships to meet business model criteria.
An alias is used to avoid circular joins and to configure self joins. (for more details on Fan Trap and Circular Joins check this blog.)
Aliases can function in numerous ways to define business model e.g. a table can act both as a dimension and a fact using aliases.
You can rename aliases to make physical and business model easier to understand.

B: BI Server Security Manager accessed through the BI Server Administration Tool.
*Set permission to business model, tables, columns and subject areas
*Specify filters to limit data accessible by users
*Set authentication options
C: Enable the SSO through the FMW Control.

D:You have three methods to start the managed server:
*with the console (recommended)
*with FMW control
*with the command line.

Explanation/Reference:
Note: This source should be combined with other sources at this level (check box) Description: Check this box when data sources at the same level of aggregation do not contain overlapping information. In this situation, all sources must be combined to get a complete picture of information at this level of aggregation.
Note 2: To use a source correctly, the Analytics Server has to know what each source contains in terms of the business model. Therefore, you need to define aggregation content for each logical table source of a fact table.
The aggregation content rule defines at what level of granularity the data is stored in this fact table.
Use the Content tab of the Logical Table Source dialog box to define any aggregate table content definitions, fragmented table definitions for the source, and Where clauses (if you want to limit the number of rows returned).
Reference: Siebel Business Analytics Server Administration Guide > Creating and Administering the Business Model and Mapping Layer in a Repository > Creating and Administering Logical Table Sources (Mappings) > Defining Content of Logical Table Sources

Explanation
See BI Home Page screenshot below:

Note: The BI Home page contains the BI content catalog. Fusion Apps will use OBIEE web catalog to store all shipped reporting and analytics content.
From the BI home page users can browse and view the entire BI content. The BI catalog folder structure will match the Fusion Apps main menu structure. Folder structure would be content driven not technology driven which would enable ease of navigation for fusion Apps users.
Following content will be available under the BI catalog structure:
BI Publisher Reports (regardless of data source)
OTBI reports & dashboards
OBIA dashboards & scorecards
Financial Reporting
Also, users can do some additional actions from the BI Home page like: Access personal and shared reports, View/ edit BI publisher report schedules, Launch BI tools for advanced actions and create new reports with report wizard.
New reports created can be saved in BI catalog and added as embedded content within Fusion applications screens or links added to reporting pane. This enables users to extend the prebuilt embedded analytics within Fusion Applications.