Skip to main content

 
Professional certification

  >  
Certifications

  >  
Test information

Test 931: IBM Tivoli Netcool/Proviso V4.4.1 Implementation


Overview Objectives Test Preparation

Section 1: Planning

  1. Given network infrastructure documentation and customer requirements, gather the resources so that a list of resources is created for sizing Proviso. With emphasis on the following steps:
    1. Gather Network Infrastructure documentation.
    2. Gather customer requirements.
    3. Determine a list of vendor equipment.
    4. Determine technologies.
    5. Estimate the number of resources for vendor and technology.
    6. Create the list of resources for sizing.

  2. Given basic customer requirements, gather Proviso-related requirements so that a sizing can be performed and an end-to-end architecture can be created. With emphasis on the following steps:
    1. Meet with customer stakeholders.
    2. Determine technical requirements based on network hardware and services to be monitored.
    3. Produce metrics list based on all requirements.
    4. Match Application Packs to metrics list and produce Application Pack list.
    5. Produce user list or template based on all requirements.
    6. Produce grouping structure or template based on all requirements taking into account both technologies and user template.
    7. Produce input data requirements list based on for provisioning.
    8. Produce document showing mock-up of grouping structure, reporting structure, and describing user experience.
    9. Verify user experience document with customer; modify if necessary.

  3. Given a customer’s requirements for SNMP and BULK (non-VOIP) devices in the target network, translate them into hardware architecture, so that the requirements can be met. With emphasis on the following steps:
    1. Identify the application packs required.
    2. Size each application pack based on number of devices/resources in the target network.
    3. Validate the application-pack sizing with Product Management.
    4. Produce the sizing output based on Abacus estimates, for the hardware preferences of the customer taking into account the geographical, network and firewall constraints, and high-availability/failover requirements, draft a sizing output document specifying the CPU, Memory and Disk requirements for servers to handle each type of Proviso workload.
    5. Review sizing output with PMG.
    6. Review and agree sizing output with the customer.

  4. Given a customer’s requirements, develop an architecture around the product, so that the requirements are fulfilled. With emphasis on the following steps:
    1. Prepare a list of functions and features required.
    2. Conduct a sizing exercise for all required application packs.
    3. Review and agree sizing output with the customer.
    4. Prepare a solution architecture based on sizing, and high-availability requirements.
    5. Review and obtain agreement on solution architecture with the customer.
    6. Prepare a list of custom artifacts to develop, including integrations with ISV systems, and obtain agreement with the customer.
    7. Document and obtain agreement on the backup policy, both for file system and database, with the customer.
    8. Document the database table spaces layout for different types of data, based on retention policies and size of mount points.
    9. Develop a set of high-level tests to validate the solution upon delivery.

  5. Given access to the Proviso and Oracle configuration files examine the protocols and ports used to communicate between the Proviso components so that firewall ports can be configured correctly. With emphasis on the following steps:
    1. Examine the DataLoad environment file, dataLoad.env, or the DataLoad registry to identify the DataLoad service (SSD) port.
    2. Examine the SNMP configuration tool to determine the port(s) and hosts that SNMP requests will be sent to.
    3. Examine the DataChannel configuration file, dc.cfg, to determine the file transfer method and ports used by each FTE and bulk collector.
    4. Examine the DataChannel configuration file, dc.cfg, and the DataView configuration page, DVConfigurationPage.html, to determine the ports used for CORBA communication.
    5. Examine the DataChannel configuration file, dc.cfg, to determine the ports used for logging.
    6. Examine the DataChannel configuration file, dc.cfg, to determine the SNMP trap destination hosts and ports.
    7. Examine the Oracle net service names file, tnsnames.ora, or the listener configuration file, listener.ora, to determine the ports used to connect to the database.

  6. Given a Proviso solution, gather customers business requirements so that a HA/failover architecture can be created. With emphasis on the following steps:
    1. Gather customer requirements.
    2. Determine Proviso components that require HA/Failover.
    3. Determine the type of HA/Failover for each component (1+1, N+1).
    4. Determine Technologies to use (SilverStream cluster, HAM, Veritas, Sun Cluster).
    5. Determine additional Hardware requirements.
    6. Create Proviso HA/Failover architecture.

  7. Given recovery time requirements and sizing information, produce a disaster recovery draft plan and add backup capabilities to Proviso in the project implementation plan so that the customer's requirements are met. With emphasis on the following steps:
    1. Use the Abacus created during sizing exercise to determine full database size.
    2. Using the same Abacus, determine amount of data added to database daily.
    3. Calculate approximate length of time for full backup, restore based on inputs.
    4. Using backup solution throughput and data retention requirements, calculate time between baseline backups in order to meet recovery time requirement.
    5. Add database modifications into implementation plan.
    6. Add DataChannel modifications into implementation with dependency that database backup is already running.
    7. Determine the file systems that need to be backed up for application components including DataChannel, DataView, DataMart and DataLoad.

