Ejemplo_1_2

Question

If the following command is executed: CREATE DATABASE test What is the page size (in kilobytes) of the database?

Answer 1

ALTER TABLE sales ADD COLUMN item CHAR(40);

Answer 2

ALTER TABLE sales ALTER COLUMN item CHAR(40);

Answer 3

ALTER TABLE sales MODIFY COLUMN item CHAR(40);

Answer 4

ALTER TABLE sales ALTER COLUMN item SET DATA TYPE CHAR(40);

Answer 5

SQL Procedure

Answer 6

Sequence Object

Answer 7

Materialized Query Table

Answer 8

When you want to control the order in which triggers are fired.

Answer 9

When you want to control the order in which stored procedures can be invoked.

Answer 10

When you want to automatically generate a numeric value that is not tied to any specific column or table.

Answer 11

When you want to automatically generate a numeric value for each row that is added to a specific table.

Answer 12

ADD COLUMN

Answer 13

ALTER COLUMN

Answer 14

APPEND COLUMN

Answer 15

RENAME COLUMN

Answer 16

A transaction-start-id column must be defined for the table.

Answer 17

A history table must be defined and associated with the base table.

Answer 18

A BUSINESS_TIME period must be specified in a CREATE or ALTER of the table.

Answer 19

A unique index must be created that prevents overlapping of the BUSINESS_TIME period of the table.

Answer 20

Oracle connect

Answer 21

Trusted context

Answer 22

Oracle federation

Answer 23

Distributed request

Answer 24

Collection

Answer 25

Bitemporal

Answer 26

Time-period

Answer 27

System-period

Answer 28

Application-period

Answer 29

In the table definition

Answer 30

In the system catalog.

Answer 31

In the schema that the index resides in.

Answer 32

In the metadata of the table the index was created for.

Answer 33

Workload manager

Answer 34

Data partitioning feature

Answer 35

Self-tuning memory manager

Answer 36

partitioned

Answer 37

To automatically capture and stop rogue queries.

Answer 38

To provide recommendations and analysis for tuning a single query.

Answer 39

To provide recommendations and analysis for tuning up to 100 queries.

Answer 40

To recommend indexes and to guide DBAs through the process of creating new indexes.

Answer 41

Control Center

Answer 42

IBM Data Studio

Answer 43

Universal Connection Expert

Answer 44

DB2 Connection Pool Manager

Answer 45

Confirm product inventory.

Answer 46

Monitor product availability.

Answer 47

Summarize sales by region.

Answer 48

Identify patterns for products sold in the last five years.

Answer 49

Associate one or more products with a purchase order.

Answer 50

To combine data from multiple sources.

Answer 51

To discover hidden relationships in data.

Answer 52

To analyze large amounts of data to find patterns.

Answer 53

To make changes to a small number of records within a single transaction.

Answer 54

Read Stability (RS)

Answer 55

Cursor Stability (CS)

Answer 56

Repeatable Read (RR)

Answer 57

Uncommitted Read (UR)

Answer 58

Table size

Answer 59

Buffer space

Answer 60

Number of locks

Answer 61

Available real storage

Answer 62

Update (U)

Answer 63

Exclusive (X)

Answer 64

Intent Exclusive (IX)

Answer 65

Read Stability (RS)

Answer 66

Repeatable Read (RR)

Answer 67

Uncommitted Read (UR)

Answer 68

Cursor Stability (CS)

Answer 69

LOCK TABLE tab1 IN READ MODE

Answer 70

LOCK TABLE tab1 IN SHARE MODE

Answer 71

LOCK TABLE tab1 IN EXCLUSIVE MODE

Answer 72

LOCK TABLE tab1 IN READ-ONLY MODE

Answer 73

When a transaction intends to read or change data.

Answer 74

When a transaction intends to change but not read data.

Answer 75

When a transaction intends to read but not change data.

Answer 76

When a transaction intends to change the system catalog.

Answer 77

Lock escalation

Answer 78

Lock substitution

Answer 79

Lock switch/exchange

Answer 80

Lock conversion/promotion

Answer 81

Read stability (RS)

Answer 82

Cursor stability (CS)

Answer 83

Repeatable read (RR)

Answer 84

Uncommitted read (UR)

Answer 85

All locks held on the database are automatically released.

Answer 86

Data stored in global temporary tables is automatically deleted.

Answer 87

Open cursors defined WITH HOLD are closed, but their data is retained.

Answer 88

The current transaction is terminated and a new transaction boundary is started.

