Oracle 1Z0-531 Online Practice Questions and Exam Preparation

Oracle 1Z0-531 Online Questions & Answers

• Question 11:

  Which four are the directories used for aggregate storage databases?

  A. Default
  B. Log
  C. Metadata
  D. Data
  E. Bin
  F. Temp
  A. Default
  B. Log
  C. Metadata
  F. Temp

  ---

  ASO (Aggregate storage option):

  *

  Directory structure differs in both content and purpose from BSO

  *

  Tablespaces are utilized to store data and metadata ** Default stores numeric data (.dat file) ** Log records database activity ** Metadata stores metadata information about the objects in the database ** Temp temporary working space for the Essbase kernel

• Question 12:

  Which two options would provide a better design for the following accounts and metrics?

  

  A. If there are a small number of accounts that require FTE and Expense dollars, split Accounts and Metrics into 2 dimensions
  B. If there are a large number of accounts that require FTE and Expense dollars, split Accounts and Metrics into 2 dimensions
  C. If reporting dictates FTE and dollars in the columns and accounts in the rows, split Accounts and Metrics into 2 dimensions
  D. If block size is large, then keep Accounts and Metrics as one dimension with a dense dimension
  B. If there are a large number of accounts that require FTE and Expense dollars, split Accounts and Metrics into 2 dimensions
  D. If block size is large, then keep Accounts and Metrics as one dimension with a dense dimension

  ---

  Use Application Design Best Practices, Minimize the number of dimensions, Avoid Repetition in dimensions, Avoid inter dimensional irrelevance.

  http://www.scribd.com/doc/40391863/10-Hardcore-Essbase-Tuning-Tips-You-Ve-Never-Heard-Before

• Question 13:

  You receive the following error: Error: 1042017: Network error: The client or server timed out waiting to receive data. Which two settings in the Essbase.CFG are most commonly used to correct the issue?

  A. DISPLAYMESSAGELEVEL
  B. NETDELAY
  C. NETRETRYCOUNT
  D. MAX_REQUEST_GRID_SIZE
  E. MAX_RESPONSE_GRID_SIZE
  B. NETDELAY
  C. NETRETRYCOUNT

  ---

  1042017 Network error:

• Question 14:

  How are the ASO data files managed?

  A. Page files
  B. Index files
  C. Table spaces
  D. Bin files
  C. Table spaces

  ---

  With regard to ASO, table spaces are comparable to page and index files For ASO - the data is stored in table spaces in a .dat file in the \App\Appname\default folder. Again the format is some type of binary and you cannot open the file and

  do anything with the contents.

  Note:

  For BSO - the data is stored in the page files (*.pag) in the \App\Appname\DBname folder. The format is proprietary or some kind of binary, point being you can't open a .pag file and do anything with it.

• Question 15:

  You have the following customer dimensions;

  You need to create a % of total (by region) calculation by customer in you aggregate storage database for Net_Revenue. Select the best syntax for member formula so that the % Total calculation works at all levels of customer dimension.

  

  A. (Net_Revenue]) / (Parent. [Net_Revenue])
  B. (customer.CurrentMember, [Net_Revenue]) / (customer.CurrentMember.Parent, [Net_Revenue]);
  C. (customer.CurrentMember, [Net_Revenue]) / (customer.CurrentMember,Parent, [Net_Revenue])
  D. (customer.CurrentMember, [Net_Revenue]) / (customer. [Net_Revenue]);
  E. (customer.CurrentMember, [Net_Revenue]) / (customer. [Net_Revenue], Products, YearTotal);
  B. (customer.CurrentMember, [Net_Revenue]) / (customer.CurrentMember.Parent, [Net_Revenue]);

  ---

  We need to use the methods .CurrentMember and CurrentMember.Parent to get the correct % throughout all level of the customer dimension.

• Question 16:

  Identify the two true statements about compression for block storage databases.

  A. Index value pair compression works well for consecutive zero values or repeating values within a database.
  B. RLE compression works well for consecutive zero values or repeating values within a database.
  C. Bitmap compression is the default compression method.
  D. The Accounts dimension is tagged the compression dimension by default.
  E. Do not set compression for a dimension that has many members.
  B. RLE compression works well for consecutive zero values or repeating values within a database.
  C. Bitmap compression is the default compression method.

  ---

  B: RLE (Run Length Encoding) is a good compression type when your data has many zeros (block density low) or often repeats. RLE uses multiple compression compressions (one per block). RLE will use RLE, bitmap or IVP.

  C: By default, Bitmap compression is enabled. To switch to a different compression type, use alter database set compression.

