Oracle 1Z0-531 Online Practice Questions and Exam Preparation

Oracle 1Z0-531 Online Questions & Answers

• Question 41:

  What are five reasons to use Attributes over a Shared Members dimension?

  A. To create crosstab reports
  B. To describe a dense dimension
  C. To describe a sparse dimension
  D. To perform comparisons based on certain type of data
  E. To perform calculations based on characteristics
  F. To add dimensionality to the database without increasing database size
  A. To create crosstab reports
  C. To describe a sparse dimension
  D. To perform comparisons based on certain type of data
  E. To perform calculations based on characteristics
  F. To add dimensionality to the database without increasing database size

  ---

  C: Attribute dimensions can only be applied to sparse dimensions.

  F: Varying attributes let you vary information in one dimension by up to four additional dimensions. A, D, E:

  

  Incorrect answer:

  B: Attribute dimensions can only be applied to sparse dimensions.

• Question 42:

  The data block density for a particular BSO database is between 10% and 90%, and data values within the block do not consecutively repeat. Which type of compression would be most appropriate to use?

  A. Bitmap
  B. RLE
  C. ZLIB
  D. No compression required
  A. Bitmap

  ---

  Bitmap is good for non-repeating data. It will use Bitmap or IVP (Index Value Pair).

  Note: Bitmap compression, the default. Essbase stores only non-missing values anduses a bitmapping scheme. A bitmap uses one bit for each cell in the data block, whether the cell value is missing or non- missing. When a data block is not compressed, Essbase uses 8 bytes to store every non-missing cell. In most cases, bitmap compression conserves disk space more efficiently. However, much depends on the configuration of the data.

• Question 43:

  You notice that your reports are running slower than before and realized that nothing in terms of data volume or dimension members has changed. You also checked the log file and found that no one ran any calculation.

  Which two would you look for to diagnose the cause of this slower response time?

  A. Run a MaxL comment to see if the database is fragmented
  B. Check when was the last time the application was stopped
  C. Check the data cache setting
  D. Check the commit-level setting
  A. Run a MaxL comment to see if the database is fragmented
  C. Check the data cache setting

  ---

  A: Database fragmentation would slow down the database performance. You can use MaxL commands to check the fragmentation status.

  C: The data cache could affect the running time of the reports. Checking this cache would be a good idea.

  Incorrect answers

  Stop time of the application is not of interest here.

  The commit-level setting would affect real-time updates, not producing reports.

• Question 44:

  Given the following, what is the declared block size?

  

  A. 1920 bytes
  B. 480 bytes
  C. 3840 bytes
  D. 12450 bytes
  C. 3840 bytes

  ---

  We need to multiple the stored (not the total) members of the dense dimensions (here Year: 12, Measures:20, and Scenario:2) with 8 to calculate the block size.

  Block size: 12x20x2x8 = 3840

  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 45:

  What are the three rules for Shared Members in ASO?

  A. A Multiple Hierarchy Enabled dimension can have shared members.
  B. When a hierarchy is tagged Multiple Hierarchies Enabled, it must be store.
  C. The alternate hierarchy has shared members that refer to nonshared members of previous hierarchies in the outline.
  D. The shared members roll up according to a different hierarchy from the nonshared members to which they refer.
  A. A Multiple Hierarchy Enabled dimension can have shared members.
  C. The alternate hierarchy has shared members that refer to nonshared members of previous hierarchies in the outline.
  D. The shared members roll up according to a different hierarchy from the nonshared members to which they refer.

  ---

  Shared member hierarchy is also an alternate hierarchy. All shared member refers to stored members of outline (C). In aggregate storage application only multiple hierarchies can have shared members. (A)

  Stored hierarchy has only addition as consolidation operator. You can use the stored hierarchy type where aggregation is the only mathematical requirement. If you have some shared member in hierarchy then use multiple hierarchy.

• Question 46:

  You need to tune a block storage option database for calculations on a 32bit Essbase server. Identify the two starting point tuning steps that you might take (assuming no direct I/O).

  A. Set Index Cache the size of the index file
  B. Set Data Cache to the size of 0.125 * pag file
  C. Set Data File Cache to the size of .025 * data file
  D. Reset sparse and dense dimensions to achieve a block size greater than 100KB
  A. Set Index Cache the size of the index file
  B. Set Data Cache to the size of 0.125 * pag file

  ---

  Here are the best practices to tune a BSO database:

  -

  ACR (Average clustering Rate) should be as close to 1 as possible, launch a dense restructure to de- fragment the database

  -

  Block Size should be between 10 and 100KB (can be more on 64 bit systems)

  -Data cache should be 12.5% of the pag files (B)

  -Index cache should be the same size as the ind files (A)

  -1 Database per Application

• Question 47:

  Market size is an attribute dimension with the following members: Large, Medium, and Small.

  Which of the following options below represent valid syntax statements in a calc script?

  A. FIX (@ATTRIBUTE(Large))
  B. Calc Dim (Accounts, Markets, "Market Size");
  C. Calc Dim (Accounts, Markets, Market Size);
  D. FIX(Large)
  A. FIX (@ATTRIBUTE(Large))
  B. Calc Dim (Accounts, Markets, "Market Size");

  ---

  For example, using Sample Basic, assume this statement is in a calculation script: FIX (@children(january))CALC DIM (Accounts, Product, Market)ENDFIX

  

• Question 48:

  Which two statements are true (assuming data is loaded to a BSO database and to the members noted below)?

  A. If you delete a sparse shared member, the outline file shrinks.
  B. If you delete a sparse shared member, the page file shrinks.
  C. If you delete a sparse stored member, the index file shrinks.
  D. If you delete a sparse stored member, the block density shrinks.
  E. If you delete a dense shared member, the block size shrinks.
  F. If you delete a dense stored member, the number of blocks shrinks
  A. If you delete a sparse shared member, the outline file shrinks.
  C. If you delete a sparse stored member, the index file shrinks.

  ---

  C: If a member of a sparse dimension is moved, deleted, or added, Essbase restructures the index and creates new index files. Restructuring the index is relatively fast; the time required depends on the index size.

  Sparse restructures are typically fast, but depend on the size of the index file(s). Sparse restructures are faster than dense restructures.

• Question 49:

  With an average block density greater than 90%.

  A. You should reconsider the dense and sparse settings
  B. You should consider no compression
  C. You should set Commit blocks to
  D. You should reconsider the outline order of dimensions
  B. You should consider no compression

  ---

  Hyperion recommends that you should turn compression off if you have a block density > 90% (rarely happens) and you should change to RLE compression when the block density is < 3% (or if you have all the same values in the database lots of zeros).

  Note: You may want to disable data compression if blocks have very high density (90% or greater) and have few consecutive, repeating data values. Under these conditions, enabling compression consumes resources unnecessarily. Don't use compression if disc space/memory is not an issue compared to your application. It can become a drain on the processor.

• Question 50:

  Identify the true statement about the data cache.

  A. Data cache contains compressed data blocks
  B. Data cache contains uncompressed data blocks
  C. Data cache contains compressed index entries
  D. Data cache contains uncompressed index entries
  B. Data cache contains uncompressed data blocks

  ---

  The Data Cache is a buffer in memory that holds uncompressed data blocks. Essbase allocates memory to the data cache during data load, calculation, and retrieval operations, as needed.

  Note: there are four other caches as well, including the index cache.