050-730 Practice Questions

The Micro Focus Identity Manager Integrated Installer is designed to simplify and automate the deployment process. It automatically handles critical dependencies by installing prerequisite components like eDirectory in the correct sequence (A). The installer also contains the entire suite of available drivers and automates the installation process for them. While the administrator must select which drivers to install, the installer manages the automated deployment of any or all chosen drivers, which is the most reasonable interpretation of statement (B) in the context of a simplified, all-in-one installation utility.

C. The iManager plug-in needs to be manually installed

The Integrated Installer's purpose is to automatically install the necessary iManager plug-ins, eliminating the need for a separate, manual installation process.

D. It exists only for the Windows operating system family

The installer is cross-platform and is officially provided for both supported Windows Server and SUSE Linux Enterprise Server (SLES) operating systems.

1. Micro Focus Identity Manager 4.8 Installation Guide, Section 2.1, "Installation Programs". This section states, "The integrated installer automatically installs NetIQ eDirectory, and then installs the Identity Manager engine, drivers, and plug-ins for iManager." This statement directly supports that dependencies are handled (A) and refutes the claim that iManager plug-ins are installed manually (C).

2. Micro Focus Identity Manager 4.8 Installation Guide, Section 1.2, "System Requirements for Identity Manager". This section explicitly lists supported operating systems, including "SUSE Linux Enterprise Server 12 SP4" and "Windows Server 2019," which refutes the claim that the installer is Windows-only (D).

3. Micro Focus Identity Manager 4.8 Installation Guide, Chapter 3, "Installing Identity Manager on Linux Using the Integrated Installer", Step 10 ("Driver Selection"). This step shows that the installer presents a list of all available drivers for the administrator to select for automated installation, which supports the interpretation of option (B).

Best practices for using version control with Designer extend beyond the tool itself and into team processes and governance. Assigning a single team member to a specific policy (E) is a crucial development practice to prevent conflicting changes and difficult merges, which can easily occur with the complex XML structure of Identity Manager policies. Similarly, restricting production deployments to a designated individual or a very small team (D) is a fundamental IT governance principle. This ensures that all changes to the live environment are controlled, audited, and follow a consistent, tested procedure, minimizing the risk of service disruption.

A. Use the Tortoise Subversion client.

This is not a best practice. Designer has an integrated Subversion client (Subclipse) that is aware of the project's structure and metadata, which is the recommended tool.

B. Use the Subversion command line when possible.

Using the command line bypasses the integrated Designer UI, which is designed to simplify version control operations and maintain project integrity. It is not a recommended best practice.

C. Enable Subclipse before using version control with Designer.

This is a mandatory prerequisite for using version control within Designer, not a best practice for its ongoing use. A best practice describes how to use the tool effectively.

1. Micro Focus Documentation: NetIQ Identity Manager - A Team Development and Deployment Guide.

Reference for E: Section 3.2, "Best Practices for Team Development," explicitly states: "To avoid conflicts, we recommend that you assign one team member to a policy rather than having multiple team members work on one policy."

Reference for D: Section 4.2, "Deploying a Project to a Production Environment," outlines a formal, planned process. The guide states, "When you are ready to deploy the project to the production environment, you need to have a plan in place." This formal plan inherently supports the best practice of having a designated person or role responsible for the deployment to ensure control and accountability.

2. Micro Focus Documentation: NetIQ Designer for Identity Manager Administration Guide.

Reference for A & B (Incorrect): Section 8.0, "Using Version Control with a Project," details the procedures for using the integrated Subclipse client within the Designer interface. The entire chapter is predicated on using the integrated tool, not external clients like TortoiseSVN or the command line, reinforcing that the integrated approach is the intended and standard practice.

In the Standard SoD Constraint Exception Approval Workflow, the "Check for Processing Type" activity is a conditional activity. Its specific purpose is to evaluate the processingType flow data variable. Based on the value of this variable (e.g., 'quorum' or 'serial'), this activity directs the workflow to the appropriate approval path. It is the central decision point that determines whether the "Approve SoD Conflict (Quorum)" or the "Approve SoD Conflict (Serial)" activity is initiated.

A. Localize SoD Name: This activity is responsible for retrieving and displaying the SoD constraint's name in the appropriate language, not for determining workflow logic.