Answer 89

COMMIT TO SAVEPOINT

Answer 90

ROLLBACK TO SAVEPOINT

Answer 91

CALL conv_temp(climate_info.avg_temp);

Answer 92

CALL convert_ftoc(climate_info.avg_temp);

Answer 93

SELECT conv_temp(avg_temp) FROM climate_info;

Answer 94

SELECT convert_ftoc(avg_temp) FROM climate_info;

Answer 95

The last 5 rows in the table will be deleted.

Answer 96

The first 5 rows in the table will be deleted.

Answer 97

The statement will fail because a subquery cannot be used with a DELETE statement.

Answer 98

The statement will fail because a table name was not specified with the DELETE statement.

Answer 99

SELECT employees.name, sales.revenue FROM employees INNER JOIN sales ON employees.id = sales.emp_id

Answer 100

SELECT employees.name, sales.revenue FROM employees INNER JOIN sales ON sales.emp_id = employees.id

Answer 101

SELECT employees.name, sales.revenue FROM sales LEFT OUTER JOIN employees ON employees.id = sales.emp_id

Answer 102

SELECT employees.name, sales.revenue FROM sales RIGHT OUTER JOIN employees ON employees.id = sales.emp_id

Answer 103

CALL statements.

Answer 104

External file access.

Answer 105

Use of a scratch pad.

Answer 106

COMMIT statements.

Answer 107

SQL control statements.

Answer 108

XMLATTRIBUTES

Answer 109

SELECT * FROM employee WHERE (hiredate < '1999-01-01' AND salary < 40000) OR (education ='University')

Answer 110

SELECT * FROM employee WHERE (hiredate < '1999-01-01') OR (salary < 40000) OR (education ='University')

Answer 111

