Your current backup strategy is to run COPY SHRLEVEL CHANGE for all your table spaces each night. You create FULL image copies once a week and INCREMENTAL copies during the rest of the days. After migrating to DB2 10, you plan to create the FULL image copies using FLASHCOPY YES and COPYDDN, that is you create a flash copy image copy (FCIC) andadditionally a sequential copy. What happens to the incremental copies that you continue to create on all other days?

• A. If DSNZPARM FLASHCOPY_COPY is set to YES, the incremental copies will automatically be incremental FLASHCOPY copies.
• B. The COPY utilities with FULL NO option will not run. If there are entries in SYSIBM.SYSCOPY that indicate thatFCICs exist for a give page set, INCREMENTAL copies cannot be taken anymore.
• C. The first image copy utility execution after the FULL FCIC and sequential copy created from the FCIC will end up as FULL copy although you specify the FULL NO statement on theCOPY utility control statement.
• D. Nothing special. The only difference is that the FULL copy, which is the basis for the subsequent incremental copies has now been generated from the FCIC.

Given the following view definition: CREATE VIEW EMPD AS (SELECT D.DEPTNAME,
E.LASTNAME FROM DEPT D INNER JOIN EMP E ON D.DEPTNO = E.WORKDEPT);
Can an UPDATE statement be used to update the view EMPD on joined tables DEPT and EMP?

• A. Yes, the view EMPD can be updateddirectly via an UPDATE statement.
• B. Yes, an UPDATE statement against the EMPD view is allowed if an INSTEAD OF trigger is defined on the view.
• C. No, an UPDATE statement against the EMPD view is not allowed at all.
• D. No, only a clone of the view EMPD can be updated via an UPDATE statement.

What is the purpose of the following query? SELECT DBNAME, NAME FROM
SYSIBM.SYSTABLESPACE TS WHERE NOT EXISTS (SELECT TP.DBNAME,
TP.TSNAMEFROM SYSIBM.SYSTABLEPART TP WHERE TP.DBNAME = TS.DBNAME
AND TP.TSNAME = TS.NAME);

• A. It displays the number of inconsistent rows in SYSIBM.SYSTABLESPACE.
• B. It identifies whichtable spaces have missing related rows in SYSIBM.SYSTABLEPART.
• C. It displays which rows in SYSIBM.SYSTABLEPART do not have a matching table name in SYSIBM.SYSTABLESPACE.
• D. It identifies which tables do not have related rows in SYSIBM.SYSTABLEPART.

For monitoring space growth over time, which statistics should NOT be considered?

• A. SYSIBM.SYSTABLEPART
  CARDF, SPACEF
  SYSIBM.SYSINDEXPART
  CARDF, SPACEF
• B. SYSIBM.SYSTABLEPART_HIST
  CARDF, SPACEF
  SYSIBM.SYSINDEXPART_HIST
  CARDF, SPACEF
• C. SYSIBM.SYSTABLESPACE
  DSSIZE, AVGROWLEN
  SYSIBM.SYSINDEXES
  PIECESIZE, AVGKEYLEN
• D. SYSIBM.SYSTABLESPACESTATS
  SPACE
  SYSIBM.SYSINDEXSPACESTATS
  SPACE