IBM Certified Data Architect - Big Data Certification Questions and Answers (Dumps and Practice Questions)
Question : You are working as an infrastructure architect for Acmeshell Inc. And one of the solution architect asked you to create infrastructure for the Hadoop File System and
told hos requirement. Now, while choosing the storage , you have to option either DAS or SAN based storage. And you come to the conclusion that, you can use SAN for this
requirement why ?
1. SAN storage is must faster than DAS
2. SAN is always easy to manage , compare to DAS.
3. Access Mostly Uused Products by 50000+ Subscribers
4. SAN storage supports replication
Correct Answer : Get Lastest Questions and Answer :
Explanation: In a DAS configuration, storage array ports are linked directly to servers, whereas in a SAN a switched network infrastructure exists between storage and
the servers. The major advantages of using a SAN are increased flexibility and scalability. SANs allow multiple hosts to access disk storage within a single array through a single
port, thereby reducing waste and increasing return on investment.
Typically, intelligent disk storage arrays are used in SAN environments. SAN-attached intelligent disk arrays offer additional functionality, including local replication and
remote replication, snapshots, data deduplication and storage virtualization, and are highly resilient to failure of a single component.
SAN Storage Area Network
A storage area network is a dedicated, high-performance storage system that transfers block-level data between servers and storage devices. SAN is typically used in data centers,
enterprises or virtual computing environments. It offers the speed of DAS with the sharing, flexibility and reliability of NAS. SAN storage is a very sophisticated option thats
meant to support complex, mission-critical applications.
Best Use Case Scenario: SAN is best for block-level data sharing of mission- critical files or applications at data centers or large-scale enterprise organizations.
Worst Use Case Scenario: SAN is an expensive and sophisticated solution thats typically reserved for serious computing needs. A small-to-midsize organization with a limited
budget and few IT staff or resources likely wouldnt need SAN.
Question : To create High Availability solution, in Hadoop installation. You have to have two separate high end machines are required for which of the following ?
1. Data Node
2. NameNode
3. Access Mostly Uused Products by 50000+ Subscribers
4. Both 1 and 3
Correct Answer : Get Lastest Questions and Answer :
Explanation: The NameNode in Hadoop is the node where Hadoop stores all the location information of the files in HDFS. In other words, it holds the metadata for HDFS.
Whenever a file is placed in the cluster a corresponding entry of it location is maintained by the NameNode.
Question : A service-level agreement is an agreement between two or more parties, where one is the customer and the others are service providers. This can be a legally binding
formal or an informal "contract" (for example, internal department relationships). The agreement may involve separate organizations, or different teams within one organization.
Contracts between the service provider and other third parties are often (incorrectly) called SLAs because the level of service has been set by the (principal) customer, there
can be no "agreement" between third parties; these agreements are simply "contracts." Service level agreements are also defined at different levels, which all are correct levels
A. Customer-based SLA
B. Service-based SLA
C. Multilevel SLA
D. Third-party SLA
1. A,B,C
2. B,C,D
3. Access Mostly Uused Products by 50000+ Subscribers
4. A,B,C,D
Correct Answer : Get Lastest Questions and Answer :
Explanation: A service-level agreement is an agreement between two or more parties, where one is the customer and the others are service providers. This can be a
legally binding formal or an informal "contract" (for example, internal department relationships). The agreement may involve separate organizations, or different teams within one
organization. Contracts between the service provider and other third parties are often (incorrectly) called SLAs because the level of service has been set by the (principal)
customer, there can be no "agreement" between third parties; these agreements are simply "contracts." Operational-level agreements or OLAs, however, may be used by internal groups
to support SLAs. If some aspect of a service has not been agreed with the customer, it is not an "SLA".
SLAs commonly include many components, from a definition of services to the termination of agreement.[2] To ensure that SLAs are consistently met, these agreements are often
designed with specific lines of demarcation and the parties involved are required to meet regularly to create an open forum for communication. Rewards and penalties applying to
the provider are often specified. Most SLAs also leave room for periodic (annual) revisitation to make changes.[3]
Since late 1980s SLA's have been used by fixed line telecom operators. SLAs are so widely used these days that larger organizations have many different SLAs existing within the
company itself. Two different units in an organization script a SLA with one unit being the customer and another being the service provider. This practice helps to maintain the
same quality of service amongst different units in the organization and also across multiple locations of the organization. This internal scripting of SLA also helps to compare
the quality of service between an in-house department and an external service provider.[4]
The output received by the customer as a result of the service provided is the main focus of the service level agreement.
Service level agreements are also defined at different levels:
Customer-based SLA: An agreement with an individual customer group, covering all the services they use. For example, an SLA between a supplier (IT service provider) and the
finance department of a large organization for the services such as finance system, payroll system, billing system, procurement/purchase system, etc.
Service-based SLA: An agreement for all customers using the services being delivered by the service provider. For example:
A mobile service provider offers a routine service to all the customers and offers certain maintenance as a part of an offer with the universal charging.
An email system for the entire organization. There are chances of difficulties arising in this type of SLA as level of the services being offered may vary for different customers
(for example, head office staff may use high-speed LAN connections while local offices may have to use a lower speed leased line).
Multilevel SLA: The SLA is split into the different levels, each addressing different set of customers for the same services, in the same SLA.
Corporate-level SLA: Covering all the generic service level management (often abbreviated as SLM) issues appropriate to every customer throughout the organization. These
issues are likely to be less volatile and so updates (SLA reviews) are less frequently required.
Customer-level SLA: covering all SLM issues relevant to the particular customer group, regardless of the services being used.
Service-level SLA: covering all SLM issue relevant to the specific services, in relation to this specific customer group.
Related Questions
Question : You are working in an organization, which provide data storage solutions for many companies and government. However, their are various types of data , which of the
following approach can help to solve the impact on performance data and capacity
1. Define a data catalog in a traditional data warehouse
2. Create different solutions to handle every kind of data
3. Store a wide range of data formats on the same platform
4. Define a comprehensive taxonomy and constantly review
Question : Which of the following is a browser based virtualization tool?
1. BigR
2. BigSheets
3. Analytics Workbench
4. Watson Explorer
Question : You are working in a Financial Risk Analytics company, where you have last years of history data, which is stored in TeraData data warehouse system and underline
storage is very costly. Hence, you decided to move this data to Hadoop commodity hardware for historical data and for ongoing data they will still use Teradata and uses federation
method to
access both sets of data. which of the following Big Data value proposition for this use case?
1. IBM Logical Data Warehouse and IBM Big SQL
2. Enterprise Data Warehouse
3. Pure Data for Analytics
4. InfoSphere Information Server
Question : Which of the following statements is TRUE regarding IAAS vs PAAS?
1. Performance and scalability requirements are a critical factor for deciding between Platform as a Service and Infrastructure as a Service deployment models
2. In PAAS, you will be getting Root access to the operating system.
3. If your web application has a very high transactions volumes are good candidates for Platform as a Service
4. In an infrastructure as a service deployment, the cloud provider provides security patching, monitoring and fail over capabilities
Question : You are an enterprise architect of ARINIKA Inc. You have after every days there will be a big spike of new data with multiple TB. And regulations says data
older than one year needs to be archived older than 3 years data needs to be removed. Which of the following is a best solution as well as low cost.
1. Estimate the peak volume over a 3 year period and set up a Hadoop system with commodity HW and storage to accommodate that volume.
2. Estimate the peak volume over a 3 year period and set up a Hadoop system with NAS to accommodate the expected volume
3. Use Cloud elasticity capabilities to handle the peak and valley data volume
4. Use SAN storage with compression to handle the peak and valley data volume
Question : SAN or NAS should not be used to set up HDFS
1. True
2. False