Question : Which statement most accurately describes the relationship between MapReduce and Pig? 1. Pig programs rely on MapReduce but are extensible, allowing developers to do special-purpose processing not provided by MapReduce. 2. Pig provides no additional capabilities to MapReduce. Pig programs are executed as MapReduce jobs via the Pig interpreter. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Pig provides the additional capability of allowing you to control the flow of multiple MapReduce jobs.
Explanation: Pig is a framework that translates programs written in Pig Latin into jobs that are executed by the MapReduce framework. Pig does not provide any functionality that isn't provided by MapReduce, but it makes some types of data operations significantly easier to perform.
Question : You are working in Acmeshell Inc as an architect, and you have designed comlete BigData Software Architecture for this company and you asked your juniour team member to create Architecture Overview Document for this. As you are well qualified architect hence, you know, what to include and what not to include in this document and you found that following things are included in the Architecture Overview Document. Which all, you think are correct ?
Correct Answer : Get Lastest Questions and Answer : Explanation: The component model consists of the components, configurations, folders, and files to which you can map various design constructs of the software model. The component model illustrates the software components that will be used to build the system. These may be built up from the class model and written from scratch for the new system, or may be brought in from other projects and 3rd party vendors. Components are high level aggregations of smaller software pieces, and provide a 'black box' building block approach to software construction.
The Architecture Overview Diagram (AOD) provides overview of the fundamental architectural building blocks .It also defines architectural principles serving as a guideline for creating any environment.
In the RUP approach, the main artifact used to document the architecture of a software solution is called the Software Architecture Document (SAD). It is used to gather and communicate all of the architectural decisions made during the Elaboration phase. The SAD provides a comprehensive architectural overview of the system, using a number of different views to depict different aspects of the solution. It is intended to capture and convey the significant architectural decisions which have been made regarding the system.
In order to describe the software as accurately as possible, the structure of the SAD is based on the 4+1 view model of architecture
The SAD is nothing but a document you can create with your favorite text editor. But the design information comes from a modeling tool. Actually, if you have chosen to produce a RUP Software Architecture Document, you need to fill each section with the appropriate information, that is to say, with the appropriate UML diagrams from the UML model.
Question : You have been working on IBM cloude and you are quite comfortable with the services and support provided by IBM for their cloud solution. However, sometime some services fails and you ask IBM support to fix the same and they fix it perfectly. However, you need to give the SLA to your seniors about the service failure in cloud ? Which all you can find relatively easier and give in SLA
A. Root cause for service interruptions B. Turn-Around-Time (TAT) C. Mean Time To Recover (MTTR) D. First Call Resolution (FCR) E. Abandonment Rate
F. Average Speed to Answer (ASA) 1. A,B,C 2. B,C,D 3. Access Mostly Uused Products by 50000+ Subscribers 4. A,B,E 5. A,C,F Correct Answer : Get Lastest Questions and Answer : Explanation: It is very difficult to find the actula root cause of service failure in cloud, even it is fixed easily. Root-cause analysis is vital to the development and operation of cloud infrastructures. As more businesses move to public, private, or hybrid clouds, broad collaboration and the ability to connect with extended teams are vital. No longer is there a single set of people who provide the skills to restore service, ensure reliability, and maintain the infrastructure.
In the push to cloud adoption, problem management and root-cause analysis must be included. People expect cloud services to always be available and to improve continuously. Problem management can't be a part-time task; it's the driver to eliminate repeated issues. You must fix the right issue the first time, as repeated problems can lead to a loss of faith in the reliability of your application.
Identifying the root cause in a cloud environment Finding the root cause of on-premises issues might require being methodical in your search. But the cloud can make it difficult to easily detect root cause because the system is orchestrated to proactively resolve itself. A system might automatically migrate an application to another zone or restart something to prevent an outage. This automation means that root-cause analysis must be proactive instead of reactive.
Because the system is designed and monitored to not exceed the service level agreement thresholds, no alarms are raised. The only way to detect and identify root cause is through analytics, such as trending or anomaly detection. Problem management activities to support and maintain the cloud need strong collaboration across the system resources and developers to ensure that the right questions are followed by deep research and analysis before moving to the next Why.
Not all problems are worth solving. As incidents are the input to the root-cause analysis, you must prioritize and classify records to ensure focus. This focus on identifying and solving the right problems can have a positive impact on the availability and reliability of the overall cloud infrastructure.
Define a strong problem management strategy that focuses on increasing IT service availability while simultaneously increasing IT service quality and decreasing problems. When the right problems are identified, deliver the initial root-cause response in 24 hours and deliver the final findings within 5 days. By using this type of service level agreement, you ensure correct focus on problem activities and create a sense of urgency among the collaborating groups and resources.