Oracle 1Z0-533 Online Practice Questions and Exam Preparation

Oracle 1Z0-533 Online Questions & Answers

• Question 31:

  Planning administrators can access which four administration tools via the EPM Workspace?

  A. Planning
  B. EPMA
  C. ODI
  D. LCM
  E. Calculation Manager
  F. EAS
  G. FR Studio
  A. Planning
  B. EPMA
  D. LCM
  E. Calculation Manager

  ---

  A: Planning is available within Oracle Enterprise Performance Management Workspace

  B: Oracle Enterprise Performance Management Architect (EPMA) is accessible from the EPM Workspace.

  D: The Shared Services Web application and the LCM utility communicate over TCP/IP to the EPM Workspace Core Service.

  Note: One of the smartest tools Oracle/Hyperion ever integrated into its product suite was the migration utility. Overtime this has evolved to the LifeCycle Managment utility or LCM for short. Actually Oracle/Hyperion has taken it even one step

  further by calling its fully integrated migration tool the BI+ Artifact LifeCycle Management utility even though they have retained the same acronym, LCM.

  E: Calculation Manager was introduced in EPM workspace common Foundation Services in release 11.

  Single interface for both Hyperion

  Planning and Financial Management

  

  Graphical flow provides better understanding of calculation process

  

  Re-usable rules to share among applications

• Question 32:

  Identify the two true statements about a sparse Entity dimension In Hyperion Planning.

  A. You cannot build alternate rollups or assign custom attributes.
  B. Base currencies are assigned to entity members.
  C. Exchange rates are assigned to entity members.
  D. Entity along with Scenario and Period make up a planning unit.
  E. Entity along with Scenario and Version make up a planning unit.
  B. Base currencies are assigned to entity members.
  E. Entity along with Scenario and Version make up a planning unit.

  ---

  E: The Scenario and Version dimensions represent the broadest categories of data in your application. Scenario describes the type of data that a plan includes, such as budget, actual, or forecast, as well as the time span that the plan covers.

  Version allows for flexibility and iterative planning cycles. For example, your application could have two versions, Working and Final, for each scenario. You can also use versions to model possible outcomes based on different assumptions

  about interest rates, growth rates, and so on. For example, your application an have a Best Case and Worst Case version for each scenario.

  Note:

  Essbase maximizes performance by dividing the Essbase - Standard dimensions of an application into two types:

  dense dimensions

  sparse dimensions.

  Sparse and dense are a property of the values of an attribute.

  Sparse

  Data is normally stored in sparse form. If no value exists for a given combination of dimension values, no row exists in the fact table. For example, if not every product is sold in every market. In this case, Market and Product are sparse

  dimensions.

  It's why in the reporting tool Obiee for instance, by default, data are considered sparse.

  Dense

  Most multidimensional databases may also contain dense dimensions. A fact table is considered to have dense data if it has (of a high probability to have) one row for every combination of its associated dimension levels.

• Question 33:

  Assuming EAS Business rules, a user cannot see a business rule on a data Form. What are three possible causes?

  A. The business rule has not been assigned to the data form.
  B. The business rule was created for another plan type.
  C. The valid locations have not been defined for the business rule.
  D. The valid locations have not been defined for the data form.
  E. The Validate and Launch privileges have not been granted for the business rule.
  F. The Validate and Launch privileges have not been granted for the data form.
  A. The business rule has not been assigned to the data form.
  C. The valid locations have not been defined for the business rule.
  E. The Validate and Launch privileges have not been granted for the business rule.

  ---

  A: Business Rules can be assigned to data forms.

  C: You can manage database locations, and the access privileges of repository objects that are assigned to them, using the Location Editor. You can use the Location Editor to create, edit, and copy database locations, assign new access privileges to locations, copy access privileges from one location to another, and copy business rules from one location to another.

  E: When you validate a business rule, Business Rules determines whether the member or members you select exist in the database and whether the syntax of the business rule is correct. You need to have access privileges to all rules in the sequence before you can launch it.

  Reference: Hyperion Business Rules, Administrative Guide, Release 9.3.1