• Question 17:

  Given the following, what is the block size In bytes?

  

  A. Block size = 40 * 17 * 2
  B. Block size = 40 *17 * 2 * 8
  C. Block size = 50 * 17 * 5
  D. Block size = 50* 17*5 * 8
  B. Block size = 40 *17 * 2 * 8

  ---

  We need to multiple the stored (not the total) members of the dense dimensions (here Measures: 40, Time:17, and Dense:2) with 8 to calculate the block size.

  Note: Data block size is determined by the amount of data in particular combination of dense dimensions. For ex: when you change the dense or sparse configuration of one or more dimensions in the database, the data block size changes. Data block size is 8n bytes, where n is the number of cells that exist (ie. Stored, not total) for that combination of dense dimensions.Note: Optimal range is 8 to 100 kb

• Question 18:

  Identify four disadvantages / considerations when using a transparent partition.

  A. Old data
  B. Slow retrievals
  C. Slow calculations if referencing dynamic calc members in the source
  D. Outline sync complexities
  E. Increased network load
  F. Downtime required to sync data
  B. Slow retrievals
  C. Slow calculations if referencing dynamic calc members in the source
  D. Outline sync complexities
  E. Increased network load

  ---

  Disadvantages of Transparent Partitions

  *

  Outline synchronization is required (D)

  If you make changes to one outline, the two outlines are no longer synchronized. Although Essbase makes whatever changes it can to replicated and transparent partitions when the outlines are not synchronized, Essbase may not be able to

  make the data in the data source available in the data target. Essbase tracks changes that you make to block storage outlines and provides tools to keep your block storage outlines synchronized.

  Note:

  Essbase does not enable automatic synchronization of aggregate storage outlines. You must manually make the same changes to the source and target outlines.

  *

  Transparent partitions increase network activity, because Essbase transfers the data at the data source across the network to the data target. Increased network activity results in slower retrieval times for users.

  (E)

  *

  Because more users are accessing the data source, retrieval time may be slower. (B)

  *

  If the data source fails, users at both the data source and the data target are affected. Therefore, the network and data source must be available whenever users at the data source or data target need them.

  *

  (C) When you perform a calculation on a transparent partition, Essbase performs the calculation using the current values of the local data and transparent dependents. Essbase does not recalculate the values of transparent dependents,

  because the outlines for the data source and the data target may be so different that such a calculation is inaccurate. To calculate all partitions, issue a CALC ALL command for each individual partition, and then perform a CALC ALL

  command at the top level using the new values for each partition.

  *

  Formulas assigned to members in the data source may produce calculated results that are inconsistent with formulas or consolidations defined in the data target, and vice versa.

  Note: Advantages of Transparent Partitions

  Transparent partitions can solve many database problems, but transparent partitions are not always the ideal partition type.

  *

  You need less disk space, because you are storing the data in one database.

  *

  The data accessed from the data target is always the latest version. (not A)

  *

  When the user updates the data at the data source, Essbase makes those changes at the data target.

  *

  Individual databases are smaller, so they can be calculated more quickly.

  *

  The distribution of the data is invisible to the end user and the end user's tools.

  *

  You can load the data from either the data source or data target.

  *

  You can enable write-back functionality for aggregate storage databases by creating a transparent partition between an aggregate storage database as the source and a block storage database as the target.

• Question 19:

  What is the default calculation order for ASO database?

  A. Accounts, Time, all remaining dimensions in ascending order of member count
  B. Time, Accounts, all remaining dimensions in ascending order of member count
  C. Accounts, Time, all remaining dimensions in descending order of member count
  D. Time, Accounts, all remaining dimensions in descending order of member count
  E. Dynamic hierarchies, Stored hierarchies
  F. Stored hierarchies, Dynamic hierarchies
  F. Stored hierarchies, Dynamic hierarchies

  ---

  Aggregate storage calculation order and block storage calculation order differ. For aggregate storage databases, Essbase calculates data in the following order:1.Aggregates members of stored hierarchies and attribute dimensions. The order in which members and dimensions are aggregated is optimized internally and changes according to the nature of the database outline and the existing aggregations...2.Calculates dynamic hierarchy dimension members and formulas...

  Note: BSO calculations order: First, Accounts Second, Time Third, remaining dense dimensions Fourth, remaining sparse dimensions Two Pass Calculation

• Question 20:

  You are building a sales analysis model. In this model there is no requirement for calculation. The user needs to aggregate data across all dimensions and wants to archive many years of data. Archived data will be analyzed once in while. What types of cube would you build using Essbase for this kind of requirement?

  A. Block Storage
  B. XOLAP
  C. Aggregate Storage
  D. Virtual Cube
  C. Aggregate Storage

  ---

  Consider using the aggregate storage storage model if the following is true for your database:

  *The database is sparse and has many dimensions, and/or the dimensions have many levels of members. *The database is used primarily for read-only purposes, with few or no data updates. (C) *The outline contains no formulas except in the dimension tagged as Accounts. *Calculation of the database is frequent, is based mainly on summation of the data, and does not rely on calculation scripts.