IBM Professional Certification Program

Certify your skills. Accelerate your career.

Test C9010-251: Power Systems with POWER8 Scale-out Technical Sales Skills V1

Section 1 - Power Systems Architecture and Product Family (29%)

  1. Identify and differentiate models and features within the Power Systems Scale-out product family, including I/O, memory, and processor.

  2. Compare POWER7/7+ to POWER8 for migration purposes.

  3. Articulate Scale-out server Reliability, Availability and Serviceability (RAS) capabilities.

  4. Given a customer's networking and storage requirements, identify and configure the appropriate I/O and storage features.

  5. Describe the benefits of POWER processor architecture, including SMT, cache, balanced performance, clock speed, EnergyScale, CAPI, etc.

  6. Differentiate between memory optimization technologies for Power Systems (for example: Active Memory Expansion (AME), Active Memory Sharing (AMS)), identifying the configuration requirements of each on the systems which support them.

  7. Given a scenario, describe why Power Systems is the preferred platform for a CAMS (Cloud, Analytics, Mobile, Social) solution, including optimization for DB2, Cognos, SPSS, etc.

  8. Determine processor requirements for micropartitioning, shared processor pools, dedicated and shared dedicated processors, etc.

  9. Position POWER8 Scale-out servers with regards to price performance, workload consolidation, virtualization without limits, design for function, etc. (Compare and contrast with other POWER as well as x86 servers).

  10. Identify features/function/capability of SR-IOV.

Section 2 - Virtualization (27%)

  1. Given a scenario, recognize when to configure physical I/O, virtual I/O or a combination of both.

  2. Describe storage hardware connectivity (Fibre Channel or SAS) options and types of virtualization (NPIV, vSCSI).

  3. Describe the value of shared storage pools (SSP).

  4. Identify the configuration requirements for Live Partition Mobility.

  5. Given a scenario, describe Power Systems' ability to share resources including processors, I/O and memory.

  6. Describe the business advantages of virtualization from a technical perspective.

  7. Differentiate capabilities of Power Hypervisor offerings (e.g., PowerVM, PowerKVM).

  8. Position Power Hypervisor offerings (PowerVM, PowerKVM) compared to competitive offerings (VMWare, Hyper-V, Xen Server, KVM on x86).

  9. Design an appropriate virtualization system management solution (consider: HMC, IVM, PowerVC, Cloud Manager with OpenStack).

  10. Design an appropriate console solution (consider migration options, operating systems and virtualization, and high availability: HMC, ASMI, Putty, LAN Console).

  11. Compare and contrast PowerVC features with VMware.

  12. Discuss the offerings available for OS virtualization (e.g., WPAR).

Section 3 - Design Solution to Customer Requirements (29%)

  1. Given a set of customer requirements, differentiate the POWER8 Scale-out server capabilities for each of the scale-out servers, and make a recommendation that best meets their need(s).

  2. Given a set of business requirements, create an optimal technology solution.

  3. Incorporate appropriate existing hardware in a new configuration.

  4. Evaluate storage requirements, disk protection options (RAID-5,6,10, mirroring), storage tiering, and placement (e.g., internal disk, SAN, Flash), appropriate to OS environments.

  5. Given customer requirements, design a single or dual VIO server solution (including using NPIV and vSCSI to host storage). Consider requisites, corequisites and limitations which may impact future requirements.

  6. Given customer requirements such as RTO (Recovery Time Objective) and RPO (Recovery Point Objective), design an HA or DR environment at a high level (e.g., synchronous vs. asynchronous, Copy Services offering, Global Mirror vs. Metro Mirror), including selecting the appropriate PowerHA Edition and capabilities.

  7. Given a scenario, identify the correct planning tools and information resources such as eConfig, System Planning Tool (SPT), Workload Estimator (WLE) and Sizing Guide, Energy Estimator, and System Performance Reports to confirm that the requirements of the solution have been met.

  8. Evaluate networking requirements needed to manage redundancy, vLAN, security, bandwidth (CPU requirements, network settings) and sharing, including determining the correct adapter type(s) and quantity.

  9. Discuss a customer's requirements with regards to TCA and TCO (e.g., software licensing relative to cores).

  10. Identify strategic activities and technologies (e.g. CAPI, OpenPOWER Foundation) that allow Power Systems to be positioned in open initiatives (Google, TYAN, Mellanox, Samsung, NVIDIA).

  11. Identify solution editions (CAMS: IBM Solution for Hadoop - Power Systems Edition, IBM Solution for Analytics - Power Systems Edition, BLU Acceleration- Power Systems Edition, IBM SmartCloud Entry on Power Systems, IBM Power Systems Solution Edition for Scale-out Cloud).

  12. Identify environment considerations (e.g., power, UPS, space, racks, etc.).

  13. Defend the solution against competitive technical claims (e.g., cost per VM, price per watt, etc.)

Section 4 - Software and Operating System Considerations (15%)

  1. Given a customer's requirements, identify which operating system (or mix of operating systems) is appropriate and defend the choice (AIX, IBM i, or Linux).

  2. Describe Power Systems licensing considerations with regard to transfers, sub-capacity licensing, etc. (operating systems, PowerVM, etc.).

  3. Recognize the basic security strengths in AIX, Linux, IBM i, and PowerVM and discuss PowerSC offerings.

  4. Given a customer's requirements, describe which Power Systems Software product, and Edition, is appropriate, including PowerHA, PowerVM, and PowerVC.

  5. Given a customer's requirements, identify which IBM Software Group product category is appropriate, including Rational, Tivoli, WebSphere, DB2, Cognos/SPSS, etc.

  6. Identify supported Linux distributions (RedHat, Ubuntu, SUSE) and their features (including Endian / portability considerations).


Connect with Us