• Question 34:

  Assuming the following dimensions and members:

  Scenario - Actual, Budget and Year - 2010, 2011, you need to create a data form with two columns. One column should list Actual for 2010 and the second column should list Budget 2011. You do not want to show data for Actual 2011 even though the first three months of the year have been loaded from the GL.

  What is the best way to only show the 2 columns in the data form?

  A. You cannot build a data form with these two columns, hour columns will display: Actual >2010, Actual >2011, Budget->2010 and Budget >2011
  B. Use Segments on the data form to create the asymmetric columns.
  C. Use User Variables on the data form to create the asymmetric columns.
  D. Use a composite data form to meet this requirement.
  E. Use data suppression on the data form.
  B. Use Segments on the data form to create the asymmetric columns.

  ---

  Asymmetric rows and columns are ones in which different sets of members are selected across the same dimension.

• Question 35:

  Fragmentation in an underlying Planning Essbase database that is caused by what two actions?

  A. Delete member from a sparse dimension.
  B. Delete member from a dense dimension.
  C. Renaming a member.
  D. Renaming an alias.
  E. Submitting data / deleting data frequently.
  B. Delete member from a dense dimension.
  E. Submitting data / deleting data frequently.

  ---

  Fragmentation is unused disk space.

  EssBase Database fragmentation is likely to occur with the following:

  Read/write databases that users are constantly updating with data (E).

  Databases that execute calculations around the clock

  Databases that frequently update and recalculate dense members (B)

  Data loads that are poorly designed

  Databases that contain a significant number of Dynamic Calc and Store members

  Databases that use an isolation level of uncommitted access with commit block set to zero

• Question 36:

  The Hyperion Planning administrator needs to run several calculations in a specific order against two different databases within the application. Identify the two options that are not valid.

  A. Esscmd
  B. Calc Script
  C. Business Rule Sequence
  D. MaxL
  E. Business Rule Macro
  A. Esscmd
  D. MaxL

  ---

  ESSCMD is the original command line interface for administration commands.

  MaxL, a "multi-dimensional database access language" which provides both a superset of ESSCMD commands, but with a syntax more akin to SQL, as well as support for MDX queries.

• Question 37:

  You are designing a new Planning application.

  Which two requirements dictate multiple plan types in a single Planning application?

  A. Multiple currencies are required.
  B. Currency rates must be kept in a separate database.
  C. Sales are planned by product and channel, and salary expenses are planned by position.
  D. Security is applied to the Entity dimension but can differ for users for accounts "sales" and "expenses".
  E. You have decided to implement the Capital Expense planning module in addition to PSL budgeting.
  F. Data cannot be shared across the Organization dimension.
  C. Sales are planned by product and channel, and salary expenses are planned by position.
  E. You have decided to implement the Capital Expense planning module in addition to PSL budgeting.

  ---

  C: When you define an entity member, you assign a plan type for which it is valid. If you do not assign a plan type to a member, that member's children do not have access to that plan type. If you move a member, and the new parent of that member is valid for different plan types, then the member remains valid only for the plan types it has in common with the new parent.

  Your organization may require that different entity members prepare different plans. For example, in your organization all entity members may submit expense plans, but entity members that are cost centers do not submit revenue plans.

  When you define entity members you specify the plan types for which they are valid. Because data forms are associated with plan

  types, this allows you to control which entity members can enter data for each plan type.

  E: You would need two plan type. To add a Capital Expense plan type to an existing application see Note below.

  Note: To add the Capital Asset Planning plan type to a Planning application:

  1 In Performance Management Architect, select Navigate, then Administer, then Application Library.

  2 In the Application Library, right-click the application to which you want to add the Capital Asset Planning plan type, select Initialize, then select Capital Asset or Workforce and Capital Asset if the application will use both plan types.

  3 To confirm the initialization, click Yes.

