{"id":12535,"date":"2019-12-17T15:24:17","date_gmt":"2019-12-17T09:54:17","guid":{"rendered":"https:\/\/kseebsolutions.guru\/?p=12535"},"modified":"2021-07-02T15:36:30","modified_gmt":"2021-07-02T10:06:30","slug":"2nd-puc-computer-science-question-bank-chapter-13","status":"publish","type":"post","link":"https:\/\/kseebsolutions.guru\/2nd-puc-computer-science-question-bank-chapter-13\/","title":{"rendered":"2nd PUC Computer Science Question Bank Chapter 13 Data Concepts"},"content":{"rendered":"

You can Download Chapter 13 Data Concepts Questions and Answers, Notes, 2nd PUC Computer Science Question Bank with Answers<\/a> Karnataka State Board Solutions help you to revise complete Syllabus and score more marks in your examinations.<\/p>\n

Karnataka 2nd PUC Computer Science Question Bank Chapter 13 Data Concepts<\/h2>\n

2nd PUC Computer Science Data Concepts One Mark Questions and Answers<\/h3>\n

Question 1.
\nWhat is data?
\nAnswer:
\nData is a collection of facts, figures or statistics. Data is transformed into meaningful information. It is raw material of information.<\/p>\n

Question 2.
\nWhat is information?
\nAnswer:
\nIt is processed data with definite meaning. Information gives meaning.<\/p>\n

Question 3.
\nWhat is the database?
\nAnswer:
\nA database is a collection of large amounts of related data. In other words, It is a collection of database tables.<\/p>\n

Question 4.
\nWhat is the field?
\nAnswer:
\nEach column in a table is identified by a distinct header is called a field.<\/p>\n

\"KSEEB<\/p>\n

Question 5.
\nWhat is a record?
\nAnswer:
\nCollection of related fields (eg- Name, Age, register number, marks)<\/p>\n

Question 6.
\nWhat is an entity?
\nAnswer:
\nAn entity is a person,place, thing or event for which data is collected and maintained.<\/p>\n

Question 7.
\nWhat is an instance?
\nAnswer:
\nEach row of a table is called entity instance.<\/p>\n

Question 8.
\nWhat is an attribute?
\nAnswer:
\nAn attribute is the characteristic property of an existing entity.<\/p>\n

Question 9.
\nWhat is domain?
\nAnswer:
\nA domain describes the set of possible values for a given attribute.<\/p>\n

Question 10.
\nWhat is a relation?
\nAnswer:<\/p>\n

    \n
  • A relation is defined as a set of tuples that have the same attributes.<\/li>\n
  • A relation is usually described as a table, which is organized into rows and columns.<\/li>\n<\/ul>\n

    Question 11.
    \nWhat is a table?
    \nAnswer:
    \nA table is a collection of data elements organised in terms of rows and columns.<\/p>\n

    Question 12.
    \nWhat is normalization?
    \nAnswer:
    \nNormalization is the process of reorganizing data in a database by eliminating duplication and ensuring data dependencies.<\/p>\n

    \"KSEEB<\/p>\n

    Question 13.
    \nWhat is a key?
    \nAnswer:
    \nIt is a field in table that uniquely identifies a record (e.g. Register number of a student).<\/p>\n

    Question 14.
    \nGive the symbol notion for project.
    \nAnswer:
    \nThe symbol notion for project is \u00f0 (pi)<\/p>\n

    Question 15.
    \nWhat is data mining?
    \nAnswer:
    \nIt is the process of discovering interesting knowledge, such as patterns, associations, changes, anomalies from large amounts of data stored in databases.<\/p>\n

    2nd PUC Computer Science Data Concepts Two Mark Questions and Answers<\/h3>\n

    Question 1.
    \nHow database helps us?
    \nAnswer:
    \nA database is a collection of logically related data organized in a way that data can be easily accessed, managed and updated. In colleges, student admission details, fee payment details (annual, monthly, late payment), statement of marks etc., can be maintained and various reports can be generated time to time.<\/p>\n

    Question 2.
    \nHow do we get data?
    \nAnswer:
    \nData means collected facts, figures and statistics. The data may be in the form of letter, symbols, numbers, images, videos and sound. It can be collected from various sources inside and outside of an organization or any part of universe.<\/p>\n

    Question 3.
    \nName the data types supported by DBMS?
    \nAnswer:
    \nThe various data types supported by DBMS are integer, single’precision, double precision, character, string, memo, index, currency; date and text fields.<\/p>\n

    \"KSEEB<\/p>\n

    Question 4.
    \nWhat is generalization?
    \nAnswer:
    \nGeneralization is the process of taking the union of two or more lower level entity sets to produce a higher-level entity sets. Generalization is a bottom-up approach. For example,
    \nentities savings account and a current account can be generalized to accounts.<\/p>\n

    Question 5.
    \nWhat is specialization?
    \nAnswer:
    \nIt is a top-down approach in which one higher-level entity can be broken down into two lower level entities. For example, entity accounts can be broken down into savings account and current account.<\/p>\n

    Question 6.
    \nWhat is the difference between serial and direct access file organization?
    \nAnswer:<\/p>\n

      \n
    • In sequential access data is stored at random locations.<\/li>\n
    • In direct access data is stored at sequential locations.<\/li>\n
    • Data structure implementing Sequential access is linked list.<\/li>\n
    • Data structure implementing Direct access is an Array.<\/li>\n<\/ul>\n

      Question 7.
      \nGive the advantages of disadvantages of index sequential access method.
      \nAnswer:
      \nThe advantages of disadvantages of index sequential access method are
      \nAdvantages:<\/p>\n

        \n
      • It combines both sequential and direct<\/li>\n
      • Suitable for sequential access and random access<\/li>\n
      • Provides quick access to records<\/li>\n<\/ul>\n

        Disadvantages:<\/p>\n

          \n
        • It uses special software and is expensive<\/li>\n
        • Extra time is taken to maintain index<\/li>\n
        • Extra storage for index files<\/li>\n
        • Expensive hardware is required<\/li>\n<\/ul>\n

          Question 8.
          \nClassify various types of keys used in database.
          \nAnswer:
          \nThe various types of keys used in database are candidate key, primary key, secondary key, super key and foreign key.<\/p>\n

          Question 9.
          \nWhat is relation algebra?
          \nAnswer:
          \nRelational algebra is a formal system for manipulating relations. Operands of this algebra are relations (a set of tuples). Operations of this algebra include the usual set operations, and special operations defined Tor relations.<\/p>\n

          Question 10.
          \nGive an example for relation selection with example.
          \nAnswer:
          \nSelection:
          \nSelects tuples from a relation whose attributes meet the selection criteria, which is normally expressed as a predicate. For example, find all employees born after 14th<\/sup> February 2000.<\/p>\n

          \"KSEEB<\/p>\n

          Question 11.
          \nWhat is Cartesian product?
          \nAnswer:
          \nThe Cartesian Product is also an operator that works on two sets. It is sometimes called the CROSS PRODUCT or CROSS JOIN. It combines the tuples of one relation with all the tuples of the other relation.<\/p>\n

          Question 12.
          \nWhat is join operation?
          \nAnswer:
          \nJOIN is used to combine related tuples from two relations i.e., combines attributes of two relations into one. In its simplest form, the JOIN operator is just the cross product of the two relations.<\/p>\n

          Question 13.
          \nWhat is data warehouse?
          \nAnswer:
          \nA data warehouse (DW) is a database used for reporting. The data is offloaded from the operational systems for reporting.<\/p>\n

          Question 14.
          \nWhat is data mining?
          \nAnswer:
          \nIt is the process of discovering interesting knowledge, such as patterns, associations, changes, anomalies from large amounts of data stored in databases using pattern recognition technologies as well as statistical and mathematical techniques.<\/p>\n

          2nd PUC Computer Science Data Concepts Three Mark Questions and Answers<\/h3>\n

          Question 1.
          \nMention the applications of database.
          \nAnswer:
          \nThe applications of database are banking, water meter billing, rail and airlines, colleges, credit card transactions, telecommunication, finance\/sales, manufacturing and human resources.<\/p>\n

          \"KSEEB<\/p>\n

          Question 2.
          \nGive the difference between manual and electronic file systems.
          \nAnswer:
          \nThe difference between manual and electronic file systems.<\/p>\n\n\n\n\n\n\n\n\n\n
          Manual File System<\/td>\nElectronic File System<\/td>\n<\/tr>\n
          1) Process limited volume of data<\/td>\n1) process a large volume of data<\/td>\n<\/tr>\n
          2) uses paper to store data<\/td>\n2) use of mass storage devices in computer itself<\/td>\n<\/tr>\n
          3) the speed and accuracy is less<\/td>\n3) more speed and greater accuracy<\/td>\n<\/tr>\n
          4) cost of processing is high since more human-oriented<\/td>\n4) cost of processing less because computer performs repetitive task<\/td>\n<\/tr>\n
          5) occupies more space<\/td>\n5) little space is sufficient<\/td>\n<\/tr>\n
          6) Repetitive tasks reduces efficiency and human feel bore and tiredness<\/td>\n6) Efficiency is maintained throughout and won’t feel bore and tiredness.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

          Question 3.
          \nExplain Boyce and Codd form (BCNF).
          \nAnswer:
          \nBoyce and Codd form (BCNF):<\/p>\n

            \n
          • When a relation has more than one candidate key, anomalies may result even though the relation is in 3NF.<\/li>\n
          • 3NF does not deal satisfactorily with the case of a relation with overlapping candidate keys<\/li>\n
          • BCNF is based on the concept of a determinant.<\/li>\n
          • A determinant is any attribute on which some other attribute is fully functionally dependent. .<\/li>\n
          • A relation is in BCNF is, and only if, every determinant is a candidate key.<\/li>\n<\/ul>\n

            Examples: Conisder a database table that stores employee information and has the attributes employee_id, first_name, last_name title. In this table, the field employee_id determines first_name and last_name. Similarly, the tuple ( first_name, last_name ) determines employee_id.<\/p>\n

            Question 4.
            \nGive the different notations for E-R Diagram.
            \nAnswer:
            \nthe different notations for E-R Diagram
            \n\"2nd<\/p>\n

            Question 5.
            \nExplain any three components of the E-R diagram.
            \nAnswer:
            \nThe three main components of the E-R diagram are Entity, Attribute and Relationship.<\/p>\n

            \"KSEEB<\/p>\n

            Question 6.
            \nWhat is the relationship? Classify and give an example.
            \nAnswer:
            \nA relationship is defined as “an association among entities”. A relationship describe relations between entities and represented using diamond symbol in E-R diagram. There are three types of relationship namely binary relationship, unary relationship and ternary relationship.<\/p>\n

            1. Binary relationship:
            \nA Binary relationship is the one that links two entities sets e.g. STUDENT-CLASS.<\/p>\n

            2. Unary Relationship:
            \nAn ENTITY TYPE linked with itself also called recursive relationship. Example, Roommate, ‘ where STUDENT is linked with STUDENT<\/p>\n

            3. Ternary Relationship:
            \nA Ternary relationship is the one that involves three entities e.g. STUDENT-CLASS-FACULTY.<\/p>\n

            Question 7.
            \nExplain Chen’s style and Martin’s style of relation.
            \nAnswer:
            \nCardinality specifies how many instances of an entity relate to one instance of another entity i.e., it specifies the occurrences of relationship and also specifies the maximum number of relationships.
            \nThe cardinality notation can be shown using Information Engineering style, Bachman style, Chen style and Martin style.<\/p>\n\n\n\n\n\n\n
            Chen Style<\/td>\n<\/tr>\n
            One to zero or more<\/td>\n1:N (n=0,1,2,3..)<\/td>\n<\/tr>\n
            Zero or more to zero or more<\/td>\nM : N (m and n=0,l,2,3…)<\/td>\n<\/tr>\n
            One to one.<\/td>\n1:1<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n\n\n\n\n\n\n
            Martin Style<\/td>\n<\/tr>\n
            One, and only one (mandatory)<\/td>\n1<\/td>\n<\/tr>\n
            Many (zero or more (optional)<\/td>\n* *<\/td>\n<\/tr>\n
            One or more (mandatory)<\/td>\n1.:.*<\/td>\n<\/tr>\n
            Zero or one (optional)<\/td>\n0….1<\/td>\n<\/tr>\n
            Zero or one (optional)<\/td>\n(0,1)<\/td>\n<\/tr>\n
            C.,e or more (mandatory)<\/td>\n(l,n)<\/td>\n<\/tr>\n
            Zero or more (optional)<\/td>\n(0,n)<\/td>\n<\/tr>\n
            One and only one (mandatory)<\/td>\n(1,1)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            Question 8.
            \nExplain physical data independence.
            \nAnswer:
            \nApplication programs must remain unchanged when any changes are made in storage representation or access methods. All schemas are logical and actual date is stored in bit format on the disk. Physical data independence is the power to change the physical data without impacting the schema or logical data.<\/p>\n

            For example, in case we want to change or upgrade the storage system itself, that is, using SSD instead of Hard-disks should not have any impact on logical data or schemas.<\/p>\n

            \"KSEEB<\/p>\n

            Question 9.
            \nExplain ISAM with example.
            \nAnswer:
            \nThis method combines both the feature of the sequential and random organizations. Records are accessed by using an index or a table. The index stores the address of each record corresponding to key number of the record. The records within the file are stored sequentially but directly accessed to individual records.
            \nA indexed sequential access method (ISAM) consists of<\/p>\n

              \n
            • The main file storage<\/li>\n
            • A table to maintain the index<\/li>\n<\/ul>\n

              An example is illustrated. Using this table (or index, directory), we can find out the address of any record, given the key value. For example, the record with key equal to ‘00120’ has the address “1”.
              \n\"2nd<\/p>\n

              Question 10.
              \nExplain database users.
              \nAnswer:
              \nThere are different types of database users. They are
              \n1. Application programmers or Ordinary users:
              \nThese users write application programs to interact with the database. Application programs can be written in some programming language typically a SQL statement to DBMS.<\/p>\n

              2. End Users:
              \nEnd users are the users, who use the applications developed. They just use the system to get their task done. End users are of two types:<\/p>\n

                \n
              • Direct users<\/li>\n
              • Indirect users<\/li>\n<\/ul>\n

                3. Database Administrator (DBA):
                \nDatabase Administrator (DBA) is the person which makes the strategic and policy decisions regarding the data of the enterprise, DBA is responsible for overall control of the system at a technical level.<\/p>\n

                4. System Analyst:
                \nSystem Analyst determines the requirement of end-users, and develops specifications for transactions that meet these requirements. System Analyst plays a major role in database design, technical aspect etc. of the system.<\/p>\n

                Question 11.
                \nExplain the hierarchical data model.
                \nAnswer:
                \nThe Hierarchical Data Model is created by IBM. It is a way of organizing a database with multiple one to many relationships. The structure is based on the rule that one parent can have many children but children are allowed only one parent.
                \nAdvantages:<\/p>\n

                  \n
                • allows easy addition and deletion of new information.<\/li>\n
                • Data at the top of the Hierarchy is very fast to access.<\/li>\n
                • It relates well to anything that works through a one to many relationships.<\/li>\n<\/ul>\n

                  Disadvantages:<\/p>\n

                    \n
                  • It requires data to be repetitively stored in many different entities.<\/li>\n
                  • The database can be very slow when searching for information on the lower entities.<\/li>\n
                  • Searching for data requires the DBMS to run through the entire model, making queries very slow. Can only model<\/li>\n<\/ul>\n

                    one to many relationships, many to many relationships are not supported.<\/p>\n

                    \"KSEEB<\/p>\n

                    Question 12.
                    \nExplain the relational data model.
                    \nAnswer:
                    \nRelational Database Model:
                    \nDr. E.F.Codd first introduced the Relational Database Model in 1970. This model allows data to be represented in a ‘simple row-column format’.<\/p>\n

                    Properties of the relational database model:<\/p>\n

                      \n
                    • Data is presented as a collection of relations.<\/li>\n
                    • Each relation is depicted as a table.<\/li>\n
                    • Columns are attributes that belong to the entity modeled by the table (ex. In a student table, you could have a name, address, student ID, major, etc.).<\/li>\n
                    • Each row (“tuple”) represents a single entity.<\/li>\n
                    • Every table has a set of attributes that taken together as a “key” (technically, a superkey”) uniquely identifies each entity.<\/li>\n<\/ul>\n

                      Question 13.
                      \nExplain outer join with example.
                      \nAnswer:
                      \nJOINS are used to retrieve data from multiple tables. Outer joins are used to return all rows from at least one of the tables. All rows are retrieved from the left table referenced with a left outer join, and all rows from the right table referenced in a right outer join. All rows from both tables are returned in a full outer join.
                      \nThe three forms of the outer join.<\/p>\n

                        \n
                      • LEFT OUTER JOIN or LEFT JOIN<\/li>\n
                      • RIGHT OUTER JOIN or RIGHT JOIN<\/li>\n
                      • FULL OUTER JOIN or FULL JOIN<\/li>\n<\/ul>\n

                        1. LEFT OUTER JOIN:
                        \nThis type of join returns all rows from the LEFT-hand table specified in the ON condition and only those rows from the other table where the joined fields are equal.
                        \nVisual Illustration:
                        \nIn this visual diagram, the LEFT OUTER JOIN returns the shaded area:
                        \n\"2nd
                        \nThe LEFT OUTER JOIN would return the all records from table 1 and only those records from table2 that intersect with table 1<\/p>\n

                        2. RIGHT OUTER JOIN:
                        \nThis type of join returns all rows from the RIGHT-hand table specified in the ON condition and only those rows from the other table where the joined fields are equal.
                        \nVisual Illustration:
                        \nIn this visual diagram, the RIGHT OUTER JOIN returns the shaded area:
                        \n\"2nd
                        \nThe RIGHT OUTER JOIN would return the all records from table2 and only those records from table 1 that intersect with table2.<\/p>\n

                        3. FULL OUTER JOIN:
                        \nThis type of join returns all rows from the LEFT-hand table and RIGHT-hand table with nulls in place where the join condition is not met.
                        \nVisual Illustration:
                        \nIn this visual diagram, the FULL OUTER JOIN returns the shaded area:
                        \n\"2nd
                        \nThe FULL OUTER JOIN would return the all records from both table1 and table2.<\/p>\n

                        Question 14.
                        \nList the components of data warehouse.
                        \nAnswer.
                        \nThe components of data warehouse are data sources, data transformation, reporting, metadata, operations and operational components.<\/p>\n

                        In short, data is moved from databases used in operational systems into a data warehouse staging area, then into a data warehouse and finally into a set of conformed data marts. Data is copied from one database to another using a technology called ETL (Extract, Transform, Load).<\/p>\n

                        2nd PUC Computer Science Data Concepts Five Mark Questions and Answers<\/h3>\n

                        Question 1.
                        \nExplain data processing cycle.
                        \nAnswer:
                        \nDATA PROCESSING CYCLE:
                        \nData processing is the activity of collecting the data from various sources, properly organizing and processing to obtain required information.
                        \nThe stages of data processing cycle
                        \n\"2nd
                        \na. Data collection:
                        \nData required for an organization may be available at various places. It involves identifying the source of data for collection. The sources may include documents, such as invoices, sales orders, purchase orders etc., for the purpose of processing.<\/p>\n

                        b. Data input:
                        \nThe gathered\/collected data is entered into the system in the suitable format which is acceptable by the data processing system for the necessary process.<\/p>\n

                        c. Processing of data:
                        \nBefore any process is applied, classifying the data or grouping the similar type of data is performed. Then to such data proper arrangement\/order is done i.e., in ascending or in descending order. Then verification for any missing data, incomplete data is done. Finally calculation process gives the information.<\/p>\n

                        d. Data output:
                        \nIt is necessary to put the results in proper format in the form of a summarized report, consolidated report, statements etc.,<\/p>\n

                        e. Data storage:
                        \nThe inputted data and generated results are stored for the future use. They are stored using different mass storage devices (Hard disk, floppy dis, etc.,).<\/p>\n

                        \"KSEEB<\/p>\n

                        Question 2.
                        \nExplain normalization with classifications and examples.
                        \nNormalization
                        \nAnswer:
                        \nNormalization theory is built around the concept of normal forms. Normalization reduces redundancy. Normalization theory is based on the fundamental notion of Functional Dependency. Normalization helps in simplifying the structure of tables.<\/p>\n

                        There are four levels of normalization.
                        \n1. First Normal Form:
                        \nFor easier understanding of the first normal form, consider an example. One employee has different project codes. Hence the projcode is said to be functionally dependent on the attribute Ecode. Now consider an unnormalized data that is represented in the following Table.<\/p>\n

                        A relational model does not permit or support such unnormalized tables. The data table must be present atleast in the first normal form, which appears as shown below.
                        \n\"2nd
                        \n2. Second Normal Form:
                        \nIn the previous normal form it was noted that there was redundancy of data, and hence the table was decomposed without any loss of information. The problems encountered here were:
                        \nInsertion:
                        \nEmployee details cannot be recorded until the employee is assigned a project.<\/p>\n

                        Updation:
                        \nThe employee code and department is repeated. Hence if an employee is transferred to another department, these changes must be reflected everywhere. Any omission will lead to inconsistencies.<\/p>\n

                        Deletion:
                        \nIf any employee completes his project, his record will be deleted and details pertaining to that employee lost.
                        \nFrom the table given below easier understanding is enabled:
                        \nIt should be noted that for a table to be in the second form it should also be in the first normal<\/p>\n\n\n\n\n\n\n
                        Encode<\/td>\nDept<\/td>\n<\/tr>\n
                        101<\/td>\nAccounts<\/td>\n<\/tr>\n
                        343<\/td>\nAdmin<\/td>\n<\/tr>\n
                        987<\/td>\nsales<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n\n\n\n\n\n
                        Encode<\/td>\nProjcode<\/td>\nHours<\/td>\n<\/tr>\n
                        101<\/td>\n20<\/td>\n90<\/td>\n<\/tr>\n
                        101<\/td>\n40<\/td>\n101<\/td>\n<\/tr>\n
                        101<\/td>\n41<\/td>\n60<\/td>\n<\/tr>\n
                        343<\/td>\n56<\/td>\n50<\/td>\n<\/tr>\n
                        343<\/td>\n78<\/td>\n92<\/td>\n<\/tr>\n
                        987<\/td>\n20<\/td>\n48<\/td>\n<\/tr>\n
                        987<\/td>\n45<\/td>\n67<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

                        form and every attribute in the record should functionally depend on the primary key.<\/p>\n

                        3. Third Normal Form:
                        \nA table is said to be in the third normal form if it is in second normal form and every non-key attribute is functionally dependent on just the primary key: The primary key here is Encode. The attribute dept-code is dependent on the dept. There is an indirect dependence on the primary key, which has to be noticed.<\/p>\n\n\n\n\n\n\n\n\n\n
                        Encode<\/td>\nDept<\/td>\nDept-code<\/td>\n<\/tr>\n
                        101<\/td>\nFinance<\/td>\n909<\/td>\n<\/tr>\n
                        303<\/td>\nSales<\/td>\n906<\/td>\n<\/tr>\n
                        400<\/td>\nSales<\/td>\n906<\/td>\n<\/tr>\n
                        500<\/td>\nAdmin<\/td>\n908<\/td>\n<\/tr>\n
                        600<\/td>\nSystems<\/td>\n901<\/td>\n<\/tr>\n
                        111<\/td>\nFinance<\/td>\n909<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

                        Even here it was noted that there were problems during insertion, updating and deletion. The relation is thus reduced as shown in the following table.
                        \nEach non-key attribute is. wholly dependent only on the primary key. Even the third normal form did not satisfy the needs, Hence, a new form called the BoycecCodd Normal Form was introduced.<\/p>\n

                        4. Boyce-Codd Normal Form:
                        \nThe third normal form was not satisfactory for relations that had multiple candidate keys. Hence Boyce and Codd introduced another form.
                        \n\"2nd
                        \nHere the candidate keys are cut code and username. The attribute cut code and username are unique for each row. Consider that another table that has a few other details, as shown in the following Table.
                        \n\"2nd
                        \nThe attributes cuscode and cusname of the above two tables can be used to link these tables. These act as a foreign key in the second table. These tables can be reduced in order to minimize redundancy. The tables are shown below.<\/p>\n\n\n\n\n\n\n\n
                        Cuscode<\/td>\nIntemcode<\/td>\nQty<\/td>\n<\/tr>\n
                        100<\/td>\n19<\/td>\n4<\/td>\n<\/tr>\n
                        100<\/td>\n16<\/td>\n2<\/td>\n<\/tr>\n
                        121<\/td>\n29<\/td>\n6<\/td>\n<\/tr>\n
                        280<\/td>\n33<\/td>\n1<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n\n
                        Cuscode<\/td>\nCusname<\/td>\n<\/tr>\n
                        100<\/td>\nGAJRAJ<\/td>\n<\/tr>\n
                        121<\/td>\nSHARMA<\/td>\n<\/tr>\n
                        280<\/td>\nSINHA<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

                        Question 3.
                        \nExplain cardinality with example.
                        \nAnswer:
                        \nCardinality specifies how many instances of an entity relate to one instance of another entity i.e., it specifies the occurrences of the relationship and also specifies the maximum number of relationships. The ordinality describes the relationship as either mandatory or optional.<\/p>\n

                        When the minimum number is zero, the relationship is usually called optional and when the minimum number is one or more, the relationship is usually called mandatory. The cardinality notation can be shown using Information Engineering style, Bachman style, Chen style and Martin style.
                        \n\"2nd
                        \n\"2nd<\/p>\n\n\n\n\n\n\n
                        Chen Style<\/td>\n<\/tr>\n
                        One to zero or more<\/td>\n1:N (n-0,1,2,3 ..)<\/td>\n<\/tr>\n
                        Zero or more to zero or more<\/td>\nM : N (m and n=0,l,2,3…)<\/td>\n<\/tr>\n
                        One to one<\/td>\n1:1<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n\n\n\n\n\n\n
                        Martin Style<\/td>\n<\/tr>\n
                        One, and only one (mandatory)<\/td>\n1<\/td>\n<\/tr>\n
                        Many (zero or more (optional)<\/td>\n*<\/td>\n<\/tr>\n
                        One or more (mandatory)<\/td>\n1…*<\/td>\n<\/tr>\n
                        Zero or one (optional)<\/td>\n0….1<\/td>\n<\/tr>\n
                        Zero or one (optional)<\/td>\n(0,1)<\/td>\n<\/tr>\n
                        One or more (mandatory)<\/td>\n(1,n)<\/td>\n<\/tr>\n
                        Zero or more (optional)<\/td>\n(0,n)<\/td>\n<\/tr>\n
                        One and only one (mandatory)<\/td>\n(14)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

                        Question 4.
                        \nExplain data independence in detail.
                        \nAnswer:
                        \nDatabase systems are designed in multi-layers. Data about data itself is divided in layered architecture. A major objective for three-level architecture is to provide data independence, which means that upper levels are unaffected by changes in lower levels.
                        \nThere are two kinds of data independence:<\/p>\n

                          \n
                        • Logical data independence<\/li>\n
                        • Physical data independence<\/li>\n<\/ul>\n

                          1. Logical Data independence:
                          \nLogical data independence indicates that the conceptual schema can be changed without affecting the existing external schemas. The change would be absorbed by the mapping between the external and conceptual levels.<\/p>\n

                          Logical data independence also insulates application programs from operations such as combining two records into one or splitting an existing record into two or more records. This would require a change in the external\/ conceptual mapping so as to leave the external view unchanged.<\/p>\n

                          2. Physical Data Independence:
                          \nPhysical data independence indicates that the physical storage structures or devices could be changed without affecting conceptual schema. The change would be absorbed by the mapping between the conceptual and internal levels.<\/p>\n

                          Physical data independence is achieved by the presence of the internal level of the database and the n, IPping or transformation from the conceptual level of the database to the internal level. Conceptual level to internal level mapping, therefore provides a means to go from the conceptual view (conceptual records) to the internal view and hence to the stored data in the database (physical records).<\/p>\n

                          If there is a need to change the file organization or the type of physical device used as a result of growth in the database or new technology, a change is required in the conceptual\/ internal mapping between the conceptual and internal levels.<\/p>\n

                          This change is necessary to maintain the conceptual level invariant. The physical data independence criterion requires that the conceptual level does not specify storage structures or the access methods (indexing, hashing etc.) used to retrieve the data from the physical storage medium.<\/p>\n

                          Making the conceptual schema physically data-independent means that the external schema, which is defined on the conceptual schema, is in turn physically data independent.<\/p>\n

                          The Logical data independence is difficult to achieve than physical data independence as it requires the flexibility in the design of database and prograll1iller has to foresee the future requirements or modifications in the design.<\/p>\n

                          \"KSEEB<\/p>\n

                          Question 5.
                          \nDiscuss file organisation with respect to physical data independence.
                          \nAnswer:
                          \nAll schemas are logical and actual data is stored in bit format on the disk. Physical data independence is the power to change the physical data without impacting the schema or logical data.
                          \n1. Physical file organization:
                          \nThis organization sees a file as organized and stored in secondary storage media. It depends on the kind of secondary storage device used. If the magnetic tap drive is used then file is organized and accessed sequentially. If the hard disk is used, then the file is stored and accessed randomly or directly. The file manager of the operating system performs this operation.<\/p>\n

                          2. Sequential or serial organization:
                          \nIn sequential access, records within a file are read or written in sequential order i.e., in the same order they are organized in the file.<\/p>\n

                          In sequential or serial access, the information can be retrieved in the same sequence in which it is stored. The data records are arranged one after the other. The records are stored on the basis of order of the record.<\/p>\n

                          In sequential organization, the data records are stored in a predetermined order based on the key fields. There is a definite relationship between logical position and physical position. The key field organizes the records.
                          \nFor ex:
                          \n\"2nd
                          \nHere, the regno is key field. All the records are organized on the key field regno in ascending order. If a regno 124 is to be accessed, then we well have to go through all the previously stored records. A magnetic tape is the most common storage device used to implement sequential and serial file organization.
                          \nAdvantages:<\/p>\n

                            \n
                          • file organization is simple<\/li>\n
                          • a data processing which requires the use of all the records is best suited to use this method. For ex: Batch processing<\/li>\n
                          • the magnetic tapes are relatively cheap and reliable<\/li>\n<\/ul>\n

                            Disadvantages:<\/p>\n

                              \n
                            • It is not suitable if the file activity ration is low<\/li>\n
                            • Duplication of data is more<\/li>\n
                            • Data transfer rate is slow<\/li>\n
                            • Not suitable for on-line and real-time systems.<\/li>\n<\/ul>\n

                              Direct Access or Random organization:
                              \nA record is accessed by going straight to the record by means of a predefined algorithm. The algorithm calculates the record physical location. The information can be retrieved in a more direct or immediate manner. Access to the information stored is directly by its record key and immediate.<\/p>\n

                              It is possible to access a particular record without going through any order. Many algorithms are used to organize the records.
                              \nA common technique is the “hashing technique”. It has two portions. Namely
                              \n1. Hashing function:
                              \nIt is an expression or formula used to generate a physical storage address for a record key.<\/p>\n

                              2. Conflict resolution function:
                              \nTakes care of any conflicts which may arise when two record keys are located on a single physical storage location.<\/p>\n

                              The random organisation is implemented in random access devices only like hard disk, CD ROM etc.
                              \nAdvantages:<\/p>\n

                                \n
                              • Direct access to any record .<\/li>\n
                              • Faster data access or retrieval.<\/li>\n
                              • Any process to the records need not be arranged in any order<\/li>\n
                              • On-line processing is suited.<\/li>\n
                              • Updating several files can be done.<\/li>\n<\/ul>\n

                                Disadvantages:<\/p>\n

                                  \n
                                • random access devices are expensive<\/li>\n
                                • uses complex technique<\/li>\n
                                • can not be implemented in magnetic tape.<\/li>\n<\/ul>\n

                                  Indexed Sequential Access Method (ISAM):
                                  \nThis method combines both the feature of the sequential and random organization. Records are accessed by using an index or a table. The index stores the address of each record corresponding to key number of the record. The records within the file are stored sequentially but directly accessed to individual records.
                                  \nAn indexed sequential access method (ISAM) consists of
                                  \n1. the main file storage
                                  \n2. A table to maintain the index
                                  \nAdvantages:<\/p>\n

                                    \n
                                  • It combines both sequential and direct<\/li>\n
                                  • Suitable for sequential access and random access<\/li>\n
                                  • Provides quick access to records<\/li>\n<\/ul>\n

                                    Disadvantage:<\/p>\n

                                      \n
                                    • it uses special software and is expensive<\/li>\n
                                    • extra time is taken to maintain an index<\/li>\n
                                    • extra storage for index files<\/li>\n
                                    • expensive hardware is required<\/li>\n<\/ul>\n

                                      \"KSEEB<\/p>\n

                                      Question 6.
                                      \nExplain the features of the database system.
                                      \nAnswer:
                                      \nThe database management system has promising potential advantages, which are explained below:
                                      \n1. Controlling Redundancy:
                                      \nIn file system, each application has its own private files, which cannot be shared between multiple applications. This can often lead to considerable redundancy in the stored data, which results in wastage of storage space. By having a centralized database most of this can be avoided.<\/p>\n

                                      It is not possible that all redundancy should be eliminated. Sometimes there are sound business and technical reasons for- maintaining multiple copies of the same data. In a database system, however this redundancy can be controlled.
                                      \nFor example:
                                      \nIn case of college database, there may be a number of applications like General Office, Library, Account Office, Hostel etc. Each of these applications may maintain the following information into own private file applications:<\/p>\n

                                      It is clear from the above file systems, that there is some common data of the student which has to be mentioned in each application, like Rollno, Name, Class, Phone_No~ Address etc. This will cause the problem of redundancy which results in wastage of storage space and difficult to maintain, but in case of centralized database, data can be shared by number of applications and the whole college can maintain its computerized data with the following database:<\/p>\n

                                      It is clear in the above database that Rollno, Name, Class, Father_Name, Address, Phone_No, Date_of_birth which are stored repeatedly in file system in each application, need not be stored repeatedly in case of database, because every other application can access this information by joining of relations on the basis of common column i.e. Rollno. Suppose any user of Library system need the Name, Address of any particular student and by joining of Library and General Office relations on the basis of column Rollno he\/she can easily retrieve this information.<\/p>\n

                                      Thus, we can say that centralized system of DBMS reduces the redundancy of data to great extent but cannot eliminate the redundancy because RolINo is still repeated in all the relations.<\/p>\n

                                      2. Integrity can be enforced:
                                      \nIntegrity of data means that data in database is always accurate, such that incorrect information cannot be stored in database. In order to maintain the integrity of data, some integrity constraints are enforced on the database. A DBMS should provide capabilities for defining and enforcing the constraints.
                                      \nFor Example:
                                      \nLet us consider the case of college database and suppose that college having only BTech, MTech, MSc, BCA, BBA and BCOM classes. But if a ser enters the class MCA, then this incorrect information must not be stored in database and must be prompted that this is an invalid data entry. In order to enforce this, the integrity constraint must be applied to the class attribute of the student entity. But, in case of file system tins constraint must be enforced on all the application separately (because all applications have a class field).<\/p>\n

                                      In case of DBMS, this integrity constraint is applied only once on the class field of the General Office (because class field appears only once in the whole database), and all other applications will get the class information about the student from the General Office table so the integrity constraint is applied to the whole database. So, we can conclude that integrity constraint can be easily enforced in centralized DBMS system as compared to file system.<\/p>\n

                                      3. Inconsistency can be avoided :
                                      \nWhen the same data is duplicated and changes are made at one site, which is not propagated to the other site, it gives rise to inconsistency and the two entries regarding the same data will not agree. At such times the data is said to be inconsistent. So, if the redundancy is removed chances of having inconsistent data is also removed.<\/p>\n

                                      Let us again, consider the college system and suppose that in case of General_Office file it is indicated that Roll_Number 5 lives in Amritsar but in library file it is indicated that Roll_Number 5 lives in Jalandhar. Then, this is a state at which tile two entries of the same object do not agree with each other (that is one is updated and other is not). At such time the database is said to be inconsistent.<\/p>\n

                                      An inconsistent database is capable of supplying incorrect or conflicting information. So there should be no inconsistency in database. It can be clearly shown that inconsistency can be avoided in centralized system very well as compared to file system .<\/p>\n

                                      Let us consider again, the example of college system and suppose that RolINo 5 is .shifted from Amritsar to Jalandhar, then address information of Roll Number 5 must be updated, whenever Roll number and address occurs in the system. In case of file system, the information must be updated separately in each application, but if we make updation only at three places and forget to make updation at fourth application, then the whole system show the inconsistent results about Roll Number 5.<\/p>\n

                                      In case of DBMS, Roll number and address occurs together only single time in General_Office table. So, it needs single updation and then an other application retrieve the address information from General_Office which is updated so, all application will get the current and latest information by providing single update operation and this single update operation is propagated to the whole database or all other application automatically, this property is called as Propagation of Update.<\/p>\n

                                      We can say the redundancy of data greatly affect the consistency of data. If redundancy is less, it is easy to implement consistency of data. Thus; DBMS system can avoid inconsistency to great extent.<\/p>\n

                                      4. Data can be shared:
                                      \nAs explained earlier, the data about Name, Class, Father name etc. of General_Office is shared by multiple applications in centralized DBMS as compared to file system so now applications can be developed to operate against the same stored data. The applications may be developed without having to create any new stored files.<\/p>\n

                                      5. Standards can be enforced :
                                      \nSince DBMS is a-central system, so standard can be enforced easily may be at Company level, Department level, National level or International level. The standardized data is very helpful during migration or interchanging of data. The file system is an independent system so standard cannot be easily enforced on multiple independent applications.<\/p>\n

                                      6. Restricting unauthorized access:
                                      \nWhen multiple users share a database, it is likely that some users will not be authorized to access all information in the database. For example, account office data is often considered confidential, and hence only authorized persons are allowed to access such data. In addition, some users may be permitted only to retrieve data, whereas other are allowed both to retrieve and to update.<\/p>\n

                                      Hence, the type of access operation retrieval or update must also be controlled. Typically, users or user groups are given account numbers protected by passwords, which they can use to gain access to the database. A DBMS should provide a security and authorization subsystem, which the DBA uses to create accounts and to specify account restrictions. The DBMS should then enforce these restrictions automatically.<\/p>\n

                                      7. Solving Enterprise Requirement than Individual Requirement:
                                      \nSince many types of users with varying level of technical knowledge use a database, a DBMS should provide a variety of user interface. The overall requirements of the enterprise are more important than the individual user requirements. So, the DBA can structure the database system to provide an overall service that is \u201cbest for the enterprise”.
                                      \nFor example: A representation can be chosen for the data in storage that gives fast access for the most important application at the cost of poor performance in some other application. But, the file system favors the individual requirements than the enterprise requirements<\/p>\n

                                      8. Providing Backup and Recovery:
                                      \nA DBMS must provide facilities for recovering from hardware or software failures. The backup and recovery subsystem of the DBMS is responsible for recovery. For example, if the computer system fails in the middle of a complex update program, the recovery subsystem is responsible for making sure that the .database is restored to the state it was in before the program started executing.<\/p>\n

                                      9. Cost of developing and maintaining system is lower:
                                      \nIt is much easier to respond to unanticipated requests when data is centralized in a database than when it is stored in a conventional file system. Although the initial cost of setting up of a database can be large, but the cost of developing and maintaining application programs to be far lower than for similar service using conventional systems.<\/p>\n

                                      The productivity of programmers can be higher in using non-procedural languages that have been developed with DBMS than using procedural languages.<\/p>\n

                                      10. Data Model can be developed :
                                      \nThe centralized system is able to represent complex data and interfile relationships, which results in better data modeling properties. The data madding properties of the relational model is based on Entity and their Relationship, which is discussed in detail in chapter 4 of the book.<\/p>\n

                                      11. Concurrency Control :
                                      \nDBMS systems provide mechanisms to provide concurrent access of data to multiple users.<\/p>\n

                                      \"KSEEB<\/p>\n

                                      Question 7.
                                      \nExplain DBMS architecture.
                                      \nAnswer:
                                      \nThe design of DBMS depends on its architecture. The DBMS architecture can be a single-tier or multi-tier. The dividing the system helps to modify, alter, change or replace on independent ‘n’ modules.
                                      \nThe database architecture is logically classified as<\/p>\n

                                        \n
                                      • one-tier architecture<\/li>\n
                                      • two-tier architecture<\/li>\n
                                      • three-tier architecture<\/li>\n<\/ul>\n

                                        a. Logical one tier architecture:
                                        \nHere, DBMS is the only entity where DBMS user directly access database and uses it. Any changes made by the user directly done on DBMS itself. The database designers and programmers use 1-tier architecture.<\/p>\n

                                        b. Logical two-tier architecture:
                                        \nIt is a client\/server architecture where user interface program and application programs run on client side. The ODBC interfaces provide API that allows client side program to call the DBMS. A client program may connect to several DBMS’s.<\/p>\n

                                        c. 3-tier architecture:
                                        \nMost widely used architecture is 3-tier architecture. 3-tier architecture separates it tier from each other on basis of users. It is described as follows:
                                        \n\"2nd
                                        \n1. Database (Data) Tier:
                                        \nAt this tier, only the database resides. Database along with its query processing languages contains all relations and their constraints.<\/p>\n

                                        2. Application (Middle) Tier:
                                        \nAt this tier the application server and program, which access database, resides. Users are unaware of any existence of a database beyond application. For database-tier, the application tier is the user of it. This tier works as mediator between the two.<\/p>\n

                                        3. User (Presentation) Tier:
                                        \nAn end user sits on this tier. From a users aspect this tier is everything. He\/she doesn’t know about any existence or form of database beyond this layer. All views are generated by applications, which resides in the application tier.<\/p>\n

                                        \"KSEEB<\/p>\n

                                        Question 8.
                                        \nExplain database model.
                                        \nDatabase Models
                                        \nAnswer:
                                        \nDatabase models are broadly classified into two categories.
                                        \nThey are:<\/p>\n

                                          \n
                                        • Object-based logical models<\/li>\n
                                        • Record-based logical models<\/li>\n<\/ul>\n

                                          The object-based logical model can be defined as a collection of conceptual tools for describing data, data relationships, and data constraints.<\/p>\n

                                          The record-based model describes the data structures and access techniques of a DBMS. There are three types of record-based logical models. They are the hierarchical model, the network model, and the relational model.<\/p>\n

                                          Consider the example of a company. There are many employees who work in various departments earning a different salary. EMPLOYEE, DEPARTMENT, SALARY represents the entities about which data has to be recorded. It would be really meaningless if the data just exists in the database.<\/p>\n

                                          Hence it is necessary that these data should be related to each other. Therefore a database should maintain information about these data and relationships.<\/p>\n

                                          Hierarchical Database Systems (HDS):
                                          \nConsider the tree diagram as given below.
                                          \n\"2nd
                                          \nThis can be said to have a parent-child relationship. The orgin of a data tree is the root. Data located at different levels along a particular branch from the root is called the node.<\/p>\n

                                          The last node in the series is called the leaf. This model supports a One-to-Many relationship. Each child has pointers to numerous siblings and there is just one pointer to the parent thus proving a One-to-Many relationship.
                                          \nDrawbacks:
                                          \nIt is not possible to insert a new level in the table without altering the structure. Suppose a new level is required between the root and the department, the only alternative is to frame an entirely new structure.<\/p>\n

                                          To set this relationship, multiple copies of the same data must be stored at multiple levels that could cause redundancy of data. To overcome this drawback, the Network Database Model was introduced.<\/p>\n

                                          Network Database Systems (NDS):
                                          \nThis model comes under Record-based logical model. The main idea behind this model is to bring about a Many-to-Many relationship. The relationship between the different data items is called as the sets. This system also uses a pointer to locate a particular record. Let us consider the item – vendor example as shown.
                                          \n\"2nd
                                          \nIf one has to know which vendor(s) is selling a particular item or which particular item the vendor sells, it is completely dependent on the pointer to map out the relationship. But even here in case of large volumes of data, it is very difficult to locate the item because it will increase the complexity as it uses pointers, the mapping of data would become very difficult.<\/p>\n

                                          Since all the models use pointers it increases complexity. To overcome all the drawbacks the idea of a Relational Database System came up.<\/p>\n

                                          Relational Database Model:
                                          \nDr. E.F.Codd first introduced the Relational Database Model in 1970. This model allows data to be represented in a ‘simple row-column format’. Each data field is considered as a column and each record is considered as a row of a table. Different relationships between the various tables are achieved by mathematical set functions namely JOIN and UNION.<\/p>\n

                                          Question 9.
                                          \nExplain Codd’s rules for database management.
                                          \nAnswer:
                                          \nDr. Edgar Frank Codd was a computer scientist while working for IBM he invented the relational model for database management. Codd.proposed thirteen rules (numbered zero to twelve) and said that if a Database Management System meets these rules, it can be called as a Relational Database Management System. These rules are called as Codd’s12 rules.
                                          \nRule Zero:<\/p>\n

                                            \n
                                          • The system must qualify as relational, as a database, and as a management system. For a system to qualify as a relational database management system (RDBMS), that system must use its relational facilities (exclusively) to manage the database.<\/li>\n
                                          • The other 12 rules derive from this rule. The rules are as follows :<\/li>\n<\/ul>\n

                                            Rule 1:
                                            \nThe information rule:
                                            \nAll information in the database is to be represented in one and only one way, namely by values in column positions within rows of tables.<\/p>\n

                                            Rule 2:
                                            \nThe guaranteed access rule:
                                            \nAll data must be accessible. This rule is essentially a restatement of the fundamental requirement for primary keys. It says that every individual value in the database must be logically addressable by specifying table name, column name and the primary key value of the row.<\/p>\n

                                            Rule 3:
                                            \nSystematic treatment of null values:
                                            \nThe DBMS must allow each field to remain null (or empty). The NULL can be represented as “missing information and inapplicable information” that is systematic, distinct from all regular values, and independent of data type. Such values must be manipulated by the DBMS in a systematic way.<\/p>\n

                                            Rule 4:
                                            \nActive online catalog based on the relational model:
                                            \nThe system must support an online, inline, relational catalog that is accessible to authorized users by means of their regular query language<\/p>\n

                                            Rule 5:
                                            \nThe comprehensive data sublanguage rule:
                                            \nThe system must support at least one relational language that<\/p>\n

                                              \n
                                            • \u00a0Has a linear syntax<\/li>\n
                                            • Can be used both interactively and within application programs,<\/li>\n
                                            • Supports data definition operations, data manipulation operations, security and integrity constraints, and transaction management operations.<\/li>\n<\/ul>\n

                                              Rule 6:
                                              \nThe view updating rule:
                                              \nAll views that can be updated theoretically must be updated by the system.<\/p>\n

                                              Rule 7:
                                              \nHigh-level insert, update, and delete:
                                              \nThis rule states that insert, update, and delete operations should be supported for any retrievable set rather than just for a single row in a single table.<\/p>\n

                                              Rule 8:
                                              \nPhysical data independence:
                                              \nChanges to the physical level (how the data is stored, whether in arrays or linked lists etc.) must not require a change to an application based on the structure.<\/p>\n

                                              Rule 9:
                                              \nLogical data independence:
                                              \nChanges to the logical level (tables, columns, rows, and so on) must not require a change to an application based on the structure.<\/p>\n

                                              Rule 10:
                                              \nIntegrity independence:
                                              \nIntegrity constraints must be specified separately from application programs and stored in the catalog. It must be possible to change such constraints as and when appropriate without unnecessarily affecting existing applications.<\/p>\n

                                              Rule 11:
                                              \nDistribution independence:
                                              \nThe distribution of portions of the database to various locations should be invisible to users of the database. Existing applications should continue to operate successfully.<\/p>\n

                                              Rule 12:
                                              \nThe non-subversion rule:
                                              \nIf the system provides a low-level (record-at-a-time) interface, then that interface cannot be used to subvert the system, for example, bypassing a relational security or integrity constraint<\/p>\n","protected":false},"excerpt":{"rendered":"

                                              You can Download Chapter 13 Data Concepts Questions and Answers, Notes, 2nd PUC Computer Science Question Bank with Answers Karnataka State Board Solutions help you to revise complete Syllabus and score more marks in your examinations. Karnataka 2nd PUC Computer Science Question Bank Chapter 13 Data Concepts 2nd PUC Computer Science Data Concepts One Mark …<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[82],"tags":[],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/kseebsolutions.guru\/wp-json\/wp\/v2\/posts\/12535"}],"collection":[{"href":"https:\/\/kseebsolutions.guru\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kseebsolutions.guru\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kseebsolutions.guru\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/kseebsolutions.guru\/wp-json\/wp\/v2\/comments?post=12535"}],"version-history":[{"count":0,"href":"https:\/\/kseebsolutions.guru\/wp-json\/wp\/v2\/posts\/12535\/revisions"}],"wp:attachment":[{"href":"https:\/\/kseebsolutions.guru\/wp-json\/wp\/v2\/media?parent=12535"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kseebsolutions.guru\/wp-json\/wp\/v2\/categories?post=12535"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kseebsolutions.guru\/wp-json\/wp\/v2\/tags?post=12535"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}