Section 2: Installation

  1. Given the sizing output, install IBM Tivoli Netcool/Proviso so that IBM Tivoli Netcool/Proviso v4.4.1 is installed on a distributed platform. With emphasis on the following steps:
    1. Verify all systems are updated to latest patch level.
    2. Update Oracle Database server /etc/system file with Oracle Settings and reboot of the server.
    3. Define environment variables in /etc/profile.
    4. Update /etc/hosts and test connectivity to all relevant servers.
    5. Add users and groups.
    6. Install Oracle database using the “perform_oracle_inst” found within the DataMart as the oracle user.
    7. Install Oracle client on all other servers.
    8. Install Proviso in the following order on the relevant platforms as suggested during the planning phase:

      9. -Database Configuration
      -Database Channel
      -DataMart
      -DataLoad Collectors
      -DataChannels
      -Application Packs
      -SilverStream Server
      -DataView
    9. Validate that all components are working.

  2. Given a running Proviso system, determine the necessary components to be upgraded, and what impact this will have on the system so that the system is ready for a Proviso upgrade. With emphasis on the following steps:
    1. Determine the version to upgrade from, and the version to upgrade to.
    2. Determine if the upgrade will require an Oracle upgrade or patch.
    3. Determine if the upgrade requires a patch to one or more Proviso components, or all of Proviso components.
    4. Plan upgrade on test or development environment.
    5. Determine if any changes to the database will occur. If so allocate space on the disk and plan for a backup of the database.
    6. Complete an SNMP DataLoad audit.
    7. Determine if upgrades to Application Packs are necessary. If upgrades are necessary, review what implications, what special steps and what possible negative effects the upgrade can have.
    8. Determine all scripts and configuration files that may be overwritten as part of the upgrade (InventoryHook.sh, inventory_subelements.txt).
    9. Allocate adequate space to backup and store DataChannel data files.
    10. Review documentation on upgrade and plan for outages to the system as necessary.

  3. Given the UBA based Application Pack, install and configure components to import and parse data files so that the bof files are provided in the output directory of the UBA and the inventory is updated in the database. With emphasis on the following steps:
    1. Install the UBA application pack.
    2. Copy js scripts from DataMart to UBA server(s).
    3. Identify data source location.
    4. Amend master dc.cfg to include UBA,CME,FTE, LDR and source data location configurations for UBA.
    5. Copy master dc.cfg to all DataChannel servers.
    6. Install any ancillary scripts/applications that preprocess data.
    7. Configure Grouping in cron on DataMart server.
    8. Start UBA and preprocessor scripts.
    9. Complete inventory cycle.
    10. Verify data is going downstream.

  4. Given a Proviso platform, verify that all components are functioning correctly, so that a baseline can be captured. With emphasis on the following steps:
    1. Verify Proviso database is set to start up on boot.
    2. Log on to the DataMart, and verify the Proviso Info daemon is running.
    3. Verify whether the DataMart crontab has an entry for period analysis of Proviso’s metadata tables.
    4. Log on to the DataChannel, and verify if all DataChannel components are working correctly.
    5. Verify all BULK sub-channels can talk to the remote/ISV systems.
    6. Verify if all watchdogs are correctly listed in crontab for all configured DataChannels, including the CMGR host.
    7. Verify whether Proviso’s discovery process can be invoked correctly.
    8. Log on to the DataView and check whether SilverStream is up and running.
    9. Verify SilverStream is configured to startup on system reboot.
    10. Log on to the Web portal and check whether the reports respond, and that all relevant reports have data.
    11. Verify that the localization is configured correctly.
    12. If a SilverStream cluster is configured, verify all servers in the cluster are serving reports.
    13. Log on to the DataLoad and verify if the pvmd process is running, and responding.
    14. Verify if the SNMP DL is configured to startup on reboot.
    15. If the SNMP High-Availability Module (HAM) is configured, verify if all profiles are configured correctly.
    16. If the SNMP DataLoads are managed by HAM, verify whether they are allowed sufficient grace period for HAM to startup a spare.
    17. Verify the versions of all registered Proviso components using the dbMgr tool, and ensure all relevant components at version 4.4.1.

  5. Given a Proviso architecture and solution, install a Proviso SNMP HA so that SNMP HA is operational. With emphasis on the following steps:
    1. Install SNMP HA Monitor using the DataChannel installation program.
    2. Install SNMP collector binaries onto the spare hardware.
    3. Configure HA Monitor.
    4. Configure participating SNMP DataLoads to work under HA.
    5. Start HA Monitor and participating SNMP DataLoads.
    6. Validate HA Monitor is working and controls participating SNMP DataLoads.

  6. Given an existing, non-HA Proviso system, reconfigure Proviso system to operate properly under either a Veritas or Solaris cluster so that high availability for the core Proviso components is achieved. With emphasis on the following steps:
    1. Reconfigure Oracle database server for HA.
    2. Reconfigure DataMart for HA.
    3. Reconfigure DataChannel for HA.
    4. Reconfigure Bulk DataLoad for HA.
    5. Install SilverStream cluster.
    6. Verify that all components work with virtual host names.

  7. Given a running Proviso system, configure two DataView and SilverStream servers to work as a cluster so that the cluster can be used for load balancing purposes or general redundancy. With emphasis on the following steps:
    1. Install SilverStream and DataView on the initial server.
    2. Verify the initial server installation works by accessing the appropriate URL and logging into the server.
    3. Install DataView SilverStream on all other cluster servers.
    4. Verify all cluster servers work by accessing the appropriate URL and logging in to the servers.
    5. Stop all SilverStream servers and start the SilverCacheMgr on the primary cluster server.
    6. Start all SilverStream servers.
    7. Configure the cluster within SilverStream.
    8. Verify the Cluster is working properly.