• Question 38:

  Identify the three true statements about attribute dimensions.

  A. Planning supports hierarchies and aliases for attribute dimensions.
  B. Planning supports all attribute types (for example. Boolean, Date, Text).
  C. Planning supports varying attributes (where an attribute can vary over one or more other dimensions).
  D. Attribute dimensions can be assigned to dense dimensions.
  E. Attribute dimensions may only be assigned to one base dimension.
  A. Planning supports hierarchies and aliases for attribute dimensions.
  B. Planning supports all attribute types (for example. Boolean, Date, Text).
  E. Attribute dimensions may only be assigned to one base dimension.

  ---

  A:

  To create and change attributes, attribute values, and aliases:

  1 Select Administration, then Dimensions.

  2 Select a sparse dimension for which to define an attribute, attribute value, or alias.

  Only sparse dimensions can contain attributes.

  3 Select the top level in the dimension hierarchy, and click Edit.

  4 In the Dimension Properties dialog box, click Custom Attributes.

  5 Select options.

  5.1 To create attributes, click Create. Type an attribute name, and select a data type: Text, Date, Boolean, or Numeric.

  5.2 To modify attributes, click Modify, and update the attribute name.

  5.3 To set aliases for attributes, select an attribute and an attribute value, click Alias. Select an

  alias table, type an alias name, and click Close.

  6 Click Close.

  When you click Close, the hierarchy is validated and an error displays if issues are detected.

  7 Update and validate business rules and reports.

  B: Attributes can have data types of text, date, Boolean, and numeric.

  E: An attribute dimension is a special type of dimension that is associated with a standard dimension. A standard dimension is any dimension that is not an attribute dimension. When an

  attribute dimension is associated with a standard dimension, the standard dimension is the base dimension for that attribute dimension. I

• Question 39:

  You need to build the Entity into your Classic Planning application. You can dynamically build the Entity dimension in the Planning application via: (Select all that apply)

  A. Essbase load rules
  B. Oracle Data Integrator (ODI)
  C. Data Integration Management (DIM)
  D. Data Relationship Management (DRM)
  E. Outline Load Utility
  F. EPMA
  A. Essbase load rules
  B. Oracle Data Integrator (ODI)
  C. Data Integration Management (DIM)
  E. Outline Load Utility
  F. EPMA

  ---

  A: Essbase data load rules: A set of criteria that determines how to load data from a text-based file, a spreadsheet, or a relational data set into a database.

  You can use either the Data Load Rules and the Essbase Administration Services for Essbase 7/Analytic Administration Services for Analytic Services 9.2 or Hyperion Application Link with the Hyperion Essbase Adapter to load data into a

  Planning application.

  B: Oracle Data Integrator (ODI) is a comprehensive data integration platform that handles any data integration requirements--high-volume, high-performance batches, event-driven, trickle-feed integration processes, and SOA-enabled data

  services.

  C: One of the methods of loading Essbase cubes is by using the Hyperion Data Integration Management and its corresponding Essbase Adapter.

  Data Integration Management is integrated with Informatica PowerCenter. It provides a way of uniting disparate sources of data across an enterprise. For example, it can integrate data stored in multiple warehouses and data marts, relational

  database management systems (RDBMS), and on-line analytical processing (OLAP) stores.

  E: The Outline Load Utility that comes with Oracle EPM 11 is a utility for loading the metadata as well as data into your Planning applications. Using the utility we can load metadata for the default dimensions like Account, Period, Year, Scenario, Version, Currency, Entity as well as user-defined dimensions, attributes and UDAs.

  F: Enterprise Performance Management Architect or EPMA provides a uniform platform for metadata management across most of the Hyperion components. It enables administrators to manage, create, and deploy Hyperion applications within one interface. With EPMA you can configure dimensions, such as the Entity, and define properties from predefined, sample libraries.

• Question 40:

  When opening a data form, the user experiences slow performance.

  What three steps could you do to improve the time it takes to open the data form?

  A. Reduce the number of rows and columns displayed in the data form.
  B. Upgrade the client machine's operating system processing speed and RAM.
  C. In the data form definition, remove the option to display alias.
  D. Reduce the number of page dimensions used on the Web form
  E. Tune the index and data caches in Essbase.
  A. Reduce the number of rows and columns displayed in the data form.
  B. Upgrade the client machine's operating system processing speed and RAM.
  E. Tune the index and data caches in Essbase.

  ---

  A: Reducing the amount of rows and columns that need to be accessed would increase performance.

  B: The client machine could also be a bottleneck.

  E: Indexing and caching would help when loading data into a form.