B. Approve SoD Conflict: This is a generic term. The actual workflow uses more specific activities for quorum and serial approvals, which are selected by the conditional check.

D. Approve SoD Conflict (Serial): This is the specific approval activity executed if the "Check for Processing Type" determines the path is serial, not the decision-making activity itself.

E. Approve SoD Conflict (Quorum): This is the specific approval activity executed if the "Check for Processing Type" determines the path is quorum, not the decision-making activity itself.

1. Micro Focus Identity Manager Roles Based Provisioning Module 4.8.x User Application: Administration Guide. Chapter 10: Managing Separation of Duties, Section: "Understanding the Separation of Duties Workflows," Subsection: "Standard SoD Constraint Exception Approval Workflow." The documentation explicitly states, "The Conditional activity checks the flowdata.get('processingType') value to determine whether to use the Quorum or Serial approval process. If the value is quorum, the workflow proceeds to the Approve SoD Conflict (Quorum) activity. Otherwise, the workflow proceeds to the Approve SoD Conflict (Serial) activity." This directly identifies "Check for Processing Type" as the determining activity.

In regular expressions, the vertical bar | acts as an alternation operator, which is equivalent to a logical "OR". The expression a|b instructs the regular expression engine to match either the character or sub-expression on its left (a) or the character or sub-expression on its right (b). This is the standard syntax for matching one of several alternatives. Therefore, a|b is the correct expression to match either the character ‘a’ or the character ‘b’.

A. “a\b”: The \b is a word boundary anchor. This expression matches the character 'a' only when it is at the end of a word.

B. “a.b”: The dot . is a wildcard that matches any single character. This expression matches a three-character string starting with 'a' and ending with 'b'.

C. “ab”: The asterisk is a quantifier meaning "zero or more" of the preceding element. This matches strings like 'b', 'ab', 'aab', and so on.

E. “a:b”: The colon : is treated as a literal character. This expression matches only the exact three-character string "a:b".

1. Micro Focus UFT One Help Center: In the "Regular Expression Character and Operator Reference," the | character is defined as: "Matches either the expression before or the expression after the |. For example, z|food matches z or food." This directly confirms the use of | for alternation. (Source: Micro Focus UFT One 2023 Help Center, Section: "Regular Expression Character and Operator Reference").

2. Micro Focus LoadRunner Professional Help Center: The documentation on "Regular Expression Syntax" specifies that LoadRunner uses Perl 5 compatible regular expressions. It defines | as the alternation operator: "Matches one of a series of patterns. For example, cat|dog matches cat or dog." (Source: Micro Focus LoadRunner Professional 2023 Help Center, Section: "Vuser Scripts > Regular Expressions in VuGen > Regular Expression Syntax").

3. MIT OpenCourseWare: In the course materials for 6.035 Computer Language Engineering, regular expression operations are formally defined. The alternation (or union) operator | is specified as r1 | r2, which denotes a match for a string in the language of r1 or a string in the language of r2. (Source: MIT OCW, 6.035 Computer Language Engineering, Spring 2010, Lecture 2 Notes, Section 2.2 "Regular Expressions").

In Micro Focus Identity Manager, access to the user interface components, such as the administration tab, is governed by role-based permissions. The administration tab contains critical system-wide configuration settings. By default, only the roles with the highest level of privilege are granted access. The Security Administrator role has full rights to all aspects of the Identity Applications. The Configuration Administrator role is specifically designed to manage all configuration settings. Therefore, both of these roles have access to the administration tab to perform their designated functions. The other administrative roles are scoped to more specific, non-configuration tasks.

B. Resource Administrator: This role is limited to managing resources and resource requests, not the overall system configuration found in the administration tab.

C. Compliance Administrator: This role focuses on compliance-related activities, such as attestation and reporting, which are managed in separate sections of the interface.

D. Provisioning Administrator: This role is responsible for managing provisioning requests and user roles, tasks performed outside the core administration tab.

1. Micro Focus Identity Manager 4.7 Administration Guide: In the section "Understanding the Default Administrative Roles," the guide details the permissions for each role. It specifies that the Security Administrator has "full rights to all aspects of the Identity Applications," and the Configuration Administrator "can manage all configuration settings," both of which necessitate access to the administration tab. The guide explicitly scopes the other roles (Resource, Compliance, Provisioning) to their respective functional areas, which do not include general system administration. (Reference: Chapter on "Managing User Application Roles and Security").

