C2030-284 全真模擬試験 DEMO

問題8: What are three non-functional requirements related to cloud computing?
A. network - access for workload
B. storage - type required for workload
C. compute - requirements for workload
D. availability - delivery making workload available
E. security - define the level of compliance needed
F. scalability - define the maximum number of users to support
正解: D,E,F
Explanation:
http://public.dhe.ibm.com/partnerworld/pub/certify/study_guide_c2030_284.pdf
Page: 45-46
Describe non-functional requirements (NFRs) in the context of a cloud solution.
NFRs identify critical aspects of the cloud solution that are not feature/function related. NFRs impact
the solution design by clearing identifying key characteristics of cloud operations.
3.14.1.Availability and serviceabilityincludes characteristics such as high availability, DR, acceptable
downtime or degradation of services during maintenance. The availability expectations of a system
relate to how many hours in the day, days per week, and weeks per year the application is going to
be available to its users and how quickly they should be able to recover from failures. Since the
system includes Software (including applications), Hardware and Network components, this
requirement extends to all three types. The serviceability expectations must integrate with existing
support structure and support processes, provide a ticketing system to log/track problem tickets and
that integrated with an existing ticketing system, support automatic patch download and installation
and provide sufficient diagnostic information (logs, dumps, traces) to expedite problem resolution
and support service level agreements often measured by key performance indicators (KPIs) like
"98.5% availability" or "Full restoral to service in < 4 hrs" or "Maintenance window limited to a two
hour window once per month on second Saturday". 3.14.2.Performanceincludes UI and VM expected
performance. The cloud infrastructure and services must be able to meet the response time,
throughput and scaling requirements as defined by the service level agreements of the service
offering. The cloud infrastructure must provide manual and automated ways to optimize utilization in
the data center. Often measured by KPIs like "64 bit RHEL VM should be available within eight
minutes of user provisioning request" or "UI responsiveness should render catalog options within 5
seconds". 3.14.3.Scalabilityincludes number of concurrent users and number of number of managed
workloads and number of VMs per minute/hour. Scalability is the ability to expand the system
architecture to accommodate more users, more transactions and more data as users and data are
added. This should allow existing systems to be extended as far as possible without necessarily
having to replace them. Often measured in KPIs like "Needs to support 100 concurrent users" or
"Should have capacity to managed 10,000 RHEL VMs and 5,000 AIX LPARs" or "System should be able
to provision 100 RHEL VMs per/hour". 3.14.4.Consumabilityincludes UI usability, cloud infrastructure
install time and total cost of ownership. Consumability is a description of the customer's end-to-end
experience with the solution. The tasks associated with Consumability start before the consumer
purchases a service and continue until the customer stops using the product. By improving the
Consumability of the service, the value of that service to the client can be increased. Often quantified
as "UI should be intuitive for new users without formal training" or "Installation of cloud
infrastructure should require no more than 80 hours". 3.14.5.Extensibilityincludes 3rd party
integration, UI extensibility, application interfaces, and hypervisor support. The Cloud must be
extensible in order to address future functionality and changes without having to be rewritten,
support that the application may have access to additional disparate back-end systems, support the
ability to integrate with existing security systems either on-premise or elsewhere in clouds and be
able to add/remove/relocate physical and logical resources withoutdisturbing running services. Often
quantified as "Cloud infrastructure should interface with existing problem management system" or
"Cloud infrastructure should support Vmware, PowerVM, and HyperV" or "Self Service UI should be
invocable through RESTful APIs". 3.14.6.Securityincludes Command & Control, Identity, Access, and
Entitlement Management, Data and Information Protection Management, Software, System, and
Service Assurance, Threat and Vulnerability Management, Risk and Compliance Assessment and
Security Policy Management. Often driven by industry regulatory compliance. Often quantified as
"Must adhere to corporate standard XYZ" or "Provisioned VMs must receive monthly security
updates" or "Cloud infrastructure should ensure network isolation between tenant workloads".