Section 3: Configuration

  1. Given the SNMP MIB, import and compile the MIB, so that it is available in the Proviso MIB Browser. With emphasis on the following steps:
    1. Upload the MIB to the DataMart server.
    2. Import MIB using the MIB Compiler application as per Documentation.
    3. Compile MIB as per Documentation.
    4. Validate the new MIB has been uploaded to the SNMP DataLoads.

  2. Given a Proviso solution, examine the grouping structure, so that collection and report grouping is understood. With emphasis on the following steps:
    1. Log on to the Proviso DataMart.
    2. Examine the group(s) where requests are deployed.
    3. Verify that the resources in these groups have same metrics being collected against them, independent of the web-portal navigation.
    4. Examine the group(s) where reports are deployed.
    5. Verify the resources in these groups are visible in the reports deployed against them.
    6. Note the portal navigation is the same as the grouping structure where reports are deployed, for a reports user with NOC profile.

  3. Given customer device requirements, write a discovery formula to enable collection of a new device type so the customer can collect data. With emphasis on the following steps:
    1. Validate the MIBs supported by the device.
    2. Import any device specific MIBs needed.
    3. Determine the variables that can be used to uniquely identify resources on this device.
    4. Determine the properties needed to support the collection and reporting requirements.
    5. Write the discovery formula.
    6. Test the discovery formula.

  4. Given access to a Proviso system write a property merge discovery formula to expand upon or override the properties set by base discovery formula so that properties are added to resources after the discovery. With emphasis on the following steps:
    1. Log in to the DataMart and open the SNMP Formula Editor.
    2. Load the base discovery formula to act as a reference to the available input indices, properties returned.
    3. Alter the base formula to create a new property merge formula where new properties are added and / or old properties are overwritten and ensure the property merge formula does not create any resources. @Test the formula.
    4. Save the formula under a new name.
    5. Add the new formula to the inventory_subelements.txt file after the existing formula.
    6. Run discovery to test the results returned.

  5. Given a proviso SNMP discovery profile, configure the inventory_subelement.txt file so that the appropriate subelements are discovered. With emphasis on the following steps:
    1. Determine the Elements to be discovered.
    2. Determine the subelements to be discovered.
    3. Determine the property merge formulas to be used.
    4. Determine the required discovery formulae.
    5. Determine the appropriate OID’s.
    6. Amend the inventory_subelements file as required.
    7. Verify the inventory_subelements by carrying out a discovery.

  6. Given an operating Proviso environment and inventory profiles, configure and automate inventories so that the inventory procedure runs successfully per customer requirements. With emphasis on the following steps:
    1. Determine the inventory provisioning process.
    2. Write scripts to integrate with the inventory system(s).
    3. Schedule SNMP inventory scripts as required.
    4. Schedule BULK inventory scripts as required.
    5. Validate inventory is automated for SNMP and BULK data.

  7. Given a compiled MIB, read community string, firewall and ACL access to an SNMP enabled device, write and test a basic SNMP formula in Proviso so that valid data is returned. With emphasis on the following steps:
    1. Determine the type of data that needs to be collected from the device, and the MIB that contains that data.
    2. Determine if a generic metric will be used on the collection formula.
    3. Write the formula.
    4. Test the formula.
    5. Save the formula.

  8. Given the reports requirements, configure portal navigation rules so that users can access the appropriate reports. With emphasis on the following steps:
    1. Configure the grouping rules as required.
    2. Deploy reports as necessary.
    3. Assign groups to report users as necessary.
    4. Verify configured rules.

  9. Given a Proviso solution, create a custom report, so that the customer’s requirements are fulfilled. With emphasis on the following steps:
    1. Using DVNavigator, create a new report style, as necessary.
    2. Using DVNavigator, create a new reporter, based on the selected report style in the reporting group of choice, using the collection or CME formulae of choice
    3. Specify other reporting options such as properties, stats, resource filters, report granularity, drill-down, etc., as required.
    4. Deploy the new report on the reporting group of choice, and perform auto-grouping.
    5. Verify the report is displayed commensurate requirements.

  10. Given customer reporting requirements, create or amend portal configuration items so that reports are available as per the customer's business requirements. With emphasis on the following steps:
    1. Define the report types and colors to be used.
    2. Determine the report and graph names and formats.
    3. Add any customer logos.
    4. Validate drill downs to be accessed.
    5. Determine whether or not to display the threshold values and types.
    6. Establish who will be granted access to these reporters.
    7. Determine how to deploy the reporters.

  11. Given access to a Proviso system write a CME formula so that report statistics can be generated. With emphasis on the following steps:
    1. Log in to a DataChannel host and open the CME Formula Editor.
    2. Choose the input metrics and properties.
    3. Define any variables needed.
    4. Create the code to calculate the output.

      5. -Test the formula.
      -Save the formula.
    5. Deploy collection requests for the formula.
    6. Use bofDump to monitor the output of the new CME formula.
    7. Examine proviso.log to monitor the success of the new CME formula.

  12. Given Proviso design documentation, configure Proviso thresholds so that the customer's requirements are met. With emphasis on the following steps:
    1. Obtain the required design documentation.
    2. Configure the metric for thresholding.
    3. Configure the Proviso group or resource where the threshold will be applied.
    4. Configure the defined Threshold type.
    5. Verify threshold configuration.

  13. Given an installed, functioning Proviso system, configure Proviso to send threshold violation alarms so that the trap receiver will record them and alert operators. With emphasis on the following steps:
    1. Configure the CME’s in the DataChannel configuration with the appropriate trap destination information.
    2. Copy the DataChannel configuration to all DataChannel, DataMart, and Bulk DataLoad hosts.
    3. Restart all CME’s.
    4. Provide Proviso MIB file to trap receiver administrator(s).

  14. Given bulk data input files, inspect the files so that the data feed may be understood. With emphasis on the following steps:
    1. Obtain bulk data files.
    2. Inspect the data files.
    3. Determine subelelement definitions.
    4. Determine metric definitions.

  15. Given the requirement to provide scheduled reports, configure Proviso so that reports are created automatically. With emphasis on the following steps:
    1. Configure Scheduler by logging in to the DataView Server and applying settings.
    2. Configure the Users to enable Administration and viewing in DataMart.
    3. Configure Users to receive the appropriate report at the required frequency.
    4. Verify delivery by setting up a test delivery.

  16. Given a Proviso solution, configure reports users, so that they are able to view Proviso reports. With emphasis on the following steps:
    1. Create a SilverSecurity group, if required.
    2. Create SilverStream user with SilverSecurity.
    3. Add the new SilverStream user to SilverStream group.
    4. Create a DataView user with the same name as the SilverStream user.
    5. Add the new DataView user to a DataView group.
    6. Add the reporting groups to the DataView user as required.
    7. Assign properties to the DataView user as required.

  17. Given a Proviso platform, configure filesystem and database backups, so that data can be recovered following failure or corruption. With emphasis on the following steps:
    1. Determine the customer's current backup process.
    2. Determine the files that will need to be backed up for each of the Proviso components.
    3. Implement filesystem backup.
    4. Implement Oracle backup.
    5. Schedule backups based on frequency.
    6. Validate backup completeness.
    7. Validate restore.

