Showing posts with label IT Officer Material. Show all posts
Showing posts with label IT Officer Material. Show all posts
Tuesday, 7 February 2017
Tuesday, 10 January 2017
IT Officer 300 Important Questions For IT Officer Exam
This is 300 Important questions for IT Officer Exam so learn these all questions.

Click Here to Download Now
Monday, 2 January 2017
SBI IT OFFICER 17 JAN 2016 EXAM ASKED TOPICS/QUESTIONS
1)Embedded SQL is Hard-coded SQL statements in a program language such as Java.
Embedded SQL is a method of inserting inline SQL statements or queries into the code of a programming language, which is known as a host language. Because the host language cannot parse SQL, the inserted SQL is parsed by an embedded SQL preprocessor.
Embedded SQL is a robust and convenient method of combining the computing power of a programming language with SQL's specialized data management and manipulation capabilities.
2)Which data mining technology is used to predict the future? Predictive
Predictive analytics encompasses a variety of statistical techniques from predictive modeling, machine learning, and data mining that analyze current and historical facts to make predictions about future or otherwise unknown events.
In business, predictive models exploit patterns found in historical and transactional data to identify risks and opportunities. Models capture relationships among many factors to allow assessment of risk or potential associated with a particular set of conditions, guiding decision making for candidate transactions.
|
|
Database mirroring is the creation and maintenance of redundant copies of a database. The purpose is to ensure continuous data availability and minimize or avoid downtime that might otherwise result from data corruption or loss, or from a situation when the operation of a network is partially compromised. Redundancy also ensures that at least one viable copy of a database will always remain accessible during system upgrades.
7) Which of the following is middle ware technology? CORBA
The Common Object Request Broker Architecture (CORBA) is a standard developed by the Object Management Group (OMG) to provide interoperability among distributed objects. CORBA is the world's leading middleware solution enabling the exchange of information, independent of hardware platforms, programming languages, and operating systems. CORBA is essentially a design specification for an Object Request Broker (ORB), where an ORB provides the mechanism required for distributed objects to communicate with one another, whether locally or on remote devices, written in different languages, or at different locations on a network.The CORBA Interface Definition Language, or IDL, allows the development of language and location-independent interfaces to distributed objects. Using CORBA, application components can communicate with one another no matter where they are located, or who has designed them. CORBA provides the location transparency to be able to execute these applications.CORBA is often described as a "software bus" because it is a software-based communications interface through which objects are located and accessed. The illustration below identifies the primary components seen within a CORBA implementation.
8)A group of servers, If one server is failed and its users are switched instantly to the other servers is called Cluster.
Microsoft Cluster Server (MSCS) is a computer program that allows server computers to work together as a computer cluster, to provide failover and increased availability of applications, or parallel calculating power in case of high-performance computing (HPC) clusters (as in supercomputing).
Microsoft has three technologies for clustering: Microsoft Cluster Service (MSCS, a HA clustering service), Component Load Balancing (CLB) (part of Application Center 2000), and Network Load Balancing Services (NLB). In Windows Server 2008 and Windows Server 2008 R2 the MSCS service has been renamed to Windows Server Failover Clustering and the Component Load Balancing (CLB) feature has been deprecated.
9)Conversion of message into a form,that cannot be easily understood by unauthorized people is called encryption.
Encryption is the conversion of electronic data into another form, called ciphertext, which cannot be easily understood by anyone except authorized parties.Network encryption (sometimes called network layer, or network level encryption) is a network security process that applies crypto services at the network transfer layer - above the data link level, but below the application level. The network transfer layers are layers 3 and 4 of the Open Systems Interconnection (OSI) reference model, the layers responsible for connectivity and routing between two end points. Using the existing network services and application software, network encryption is invisible to the end user and operates independently of any other encryption processes used. Data is encrypted only while in transit, existing as plaintext on the originating and receiving hosts.
10)Prototype model is a Systems Development Method (SDM)
The Prototyping Model is a systems development method (SDM) in which a prototype (an early approximation of a final system or product) is built, tested, and then reworked as necessary until an acceptable prototype is finally achieved from which the complete system or product can now be developed. This model works best in scenarios where not all of the project requirements are known in detail ahead of time. It is an iterative, trial-and-error process that takes place between the developers and the users.
Advantages of Prototype model:
- Users are actively involved in the development
- Since in this methodology a working model of the system is provided, the users get a better understanding of the system being developed.
- Errors can be detected much earlier.
- Quicker user feedback is available leading to better solutions.
- Missing functionality can be identified easily
- Confusing or difficult functions can be identified
Requirements validation, Quick implementation of, incomplete, but
functional, application.
Disadvantages of Prototype model:
- Leads to implementing and then repairing way of building systems.
- Practically, this methodology may increase the complexity of the system as scope of the system may expand beyond original plans.
- Incomplete application may cause application not to be used as the
full system was designed
Incomplete or inadequate problem analysis.
11) COM stands for Component Object Model
COM is a platform-independent, distributed, object-oriented system for creating binary software components that can interact. COM is the foundation technology for Microsoft's OLE (compound documents) and ActiveX (Internet-enabled components) technologies.COM objects can be created with a variety of programming languages. Object-oriented languages, such as C++, provide programming mechanisms that simplify the implementation of COM objects. These objects can be within a single process, in other processes, even on remote computers.
12) Term used in networks which has header and trailer – Packet
A data packet consists of three elements. The first element is a header, which contains the information needed to get the packet from the source to the destination, and the second element is a data area, which contains the information of the user who caused the creation of the packet. The third element of packet is a trailer, which often contains techniques ensuring that errors do not occur during transmission.During communication of data the sender appends the header and passes it to the lower layer while the receiver removes header and passes it to upper layer. Headers are added at layer 6,5,4,3 & 2 while Trailer is added at layer 2.
13) Project Management Tools. A Gantt chart, Logic Network, PERT chart, Product Breakdown Structure and Work Breakdown Structure are standard tools used in project planning.
The program (or project) evaluation and review technique, commonly abbreviated PERT, is a statistical mathematics tool, used in General project management, which was designed to analyze and represent the tasks involved in completing a given project.A Gantt chart, commonly used in project management, is one of the most popular and useful ways of showing activities (tasks or events) displayed against time. On the left of the chart is a list of the activities and along the top is a suitable time scale. Each activity is represented by a bar; the position and length of the bar reflects the start date, duration and end date of the activity.
14) A network operating system (NOS) is a computer operating system system that is designed primarily to support workstation, personal computer, and, in some instances, older terminal that are connected on a local area network (LAN). Artisoft's LANtastic, Banyan VINES, Novell's NetWare, and Microsoft's LAN Manager are examples of network operating systems. In addition, some multi-purpose operating systems, such as Windows NT and Digital's OpenVMS come with capabilities that enable them to be described as a network operating system.A network operating system provides printer sharing, common file system and database sharing, application sharing, and the ability to manage a network name directory, security, and other housekeeping aspects of a network.
15) If you are on an Intranet, when you can’t access internet then what will you check? Proxy settings
A proxy or proxy server is basically another computer which serves as a hub through which internet requests are processed. By connecting through one of these servers, your computer sends your requests to the proxy server which then processes your request and returns what you were wanting. In this way it serves as an intermediary between your home machine and the rest of the computers on the internet. Proxies are used for a number of reasons such as to filter web content, to go around restrictions such as parental blocks, to screen downloads and uploads and to provide anonymity when surfing the internet.
Wednesday, 21 December 2016
1000 Questions IT Officer Ebook Video
Videos For 10 MCQ from IT officer Ebook........In this video i explain the 10 questions and elaborate the level of ebook.........So Download Now to Learn all 1000 Questions.........Link provided in Video description and also on my website.........
Sunday, 18 December 2016
IT OFFICER EBOOK(1000 QUESTIONS)
DOWNLOAD NOW IT OFFICER EXAM EBOOK
(1000 QUESTIONS)
In this ebook ,1000 important questions given of following topics:
1)DBMS
2)ORACLE
3)COMPUTER NETWORKS
4)SOFTWARE ENGINEERING
5)OPERATING SYSTEM
6)WEB TECHNOLOGY
7)C/C++
8)COMPUTER FUNDAMENTAL
9)DATA STRUCTURE
These all questions are very important and must read before it officer exam.
Wednesday, 14 December 2016
Software Engineering Notes Part-1
Software Engineering is an engineering approach for software development.The basic principle of software engineering is to use structured, formal and disciplined methods for building and using systems.The outcome of software engineering is an efficient and reliable software product.
Without using software engineering principles it would be difficult to develop large programs. In industry it is usually needed to develop large programs to accommodate multiple functions. A problem with developing such large commercial programs is that the complexity and difficulty levels of the programs increase exponentially with their sizes. Software engineering helps to reduce this programming complexity. Software engineering principles use two important techniques to reduce problem complexity: abstraction and decomposition. The principle of abstraction implies that a problem can be simplified by omitting irrelevant details. In other words, the main purpose of abstraction is to consider only those aspects of the problem that are relevant for certain purpose and suppress other aspects that are not relevant for the given purpose. Once the simpler problem is solved, then the omitted details can be taken into consideration to solve the next lower level abstraction, and so on. Abstraction is a powerful way of reducing the complexity of the problem.
The other approach to tackle problem complexity is decomposition. In this technique, a complex problem is divided into several smaller problems and then the smaller problems are solved one by one. However, in this technique any random decomposition of a problem into smaller parts will not help. The problem has to be decomposed such that each component of the decomposed problem can be solved independently and then the solution of the different components can be combined to get the full solution. A good decomposition of a problem should minimize interactions among various components.
System Requirement Specification(SRS):
It is obtained after excessive discussions with the users.Software requirement specification (SRS) is a document that completely describes what the proposed software should do without describing how software will do it.SRS is important and difficult task of a System Analyst.
Characteristics of SRS:
Without using software engineering principles it would be difficult to develop large programs. In industry it is usually needed to develop large programs to accommodate multiple functions. A problem with developing such large commercial programs is that the complexity and difficulty levels of the programs increase exponentially with their sizes. Software engineering helps to reduce this programming complexity. Software engineering principles use two important techniques to reduce problem complexity: abstraction and decomposition. The principle of abstraction implies that a problem can be simplified by omitting irrelevant details. In other words, the main purpose of abstraction is to consider only those aspects of the problem that are relevant for certain purpose and suppress other aspects that are not relevant for the given purpose. Once the simpler problem is solved, then the omitted details can be taken into consideration to solve the next lower level abstraction, and so on. Abstraction is a powerful way of reducing the complexity of the problem.
The other approach to tackle problem complexity is decomposition. In this technique, a complex problem is divided into several smaller problems and then the smaller problems are solved one by one. However, in this technique any random decomposition of a problem into smaller parts will not help. The problem has to be decomposed such that each component of the decomposed problem can be solved independently and then the solution of the different components can be combined to get the full solution. A good decomposition of a problem should minimize interactions among various components.
System Requirement Specification(SRS):
It is obtained after excessive discussions with the users.Software requirement specification (SRS) is a document that completely describes what the proposed software should do without describing how software will do it.SRS is important and difficult task of a System Analyst.
Characteristics of SRS:
- Correct
- Complete and Unambiguous
- Verifiable
- Consistent
- Traceable
- Modifiable
Software Life Cycle Models:
A software life cycle model (also called process model) is a descriptive and diagrammatic representation of the software life cycle. A life cycle model represents all the activities required to make a software product transit through its life cycle phases. It also captures the order in which these activities are to be undertaken. In other words, a life cycle model maps the different activities performed on a software product from its inception to retirement. Different life cycle models may map the basic development activities to phases in different ways. Thus, no matter which life cycle model is followed, the basic activities are included in all life cycle models though the activities may be carried out in different orders in different life cycle models. During any life cycle phase, more than one activity may also be carried out. A software life cycle model is a particular abstraction representing a software life cycle.Such a model may be:
Activity-centered----Focusing on the activities of software development
Entity-centered----Focusing on the work products created by these activities
A software life cycle model is often referred to as a Software Development Life Cycle(SDLC).ISO/IEC 12207 is an international standard for software life-cycle processes. It aims to be the standard that defines all the tasks required for developing and maintaining software.
Waterfall Model:
The Waterfall Model was first Process Model to be introduced.
The waterfall Model is a linear sequential flow. In which progress is seen as flowing steadily downwards (like a waterfall) through the phases of software implementation. This means that any phase in the development process begins only if the previous phase is complete. The waterfall approach does not define the process to go back to the previous phase to handle changes in requirement. The waterfall approach is the earliest approach that was used for software development.
Requirement Gathering and Analysis
|
Capture all the possible requirement of the system to be
developed and documented in a software requirement.
|
System Design
|
Helps in specifying hardware and system requirements and
also helps in defining overall system architecture.
|
Implementation
|
With inputs from system design, the system is first
developed in small programs called units, which are integrated in the next
phase. Each unit is developed and tested for its functionality which is
referred to as Unit Testing.
|
Integration and Testing
|
All the units developed in the implementation phase are
integrated into a system after testing of each unit. During this phase, each module
is unit tested to determine the correct working of all the individual
modules. It involves testing each module in isolation as this is the most
efficient way to debug the errors identified at this stage.
|
Integration and System Testing
|
During the integration
and system testing
phase, the modules
are integrated in a planned manner. The different modules making up a
software product are almost never integrated in one shot. Integration is
normally carried out incrementally over a number ofsteps. During each
integration step, the
partially integrated system
is tested and
a set of previously planned modules are added to
it. Finally, when all the modules have been successfully integrated and
tested, system testing is carried out.
The goal of system testing is to ensure that the developed system conforms to
its requirements laid out in the SRS document. System testing
usually consists of three different kinds of testing
activities:
α – testing: It is the system testing performed by the
development team.
β –testing: It is the system testing performed by a friendly
set of customers.
Acceptance testing: It is the system testing performed by the
customer himself after the product delivery to determine whether to accept or
reject the delivered product.
|
Deployment of System
|
Once the
functional and non functional testing is done, the product is deployed in the
customer environment or released into the market.
|
Maintenance
|
Maintenance of a typical software product requires much more
than the effort necessary to
develop the product
itself. Many studies
carried out in
the past confirm
this and indicate that the
relative effort of development of a typical software product to its maintenance
effort is roughly in the 40:60 ratios.
Maintenance involves performing any one or more of the following three kinds
of activities:
Correcting errors that were not discovered during the product
development phase. This is called corrective maintenance.
Improving the implementation of
the system, and
enhancing the functionalities of
the system according to the customer’s requirements. This is called
perfective maintenance.
Porting the software
to work in
a new environment. For
example, porting may
be required to get the software to work on a new computer platform or
with a new operating system. This is called adaptive maintenance.
|
Advantages of waterfall model:
- This model is simple and easy to understand and use.
- It is easy to manage due to the rigidity of the model – each phase has specific deliverables and a review process.
- In this model phases are processed and completed one at a time. Phases do not overlap.
- Waterfall model works well for smaller projects where requirements are very well understood.
Disadvantages of waterfall model:
- Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage.
- No working software is produced until late during the life cycle.
- High amounts of risk and uncertainty.
- Not a good model for complex and object-oriented projects.
- Poor model for long and ongoing projects.
- Not suitable for the projects where requirements are at a moderate to high risk of changing.
When to use the waterfall model:
- This model is used only when the requirements are very well known, clear and fixed.
- Product definition is stable.
- Technology is understood.
- There are no ambiguous requirements
- Ample resources with required expertise are available freely
- The project is short.
Very less customer enter action is involved during the development of the product. Once the product is ready then only it can be demoed to the end users. Once the product is developed and if any failure occurs then the cost of fixing such issues are very high, because we need to update everywhere from document till the logic.
Monday, 12 December 2016
Snapshot in Oracle Key Points.........
A snapshot is a recent copy of a table from db or in some cases, a subset of rows/cols of a table. They are used to dynamically replicate the data between distributed databases.
Snapshot connected to a Single Master Site:
Snapshot connected to a Single Master Site:
Snapshots can also contain a WHERE clause so that snapshot sites can contain customized data sets. Such snapshots can be helpful for regional offices or sales forces that do not require the complete corporate data set.When a snapshot is refreshed, Oracle must examine all of the changes to the master table to see if any apply to the snapshot. Therefore, if any changes where made to the master table since the last refresh, a snapshot refresh will take some time, even if the refresh does not apply any changes to the snapshot. If, however, no changes at all were made to the master table since the last refresh of a snapshot, the snapshot refresh should be very quick.
Snapshot and materialized view are almost same same but with one difference.
You can say that materialized view =snapshot + query rewrite functionality query rewrite functionality:In materialized view you can enable or disable query rewrite option. which means database server will rewrite the query so as to give high performance. Query rewrite is based on some rewritten standards(by oracle itself).So the database server will follow these standards and rewrite the query written in the materialized view ,but this functionality is not there in snapshots.
You can say that materialized view =snapshot + query rewrite functionality query rewrite functionality:In materialized view you can enable or disable query rewrite option. which means database server will rewrite the query so as to give high performance. Query rewrite is based on some rewritten standards(by oracle itself).So the database server will follow these standards and rewrite the query written in the materialized view ,but this functionality is not there in snapshots.
Simple snapshots are the only type that can use the FAST REFRESH method. A snapshot is considered simple if the defining query meets the following criteria:
- It does not contain any DISTINCT or aggregation functions.
- It does not contain a GROUP BY or CONNECT BY clause.
- It does not perform set operations (UNION, UNION ALL, INTERSECT, etc.).
- It does not perform joins other than those used for subquery subsetting.
- Essentially, a simple snapshot is one that selects from a single table and that may or may not use a WHERE clause.
Note
Oracle8 extends the universe of simple snapshots with a feature known as subquery subsetting, described in the later section entitled “Subquery Subsetting.”
Not surprisingly, any snapshot that is not a simple snapshot is a complex snapshot. Complex snapshots can only use COMPLETE refreshes, which are not always practical. For tables of more than about 100,000 rows, COMPLETE refreshes can be quite unwieldy.You can often avoid this situation by creating simple snapshots of individual tables at the master site and performing the offending query against the local snapshots.
Subscribe to:
Posts (Atom)