When constructing a workflow within Micro Focus Identity Manager, several structural rules must be followed for the workflow to be valid. Firstly, any parallel processing paths initiated by a Branch activity must be synchronized and brought back into a single path using a corresponding Merge activity. Secondly, a provisioning workflow's purpose is to perform an action; therefore, it must contain at least one core provisioning activity, such as an Entitlement or Entity activity, to modify identity data or grant access. Lastly, every workflow must have a single, well-defined entry point (Start activity) and a single, well-defined exit point (Finish activity) to ensure predictable and manageable process flow.

A. A workflow cannot contain a condition activity.

This is incorrect. Condition activities are fundamental components used for creating logical branches (e.g., if/then/else) based on data or previous activity outcomes, such as an approval status.

B. Each Approval activity must have a Condition activity.

This is not a strict rule. While it is common to use a Condition activity to check the result of an Approval, the flow can be routed directly from the Approval's outcomes (e.g., 'approved' or 'denied' data flows) without an intermediate Condition activity.

1. Micro Focus Identity Manager 4.7 User Application: Design Guide, Section 5.2, "Building a Provisioning Request Definition."

This section explicitly states: "All workflows must have one Start activity and one Finish activity." This supports answer E.

It also states: "A workflow must contain at least one provisioning activity (Entitlement Grant, Entitlement Revoke, or Entity) to be a valid workflow." This supports answer D.

2. Micro Focus Identity Manager 4.7 User Application: Design Guide, Section 5.6.1, "Workflow Activity Reference," subsection on "Branch Activity."

The documentation for the Branch activity states: "The Branch activity allows you to create multiple parallel paths in a workflow... You must add a corresponding Merge activity to bring the paths back together." This supports answer C.

3. Micro Focus Identity Manager 4.7 User Application: Design Guide, Section 5.6.1, "Workflow Activity Reference," subsection on "Condition Activity."

This section describes the purpose and usage of the Condition activity for creating conditional paths, demonstrating that it is a valid and essential component, which invalidates option A. The examples show its use after an Approval activity but do not mandate it, which invalidates option B.

The naming convention for a Global Configuration Value (GCV) in Micro Focus Identity Manager can be a single name (e.g., acme-gcv) or a structured name. A structured name uses a period (.) as a separator to create a hierarchical or namespaced identifier, allowing for better organization. The format [.].[.] correctly represents this structured convention, where each bracketed placeholder signifies a component of the name. For example, a GCV could be named acme.passwords.default to clearly denote its purpose within a larger configuration scheme.

A. ..[.][]: This syntax, featuring double dots and adjacent bracketed components without a separator, is not a valid GCV naming format.

B. .[.][.]: This format is incorrect because valid GCV names do not start with a period, nor do they use adjacent bracketed components.

C. .[.].[]: This syntax is invalid as GCV names are not prefixed with a period.

E. .[.][.]: This is a duplicate of option B and is incorrect for the same reasons.

1. Micro Focus Identity Manager 4.8.1: Policies in Designer Administration Guide.

Reference: Chapter 6, "Global Configuration Values," Section 6.1.1, "GCV Naming Conventions."

Content: This section explicitly states, "When you create a GCV, you must give it a name. The name can be a single name, such as acme-password-gcv, or it can be a structured name, such as acme.passwords.default." This directly supports the [.].[.] structure as a valid convention for structured GCV names.

Designer for Identity Manager is a client-side tool primarily used for the development, configuration, and deployment of Identity Manager solutions. It includes a powerful Simulator feature that allows developers to test policies and rule logic in an offline capacity, without needing a live connection to the Identity Vault or connected systems. Furthermore, a core function of Designer is to manage the lifecycle of a solution, which includes deploying the configured drivers and policies to different environments, such as development, testing, and production servers.

B. Designer is a configuration and deployment tool, not a comprehensive administration utility. Day-to-day administrative tasks on a live system, such as managing users, are performed with tools like iManager.

D. A fundamental feature of Designer is the ability to perform a "live import" of an existing Identity Manager configuration directly from the network (the Identity Vault) into a Designer project for modification or documentation.