Section 4: Administration

  1. Given access to a Proviso system, configure the database management tasks so that the Proviso database is efficiently managed. With emphasis on the following steps:
    1. Ensure all default variables in the PV_partition_purge.ksh and logon.info files are set correctly.
    2. Use the dbMgr utility to set appropriate table space and file system thresholds.
    3. Set the SNMP trap and mail destinations in the notifyDBSpace script.
    4. Schedule daily execution of the PV_partition_purge.ksh script with the required metric data retention parameters to enforce an appropriate data retention policy and manage the size of the database.
    5. Schedule daily execution of the dbMgr table space and file system monitoring functions to proactively monitor each table space and mount point.
    6. Schedule daily execution of the dbMgr analyze metadata tables function to ensure query execution plans are always optimal.

  2. Given an operating Proviso environment, write a script or set of scripts to export data using the DataAccess API so that consumable data for third-party systems is provided. With emphasis on the following steps:
    1. Determine relevant reporting groups, metrics, and properties that must be exported per customer requirements.
    2. Select the appropriate query or set of queries that will return the set of data needed.
    3. Parse and combine data as needed to produce output conforming to customer requirements.

  3. Given an installed and running Proviso environment that contains customized or modified content, extract that content and import it into another Proviso system cleanly so that the content can be reused in the new system. With emphasis on the following steps:
    1. Determine the content to be migrated.
    2. Export the content from the source system.
    3. Re-map the dbIndex fields as needed.
    4. Import the content into the target system.
    5. Test the target system to ensure all data has been successfully migrated.

  4. Given the task to upgrade a Proviso instance, perform preparation tasks so that Proviso instance can be upgraded successfully. With emphasis on the following steps:
    1. Complete an audit of the Complete Proviso Instance and Oracle database.
    2. Review documentation for recommended Upgrade steps.
    3. Review disk space for backup locations.
    4. Investigate Customizations and identify best method of migration to upgrade Proviso.
    5. Document method of upgrade for customer agreement.