SELECT * FROM employee WHERE (hiredate < '1999-01-01' OR (salary < 40000 AND (education ='University')

Answer 112

SELECT * FROM employee WHERE (hiredate < '1999-01-01' AND salary < 40000 AND (education ='University')

Answer 113

SELECT empno, hiredate, salary FROM employee FOR hiredate < '1998-01-01' AND salary < 35000

Answer 114

SELECT empno, hiredate, salary FROM employee WHERE hiredate < '1998-01-01' AND salary < 35000

Answer 115

SELECT empno, hiredate, salary FROM employee WHERE hiredate < '1998-01-01' OR salary < 35000

Answer 116

SELECT empno, hiredate, salary FROM employee FOR hiredate < '1998-01-01' OR salary < 35000

Answer 117

SELECT lastname, firstnme, salary, job FROM employee ORDER BY 3 FETCH FIRST 5 ROWS ONLY

Answer 118

SELECT lastname, firstnme, salary, job FROM employee ORDER BY 3 DESC FETCH FIRST 5 ROWS ONLY

Answer 119

SELECT lastname, firstnme, salary, job FROM employee ORDER BY 3 FETCH FIRST 5 ROWS

Answer 120

SELECT lastname, firstnme, salary, job FROM employee ORDER BY 3 DESC FETCH FIRST 5 ROWS

Answer 121

The INSERT statement is used to insert rows into a table, view, or table function.

Answer 122

Inserted values must satisfy the conditions of any check constraints defined on the table.

Answer 123

If an INSERT statement omits any column from the inserted row that is defined as NULL or NOT NULL WITH DEFAULT, the statement will fail.

Answer 124

If the underlying table of a view being referenced by an INSERT statement has one or more unique indexes, each row inserted does not have to conform to the constraints imposed by those indexes.

Answer 125

Consists of explicitly-supplied timestamps and a separate associated history table.

Answer 126

Is based on explicitly-supplied timestamps that define the time periods during which data is valid.

Answer 127

Is useful when one wants to keep both user-based period information and system-based historical information.

Answer 128

Consists of a pair of columns with database-manager maintained values that indicate the period when a row is current.

Answer 129

SELECT job, MIN(salary), MAX(salary) FROM employee GROUP BY job;

Answer 130

SELECT job, MIN(salary), MAX(salary) FROM employee ORDER BY job;

Answer 131

SELECT job, MIN(salary), MAX(salary) FROM employee GROUP BY job, MIN(salary), MAX(salary);

Answer 132

SELECT JOB, MIN(salary), MAX(salary) FROM employee ORDER BY job, MIN(salary), MAX(salary);

Answer 133

Unconnected

Answer 134

Load operations

Answer 135

Backup/copy table spaces

Answer 136

Create and drop databases

Answer 137

Monitor database performance

Answer 138

To define exactly what a specific user can do within a particular database once they have been authenticated.

Answer 139

To group a collection of privileges together so that they can be simultaneously granted to and revoked from multiple users.

Answer 140

To establish a credible relationship between DB2 and an external entity, such as a database administrator or a middleware server.

Answer 141

To group a collection of users together so that they can be simultaneously granted and revoked specific authorities and privileges.

Answer 142

GRANT ALTER ON SEQUENCE myseq TO user1

Answer 143

GRANT USAGE ON SEQUENCE myseq TO user1

Answer 144

GRANT SELECT ON SEQUENCE myseq TO user1

Answer 145

GRANT COMMENT ON SEQUENCE myseq TO user1

Answer 146

The column mask must be enabled; the EMPLOYEE table must be altered to activate column access control.

Answer 147

The column mask must be enabled (column access control for the EMPLOYEE table will be activated automatically).

Answer 148

The EMPLOYEE table must be altered to activate column access control (the column mask will be enabled automatically).

Answer 149

The EMPLOYEE table must be altered to activate column access control; row permission must be granted to everyone who needs to use thecolumn mask.

Answer 150

Assign the SSN column to a restricted role that only authorized users can access.

Answer 151

Only grant ACCESSCTRL authority for the SSN column to users who need to access SSN data.

Answer 152

Alter the table definition so that SSN data is stored in a separate schema that only authorized users can access.

Answer 153

Create a view for the EMPLOYEE table that does not contain the SSN column and require unauthorized users to use the view.

Answer 154

GRANT CREATETAB ON DATABASE TO user1

Answer 155

GRANT SELECT ON TABLE employee TO user1

Answer 156

GRANT CREATEVIEW ON DATABASE TO user1

Answer 157

GRANT REFERENCES ON TABLE employee TO user1

Answer 158

DBCTRL authority

Answer 159

SQLADM authority

Answer 160

DATAACCESS authority

Answer 161

ACCESSCTRL authority

Answer 162

REFERENCES

Answer 163

It must not contain more than one column.

Answer 164

It cannot be used in a referential constraint.

Answer 165

It must be defined with the UNIQUE attribute.

Answer 166

It must be defined as UNIQUE WHERE NOT NULL.

Answer 167

Only one INSERT, UPDATE, or DELETE trigger can be defined per table.

Answer 168

Triggers cannot be modified, they must be dropped and recreated with new definitions.

Answer 169

Adding a trigger to a table that already has rows in it will cause triggered actions to be fired.

Answer 170

Triggers can only be fired one time per statement irrespective of the number of rows affected.

Answer 171

An error will be returned and the operation will fail.

Answer 172

A warning will be returned and the unique index INDX1 will become the index for the primary key.

Answer 173

The primary key will be successfully added and the unique index INDX1 will be dropped and recreated as the primary key index.

Answer 174

The primary key will be successfully added, the unique index INDX1 will be dropped, and a new index will be created for the primary key.

Answer 175

The data in the table is deleted and the table persists.

Answer 176

The data in the table is deleted and the table is implicitly dropped.

Answer 177

The temporary table is converted to a base table and the data is deleted.

Answer 178

The temporary table is converted to a base table and the data is persistent.

Answer 179

The SYSIBM schema.

Answer 180

The SYSFUN schema.

Answer 181

A schema with the name of the UDF.

Answer 182

A schema with the userid of the UDF definer.

Answer 183

A trigger is designed to return specific types of values and contains executable code.

Answer 184

A trigger is designed to return specific types of values but contains no executable code.

Answer 185

A trigger performs actions to capture details about an activity like a join operation against multiple tables.

Answer 186

A trigger performs actions in response to an event like an INSERT, UPDATE or DELETE operation on a table.

Answer 187

The foreign key constraint columns must be supported by an index.

Answer 188

The foreign key constraint columns must be defined as NOT NULL.

Answer 189

The number and data types of foreign key constraint columns must match the parent key.

Answer 190

The columns of one foreign key constraint cannot be used in another foreign key constraint.

Answer 191

To define a foreign key constraint there must be an associated primary key or unique key in the same or different table.

Answer 192

To enable uniqueness.

Answer 193

To ensure data clustering.

Answer 194

To combine data from multiple tables.

Answer 195

To optimize queries ran against multiple tables.

Answer 196

No fractional digits or time zone.

Answer 197

6 fractional digits and no time zone.

Answer 198

12 fractional digits plus a time zone.

Answer 199

12 fractional digits and no time zone.

Answer 200

To allow queries to run more efficiently.

Answer 201

To enforce constraints such as uniqueness on index keys.

Answer 202

To order the columns of a table in ascending or descending sequence according to values in a row.

Answer 203

To order the rows of a table in ascending or descending sequence according to the values in a column.

Answer 204

Unique constraint

Answer 205

Primary key constraint

Answer 206

Informational constraint

Answer 207

Column default constraint

Answer 208

A table can only have one unique key constraint.

Answer 209

A table can have multiple primary key constraints.

Answer 210

Informational constraints tell DB2 what rules the data conforms to, but the rules are not enforced.

Answer 211

Foreign key constraints are enforced on the values within the rows of a table, or between the rows of two tables, by a unique index on a foreignkey.

Answer 212

In an XML index.

Answer 213

In line with the rest of the data for the table.

Answer 214

In an XML storage object that is separate from the table.

Answer 215

In line with the rest of the data for the table, for XML columns less than 32KB.

Answer 216

A BEFORE trigger can be used to perform validation of input data.

Answer 217

A BEFORE trigger can be used to automatically generate values for newly inserted rows.

Answer 218

A BEFORE trigger is fired for each row in the set of affected rows before the trigger event executes.

Answer 219

A BEFORE trigger is fired for each row in the set of affected rows instead of executing the trigger event.

Answer 220

Primary key

Answer 221

Partitioning key

Answer 222

Check constraint

Answer 223

Unique constraint

Answer 224

Change the data type of the sequence.

Answer 225

Reset the sequence to its starting value.

Answer 226

Establish new minimum or maximum values.

Answer 227

Change the increment between future values.

Answer 228

USER1 can only remove the SALES table.

Answer 229

USER1 can only remove records from the SALES table.

Answer 230

USER1 can remove the SALES table and grant the privilege to remove the SALES table to other users.

Answer 231

USER1 can remove records from the SALES table and grant the privilege to remove records from the SALES table to other users.

Answer 232

Authentication

Answer 233

Authorities and privileges

Answer 234

Label-based access control

Answer 235

Row and column access control

Answer 236

REVOKE USE OF TABLESPACE mytbsp FROM user1

Answer 237

REVOKE ALTER ON TABLESPACE mytbsp FROM user1

Answer 238

REVOKE UPDATE OF TABLESPACE mytbsp FROM user1

Answer 239

REVOKE CREATETAB ON TABLESPACE mytbsp FROM user1

Answer 240

Unconnected

Answer 241

When mandatory access control (MAC) is used to protect the table.

Answer 242

When discretionary access control (DAC) is used to protect the table.

Answer 243

When label-based access control (LBAC) is used to protect the table.

Answer 244

When row and column access control (RCAC) is used to protect the table.

Answer 245

BIND_REBIND

Answer 246

GRANT EXECUTE ON APPLICATION benefits TO user1

Answer 247

GRANT EXECUTE ON PACKAGE corpdata.pkga TO user1

Answer 248

GRANT EXECUTE ON APPLICATION PACKAGE corpdata.pkga TO user1

Answer 249

GRANT EXECUTE ON APPLICATION benefits USING PACKAGE corpdata.pkga TO user1

Answer 250

A row mask's access control rule is defined by an SQL CASE expression; a column permission's access control rule is defined by an SQLsearch condition.

Answer 251

A row permission's access control rule is defined by an SQL CASE expression; a column mask's access control rule is defined by an SQLsearch condition.

Answer 252

A row mask's access control rule is defined by an SQL search condition; a column permission's access control rule is defined by an SQL CASEexpression.

Answer 253

A row permission's access control rule is defined by an SQL search condition; a column mask's access control rule is defined by an SQL CASEexpression.

Answer 254

Materialized query table

Answer 255

System-period temporal table

Answer 256

Declared global temporary table

Answer 257

Application-period temporal table

Answer 258

CREATE DISTINCT ALIAS canadian_dollar AS DECIMAL (9,3) WITH COMPARISONS

Answer 259

CREATE DISTINCT TYPE canadian_dollar AS DECIMAL (9,3) WITH COMPARISONS

Answer 260

CREATE DISTINCT PROCEDURE canadian_dollar AS DECIMAL (9,3) WITH COMPARISONS

Answer 261

CREATE DISTINCT FUNCTION canadian_dollar AS DECIMAL (9,3) WITH COMPARISONS

Answer 262

Buffer pool

Answer 263

Storage group

Answer 264

Temporary table

Answer 265

DB2 Personal Edition

Answer 266

DB2 Development Edition

Answer 267

DB2 Connect Personal Edition

Answer 268

DB2 Development Unlimited Edition

Answer 269

SALES can be the name of a schema.

Answer 270

SALES can be the name of a package.

Answer 271

SALES can be the name of an existing alias.

Answer 272

SALES can be the name of a declared global temporary table.

Answer 273

Check constraint

Answer 274

Type-1 connect

Answer 275

Type-2 connect

Answer 276

Type-3 connect

Answer 277

Type-4 connect

Answer 278

Bitemporal tables are system tables and can only be queried by the schema owner.

Answer 279

Creating a bitemporal table is similar to creating a regular table except users must specify a system time period column.

Answer 280

When data in a bitemporal table is updated, a row is added to it's associated history table.

Answer 281

Querying a bitemporal table will produce results for a complete timeline; a view must be created to obtain results for a specific time period.

Answer 282

Table space

Answer 283

Storage group

Answer 284

Stored procedure

Answer 285

Identity Column

Answer 286

Once the row-begin, row-end, and transaction-start-id columns are created, all changes are tracked.

Answer 287

A history table must be created with identical columns to the base table and a unique index must be defined on the transaction-start-id column.

Answer 288

A history table must be created as a clone table of the base table after the row-begin, row-end, and transaction-start-id columns have beendefined.

Answer 289

A history table must be created with identical columns to the base table and then the base table altered with the ADD VERSIONING clause torelate it to the history table.

Answer 290

Buffer pool

Answer 291

Table space

Answer 292

Package cache

Answer 293

A LOB locator is a data type that is used to store LOB data in binary files.

Answer 294

A LOB locator is a data type that is used to store LOB data in a database.

Answer 295

A LOB locator represents a value for a LOB resource that is stored in a database.

Answer 296

A LOB locator represents a value for a LOB resource that is stored in a binary file.

Answer 297

DB2 Connect

Answer 298

DB2 pureScale

Answer 299

Workload Manager

Answer 300

High Availability Disaster Recovery

Answer 301

partitioned

Answer 302

IBM Data Studio

Answer 303

IBM Administrator

Answer 304

IBM Data Manager

Answer 305

IBM Command Center

Answer 306

DB2 for AIX

Answer 307

DB2 for z/OS

Answer 308

DB2 for Linux

Answer 309

Control Center

Answer 310

IBM Data Studio

Answer 311

Universal Connection Expert

Answer 312

DB2 Connection Pool Manager

Answer 313

SELECT name, COUNT(*) AS transactions FROM sales

Answer 314

SELECT name, COUNT(DISTINCT name) AS transactions FROM sales

Answer 315

SELECT name, COUNT(*) AS transactions FROM sales GROUP BY name

Answer 316

SELECT DISTINCT name, COUNT(*) AS transactions FROM sales GROUP BY transactions

Answer 317

When a ROLLBACK statement is executed, all locks held by the terminating transaction are released.

Answer 318

When a ROLLBACK TO SAVEPOINT statement is executed, all locks acquired up to the savepoint are released.

Answer 319

When a ROLLBACK TO SAVEPOINT statement is executed, all locks acquired after the savepoint are released.

Answer 320

When a ROLLBACK statement is executed, all locks acquired for open cursors that were declared WITH HOLD, are held.

Answer 321

All locks held on the database are automatically released.

Answer 322

Data stored in global temporary tables is automatically deleted.

Answer 323

Open cursors defined WITH HOLD are closed, but their data is retained.

Answer 324

The current transaction is terminated and a new transaction boundary is started.

Answer 325

SELECT * FROM employee WHERE salary < 100000

Answer 326

SELECT salary FROM employee WHERE salary > 100000

Answer 327

SELECT salary FROM employee WHERE salary > 100,000.00

Answer 328

SELECT * FROM employee WHERE salary GREATER THAN 100000

Answer 329

SELECT job, MIN(salary), MAX(salary) FROM employee GROUP BY job ORDER BY job;

Answer 330

SELECT job, MIN(salary), MAX(salary) FROM employee ORDER BY job;

Answer 331

SELECT job, MIN(salary), MAX(salary) FROM employee GROUP BY SALARY ORDER BY job;

Answer 332

SELECT job, MIN(salary), MAX(salary) FROM employee GROUP BY MIN(salary), MAX(salary) ORDER BY job;

Answer 333

SELECT dept_info(dept_id, dept_name)

Answer 334

SELECT dept_id, dept_name FROM dept_info()

Answer 335

SELECT TABLE dept_id, dept_name FROM dept_info()

Answer 336

SELECT dept_id, dept_name FROM TABLE(dept_info()) AS results

Answer 337

A Java stored procedure.

Answer 338

A REXX stored procedure.

Answer 339

A native SQL stored procedure.

Answer 340

An external SQL stored procedure.

Answer 341

SELECT workdept, AVG(salary) FROM employee ORDER BY workdept GROUP BY 2

Answer 342

SELECT workdept, AVG(salary) FROM employee ORDER BY workdept ARRANGE BY 2

Answer 343

SELECT workdept, AVERAGE(salary) FROM employee GROUP BY workdept ORDER BY 2

Answer 344

SELECT workdept, AVG(salary) FROM employee GROUP BY workdept ORDER BY 2

Answer 345

They store user-based period information.

Answer 346

They do not have a separate history table.

Answer 347

They can be queried without a time period specification.

Answer 348

They manage data based on time criteria specified by users or applications.

Answer 349

The statement will fail because a subquery cannot be used in an UPDATE statement.

Answer 350

The statement will fail because the result set produced by the subquery will contain more than one row.

Answer 351

The statement will succeed; the last record retrieved by the subquery will be used to provide a WORKDEPT value for the update operation.

Answer 352

The statement will succeed; the first record retrieved by the subquery will be used to provide a WORKDEPT value for the update operation

Answer 353

The UPDATE statement logs the before and after value of every column it modifies.

Answer 354

A searched UPDATE is used to update one or more rows and a positioned UPDATE is used to update exactly one row.

Answer 355

When the UPDATE statement modifies parent key columns, the value of corresponding foreign key columns are also modified.

Answer 356

The UPDATE statement modifies the values of specified columns in the rows of a table, view, or underlying table(s) of a specified fullselect.

Answer 357

<name>Joe Smith</name>

Answer 358

<name>Joe Smith></name><name>DB2</name>

Answer 359

<employeeinfo><name>Joe Smith</name></employeeinfo>

Answer 360

SELECT state_cd, COUNT(*) FROM states ORDER BY COUNT(*);

Answer 361

SELECT state_cd, COUNT(*) FROM states GROUP BY state_cd ORDER BY state_cd;

Answer 362

SELECT region_cd, COUNT(*) FROM states GROUP BY state_cd ORDER BY COUNT(*);

Answer 363

SELECT region_cd, COUNT(*) FROM states GROUP BY region_cd ORDER BY COUNT(*);

Answer 364

The SYSIBM schema.

Answer 365

The SYSFUN schema.

Answer 366

A schema with the name of the UDF.

Answer 367

A schema with the userid of the UDF definer.

	Criado por Mª Carmen Ruiz Garcia quase 9 anos atrás

	Copiado por ismael mesa domi quase 9 anos atrás

	Copiado por renanvkas quase 9 anos atrás

	Copiado por mmorenonf quase 9 anos atrás

	Copiado por alejandrogarciah quase 9 anos atrás

	Copiado por rosamarozzi quase 9 anos atrás

Próximo

Ejemplo_1_2

Descrição

Resumo de Recurso

Questão 1

Questão 2

Questão 3

Questão 4

Questão 5

Questão 6

Questão 7

Questão 8

Questão 9

Questão 10

Questão 11

Questão 12

Questão 13

Questão 14

Questão 15

Questão 16

Questão 17

Questão 18

Questão 19

Questão 20

Questão 21

Questão 22

Questão 23

Questão 24

Questão 25

Questão 26

Questão 27

Questão 28

Questão 29

Questão 30

Questão 31

Questão 32

Questão 33

Questão 34

Questão 35

Questão 36

Questão 37

Questão 38

Questão 39

Questão 40

Questão 41

Questão 42

Questão 43

Questão 44

Questão 45

Questão 46

Questão 47

Questão 48

Questão 49

Questão 50

Questão 51

Questão 52

Questão 53

Questão 54

Questão 55

Questão 56

Questão 57

Questão 58

Questão 59

Questão 60

Questão 61

Questão 62

Questão 63

Questão 64

Questão 65

Questão 66

Questão 67

Questão 68

Questão 69

Questão 70

Questão 71

Questão 72

Questão 73

Questão 74

Questão 75

Questão 76