Oracle 1Z0-533 Online Practice Questions and Exam Preparation

Oracle 1Z0-533 Online Questions & Answers

• Question 1:

  A Planning Unit has a status of First Pass; what two user types can input data?

  A. Anyone with write access to the planning unit
  B. Anyone with write access to the planning application
  C. Anyone with read or write access to the planning unit
  D. The owner of the planning unit
  E. The administrator
  A. Anyone with write access to the planning unit
  E. The administrator

  ---

  explanation:

  A: In all Planning Units states except the Not Started state, users with read access can view data, view the process state, view the history, and read and enter annotations.

  E: The Administrator have full access.

  Reference: Reference: Oracle Hyperion Planning, Fusion Edition, Release 11.1.1.3, Overview of the Review Process

• Question 2:

  Identify the two true statements about shared members.

  A. You can assign a custom attribute value to a shared member.
  B. You can define a member formula for a shared member.
  C. You can assign security rights to a shared member.
  D. There is no limit to the number of shared members that you can create for the base member.
  E. Shared members may be defined for Accounts and Entity dimensions only.
  C. You can assign security rights to a shared member.
  D. There is no limit to the number of shared members that you can create for the base member.

  ---

  explanation:

  C: Access cannot be assigned directly to a shared member. You assign access rights to shared members in one of two ways:

  *

  From the security assigned directly to the base member

  *

  From the security assigned at the parent or ancestor of the shared member

  D: You can create multiple shared members for the base member. A base member must exist before you can create a shared member, but there is no limit to the number of shared members you can create for the base member.

  E: Shared members are available for Entity, Account, and user-defined custom dimensions. " Shared members contain read-only values and are only available in the Entity dimension. "

• Question 3:

  You've created an EAS business rule and assigned it to the data form but an end user can't see it. What are two valid reasons?

  A. The user doesn't have the Launch Business Rules role in Shared Services.
  B. The user hasn't been assigned Validate or Launch Privileges in EAS.
  C. The location for the Business Rule hasn't been defined.
  D. The user hasn't been assigned access to the Business Rule in the Planning Web client.
  A. The user doesn't have the Launch Business Rules role in Shared Services.
  B. The user hasn't been assigned Validate or Launch Privileges in EAS.

  ---

  explanation:

  A: If the user does not have the launch the Business Rules role, it could prevent the user from seeing the rule.

  B: The Validate or launch Privilege enables a users or users you specify to validate and launch the business rule sequence Incorrect answer:

  C: The business rule has already been assigned to the Data Form.

• Question 4:

  What are valid data types for the Accounts dimension? Select all that apply.

  A. Currency
  B. Non-currency
  C. Percentage
  D. Saved Assumption
  E. Text
  F. Smart List
  G. Date
  A. Currency
  B. Non-currency
  C. Percentage
  E. Text
  F. Smart List
  G. Date

  ---

  explanation:

  Data types:

  How values are stored and displayed:

  *Currency (A)

  *Non-Currency (B)

  *Percentage (C)

  *Smart List (F)

  *Date (G)

  *Text (E)

  *Unspecified

  F

  or accounts, if Data Type is set to any value except Currency, you must set Exchange Rate Type to None.

  Note:

  The accounts dimension is a dimension type that makes accounting intelligence available. Only one dimension can be defined as Accounts.All members in the accounts dimension inherit the accounts property. You can create an outline that does not have an accounts dimension.

• Question 5:

  In the Workforce Planning module, an employee is terminated.

  What two activities do you perform in WFP, so that total salary numbers are correctly calculated?

  A. Run a business rule to change the employee's status.
  B. Change the employee's status on a data form using the Smart List drop down.
  C. Change the employee's status on a data form using the free form text measure.
  D. Change the employee status attribute association in the Employee dimension.
  E. Delete the employee from Workforce Planning.
  A. Run a business rule to change the employee's status.
  B. Change the employee's status on a data form using the Smart List drop down.

  ---

  explanation:

  You can change the status of the Employee through options from a Drop down/Smart List on a data form by running a Business Rule.

  

  Incorrect answer:

  Deleting the employee is a bad praxis. It would remove old salary entries.

  You do not access the attributes directly on the Employee dimension.

  Note: The Workforce Planning Module for Hyperion Planning provides a robust set of calculations and pre-defined web-forms that allows organizations to track and budget down to the benefit-level for each employee.