Section 5: Performance Tuning and Problem Determination

  1. Given a Proviso solution, troubleshoot the SNMP discovery, so that the root cause(s) may be identified. With emphasis on the following steps:
    1. Check whether the inventory binary is able to successfully communicate to the Discovery process.
    2. Check whether the Proviso solution has been supplied the correct SNMP community string to talk to the device(s) in question.
    3. Check whether the discovery formulae to be used for the profile are actually present in the database and working.
    4. Check whether the resources in question are being cancelled via inventory_subelements.txt.
    5. Check whether the SNMP DataLoad is receiving any malformed PDUs.
    6. Check whether the SNMP DataLoad is able to handle PDUs with incomplete OIDs. Check whether the SNMP DataLoad is overloaded.
    7. Check whether the discovery process is able to complete normally.
    8. Check whether discovery is timing out.
    9. Check whether the discovered resources are being discarded by any wrapper provisioning scripts.
    10. Check whether the discovered resources have all required properties.

  2. Given a Proviso solution, troubleshoot the SNMP collector so that the root cause is identified. With emphasis on the following steps:
    1. Determine whether there are any error messages within the log file.
    2. Validate if there any request errors from the devices.
    3. Determine if BOF files are still being generated by the collector and if they are moving through the channel.
    4. Verify if the data files contain resources and metrics.
    5. Determine if there have been any newly inserted formulas assigned to a non-supported resource group.
    6. Validate the overflow percent ratio for the collector.
    7. Verify if there are enough free table spaces within the Oracle database.

  3. Given access to a Proviso system troubleshoot bulk discovery so that bulk discovery runs correctly. With emphasis on the following steps:
    1. Determine if the collector is in an abnormal state.
    2. Determine if the collector is starting up as expected.
    3. Determine if the correct input is available.
    4. Determine if the collector is producing output data.
    5. If using a BCOL-based application pack, determine if the collector can transfer data to the inventory host (DataMart).
    6. If using a UBA-based application pack, determine if the inventory data is being processed correctly as appropriate for the particular application pack or design file.

  4. Given a Proviso solution with bulk collectors with an abnormal condition, troubleshoot the collector so that the root cause of the abnormal condition can be determined. With emphasis on the following steps:
    1. Determine the collector with an abnormal condition.
    2. Determine if the collector is starting up as expected.
    3. Determine if the correct input is available.
    4. Determine if the collector is producing output data.
    5. Determine if the correct requests are turned on.
    6. Determine if the abnormal condition affects all of the subelements in collection.
    7. Determine if the collector is processing data as defined by its design file.
    8. Determine if the collector is reading the input files available.
    9. Determine the root cause using all available information.

  5. Given a working Proviso system, describe how to interact with BOF files so that the data can be analyzed. With emphasis on the following steps:
    1. Do a simple dump of a set of BOF files.
    2. Search all BOF files for any metric data for a given resource ID.
    3. Search all BOF files for any resource ID’s for which data exists for a given metric ID.
    4. Export a set of all data for a given range of time given that range in EPOC format.

  6. Given a running Proviso system determine why no data is showing up in a report so that the cause of the problem is discovered. With emphasis on the following steps:
    1. Determine if the user is allowed access to see that section of data through the DVUserEditor.
    2. Verify that the reporter is pulling the correct metric in the report.
    3. Verify the status of all running components.
    4. Determine if there is a calendar and time zone associated with the group that is being reported on. @Determine if there is a valid request for the metric(s) contained in the report.
    5. Verify that the collector can connect to the device.
    6. Validate the request is active.
    7. Check the BOF files to ensure that they contain data for the metrics.

  7. Given a Proviso solution, troubleshoot component communications so that failed communications and corrective actions are identified. With emphasis on the following steps:
    1. Identify failed communications
    2. Ensure components have started up correctly
    3. Ensure there are sufficient system resources for CORBA communications.
    4. Ensure correct ports are being used.
    5. Ensure correct username/passwords are used.
    6. Ensure SNMP communication with the target network devices functions correctly.
    7. Arrange review of firewall logs to ensure compliance

  8. Given a Proviso solution, troubleshoot CME formula(e), so that the root cause is identified. With emphasis on the following steps:
    1. Open the Proviso log to identify any CME problems.
    2. Open the CME formula(e) in question.
    3. Determine if the input bindings are defined correctly.
    4. Determine if there is a circular reference.
    5. Determine if there are any syntax errors.
    6. Determine if the correct persistence of variables is used.

  9. Given that data is not displaying appropriately, troubleshoot aggregation sets so that root cause is identified. With emphasis on the following steps:
    1. Determine if the aggregation set has been appropriately created.
    2. Determine if a time zone and calendar have been assigned to the group.
    3. Determine if the aggregated data for the specified resources or resource groups can be viewed.
    4. Validate if there are any relevant error messages in the log files.
    5. Determine if the time and date have been set correctly on the server and relevant resources.

  10. Given access to a Proviso system, investigate and tune the performance of each component so that the system performs optimally. With emphasis on the following steps:
    1. Audit the proviso system to determine the key performance indicators and hence the areas on which to focus tuning activity.
    2. Perform performance tuning such as:

      3. -Deactivate unnecessary collection requests.
      -Reduce the frequency of collection.
      -Deactivate discovery formulae to prevent the discovery of unnecessary sub-elements.
      -Alter discovery formulae to filter out unnecessary sub-elements.
      -Disable unnecessary groups and rules to reduce the load on the CME.
      -Clean the meta-data tables.

  11. Given a Proviso solution, investigate all proviso components so that a proviso audit report detailing system performance can be created. With emphasis on the following steps:
    1. Investigate DataLoad components.
    2. Investigate DataChannel components.
    3. Investigate DataMart components.
    4. Investigate DataView components.
    5. Investigate Database components.
    6. Investigate HA setup.
    7. Create Audit report.

Test registration

Authorized Prometric test centers (worldwide testing)