1. Micro Focus Documentation: Designer for Identity Manager 4.8 Administration Guide.

For Answer A: Section 10.1, "Simulator," states, "The Simulator allows you to test your policies before you deploy them in a production environment. You can test policies without having Identity Manager and the drivers running." This confirms the offline testing capability.

For Answer C: Section 1.1, "Understanding Designer for Identity Manager," states, "Designer is a client-based tool for designing, customizing, testing, and documenting an Identity Manager solution. After you have created a solution, you can deploy it to one or more Identity Vaults." This confirms its role in deploying to various environments.

For Answer D: Section 4.1, "Importing an Existing Driver Set into a Project," explicitly details the procedure: "You can import an existing Identity Manager driver set and its objects from eDirectory into a project." This directly contradicts option D.

2. Micro Focus Documentation: Identity Manager 4.8.5 Administration Guide.

For Answer B: This guide details the use of iManager for administrative tasks. Chapter 7, "Administering Identity Manager," outlines tasks performed in iManager, such as viewing driver status and managing users, distinguishing its role from Designer's configuration-focused purpose. This clarifies that Designer cannot perform any task on the live system.

The Integration activity, also known as the Web Service Wizard in Micro Focus Operations Orchestration (OO) Studio, is specifically designed to automate the creation of operations for SOAP-based web services. It achieves this by parsing a Web Services Description Language (WSDL) file. The WSDL is an XML-based document that provides a machine-readable description of the web service's interface, including its available operations, data types, messages, and endpoint location. The wizard uses this structured information to automatically generate a complete action model, which can then be used within orchestration flows without manual configuration.

A. CSV: This is a format for representing tabular data and does not contain the necessary structure to describe a web service's API contract.

B. TXT: A generic, unstructured text file format that lacks the schema required to define web service operations, inputs, and outputs.

C. XMI: XML Metadata Interchange is a standard for exchanging metadata, such as UML models, not for defining the public contract of a web service.

D. XML: While WSDL is written in XML, XML itself is a generic markup language. The wizard requires the specific WSDL schema, not just any XML document.

1. Micro Focus Operations Orchestration Documentation (2022.05), Studio Guide, Chapter: "Wizards", Section: "Use the Web Service Wizard". This section explicitly states, "The Web Service Wizard helps you create flows that use web services. The wizard uses a WSDL file to create operations that call the web service." The first step of the wizard requires the user to provide the path or URL to the WSDL.

2. Micro Focus Operations Orchestration Documentation (10.x), Content Authoring Guide, Part 2: "Authoring in Studio", Chapter 10: "Wizards", Section: "Web Service Wizard". This older documentation similarly details the process: "The Web Service wizard enables you to create operations for Web services, based on a WSDL (Web Service Definition Language) document." It describes how the wizard reads the WSDL to generate the necessary inputs, outputs, and results for the operations.

The Role Mapping Administrator is a web-based tool delivered with NetIQ/Micro Focus Identity Manager’s Roles-Based Provisioning Module. Its sole purpose is to link, or “map,” authorizations that exist in connected applications (e.g., SAP roles, AD groups) to business roles that reside in the Identity Vault. Neither iManager, Designer, nor the User Application contains this dedicated mapping interface; they can view or request roles but cannot perform the authorization-to-role correlation task.

A. iFilter – No relation to Identity Manager; used for enterprise search indexing.

B. iManager – Administers eDirectory objects and some IDM drivers, but provides no interface to map external authorizations to Vault roles.

C. Designer – Design/deploy drivers and workflows offline; lacks runtime authorization-mapping functionality.

D. User Applications – End-user and workflow portal; requests roles but cannot create authorization mappings.

1. Micro Focus (NetIQ) Identity Manager 4.8 – Role Mapping Administrator Administration Guide, Section 1.1 “About Role Mapping Administrator,” para 2: “…maps application permissions and authorizations to roles in the Identity Vault.”

2. Micro Focus Identity Manager 4.8 – Installation Guide, Ch 18 “Installing the Role Mapping Administrator,” first paragraph: “Install this component when you need to correlate external system entitlements with Identity Manager roles.”

3. NetIQ Identity Manager 4.7 – Roles Based Provisioning Module User Guide, p. 15: distinguishes Role Mapping Administrator from iManager and User Application, noting only RMA “provides the mapping functionality.”