• Question 6:

  A Business Rule is launched from a data form.

  What will Planning utilize to provide a valid list of members for a run-time prompt?

  A. Members defined on the data form
  B. Planning Metadata security
  C. Business Rules security access privileges
  D. Essbase security filters
  E. Business Rules Basic User Role
  A. Members defined on the data form

  ---

  explanation:

  When launched, a business rule can prompt you to enter variable information, called a runtime business rule designer sets up runtime prompts.

  If a business rule has a runtime prompt and Use Members on Forms is selected, the default member on the runtime prompt window matches the current member in the page or POV axes of the open data form. Reference: Oracle Hyperion Planning, Fusion Edition, Release 11.1.1.3, Entering Runtime Prompts

• Question 7:

  Product status is a data element you need to include in your Planning application. Each product will have a product status that can vary over time. You will use product status in calculations and will need to report sales by product status and across products in a cross tab format.

  What is the best way to meet all of these requirements?

  A. Define Product Status as a Smart List.
  B. Define Product Status as a Separate Dimension.
  C. Define Product Status as an Attribute.
  D. Define Product Status as a Varying Attribute.
  E. Define Product Status as an alternate hierarchy in the Product dimension.
  C. Define Product Status as an Attribute.

  ---

  explanation:

  Attribute: Characteristic of a dimension member. For example, Employee dimension members may have attributes of Name, Age, or Address. Product dimension members can have several attributes, such as a size, Status, and flavor.

  Reference: Oracle Hyperion Planning, Fusion Edition, Release 11.1.1.3

• Question 8:

  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.

  ---

  explanation:

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

  You need to calculate benefit expense in your Planning application using the following logic:

  Benefit expense is equal to the Total Salary of the Organization multiplied by a factor data loaded to each cost center.

  Given the following components, what is the correct order of calculation:

  1-Custom calculation (Total Salary * Factor)

  2-Aggregate benefits

  3-Aggregate salaries

  A. 1, 2, 3
  B. 3, 2, 1
  C. 2, 3, 1
  D. 3, 1, 2
  D. 3, 1, 2

  ---

  explanation:

  First calculate the aggregated saleries.

  Then make the custom calculation on the saleries.

  Finally use the result of the custom calculation to product the benefits.

• Question 10:

  Based on the following design: Plan type 1: Summary Plan type with all Accounts by Entity Plan type 2: Sales Plan type with Sales by Product by Entity Plan type 3: Salary Plan type with Salary Expense by Employee by Entity You need to get Sales data to the Summary plan type. Identify the two true statements about

  sharing revenue data between the sales plan type and the summary plan type.

  A. Planning will build in @XREF calculations in a calc script by default to share data between plan types.
  B. A replicated partition could be created to replicate data from the sales plan type to the summary plan type and this would be done if we wanted to store the sales data in the summary plan type.
  C. A transparent partition and @XREF calculations could have performance issues for retrievals because data is not stored; it is dynamically calculated.
  D. A calc export script on the source database with the DATAEXPORT command could be used to export data out of the revenue plan type and calc import script on the target database with the DATAIMPORT command could be used to import the data file to the summary plan type.
  E. To disable the building of @XREF, update the HSPProperties file for the application before you click Create during the application creation process.
  B. A replicated partition could be created to replicate data from the sales plan type to the summary plan type and this would be done if we wanted to store the sales data in the summary plan type.
  C. A transparent partition and @XREF calculations could have performance issues for retrievals because data is not stored; it is dynamically calculated.

  ---

  explanation:

  B: Replicated Partition:

  A portion of a database, defined through Partition Manager, used to propagate an update to data mastered at one site to a copy of data stored at another site. Users can access the data as though it were part of their local database.

  C:

  Transparent partition:

  A form of shared partition that provides the ability to access and manipulate remote data transparently as though it is part of your local database. The remote data is retrieved from the data source each time you request it. Any updates made

  to the data are written back to the data source and become immediately accessible to both local data target users and transparent data source users

  Note: @XREF

  Enables a database calculation to incorporate values from another Essbase database.

  The following terminology is used to describe the @XREF function:

  Data target: the database on which the current calculation is running (that is, the database on which the @XREF call originates).

  Data source: the database that is queried by the @XREF function. This database may be remote (that is, on a different machine than the data target).

  Point of view: the member combination currently being calculated on the data target (that is, the member combination that identifies the left hand side of a calculation).

  The @XREF function retrieves values from a data source to be used in a calculation on a data target. @XREF does not impose member and dimension mapping restrictions, which means that the data source and data target outlines can be

  different.

  Note #2:

  Hyperion planning's Plan Types treated as individual databases in underlying Essbase database comes with inherent facility to share data and dimension members across plan types in Hyperion Planning or equivalent databases in underlying

  Essbase. This reduces the need for additional development/maintenance effort when compared to Planning systems based on Standalone Essbase. The Hyperion Planning user would seldom realize that the dimension members belong to

  multiple databases. While this might be an area of concern while using Standalone Essbase to build planning system.