Interview Questions

Reconciling the bank statement monthly is an example of independent internal verification

Capital expenditures are capitalized because of the timing of their estimated benefits – the lemonade stand will benefit the firm for many years. The employees’ work, on the other hand, benefits the period in which the wages are generated only and should be expensed then. This is what differentiates an asset from an expense.

In most cases, the best answer to this question is answering yes. Working well under pressure is a good trait to have. However, I think if you answer that you work the same with pressure and without pressure, the interviewer will be more impressed. However, you will need to explain in words why this is better. Here are some of my answers.

1. "I work well under pressure because I use the pressure to help me work more efficiently."

2. "I enjoy working under pressure because I believe it helps me grow. In my previous experience, I always worked well during deadlines, and I always learned how to work more efficiently afterwards."

3. "I work well under pressure because I don't panic. I maintain self control and work as efficiently as possible. In all my experiences, I did well and I always enjoyed the experience."

All the above listed are debugging windows in .NET

At the time of updating the data warehouse, a lookup table is used. When placed on the fact table or warehouse based upon the primary key of the target, the update is takes place only by allowing new records or updated records depending upon the condition of lookup.

The materialized views are aggregate tables. It contains summarized data. For example, to generate sales reports on weekly or monthly or yearly basis instead of daily basis of an application, the date values are aggregated into week values, week values are aggregated into month values and month values into year values. To perform this process aggregate function is used.

The Java programming language provides a system-level thread to track memory allocation.

Garbage collection has the following characteristics:

• Checks for and frees memory no longer needed

• Is done automatically

• Can vary dramatically across JVM implementations

Aynchronous and Event Driven - All APIs of Node.js library area unit aynchronous that's non-blocking. It basically means that a Node.js based mostly server not waits for a API to return information. Server moves to next API when calling it and a notification mechanism of Events of Node.js helps server to induce response from the previous API decision.

Very Fast - Node.js library is very fast in execution of code.

Single Threaded but highly Scalable - Node.js uses a single threaded model with event looping. Node.js uses a single threaded program and same program can services much larger number of requests than traditional server like open source.

No Buffering - Node.js applications never buffer any data. These applications simply output the data in faster.

Delete command removes the rows from a table based on the condition that we provide with a WHERE clause. Truncate will actually remove all the rows from a table and there will be no data in the table after we run the truncate command.

TRUNCATE:

- TRUNCATE is faster and uses fewer system and transaction log resources than DELETE.

- TRUNCATE removes the data by deallocating the data pages used to store the table's data, and only the page deallocations are recorded in the transaction log.

- TRUNCATE removes all rows from a table, but the table structure, its columns, constraints, indexes and so on, remains. The counter used by an identity for new rows is reset to the seed for the column.

- You cannot use TRUNCATE TABLE on a table referenced by a FOREIGN KEY constraint. Because TRUNCATE TABLE is not logged, it cannot activate a trigger.

- TRUNCATE cannot be rolled back.

- TRUNCATE is DDL Command.

- TRUNCATE Resets identity of the table

DELETE:

- DELETE removes rows one at a time and records an entry in the transaction log for each deleted row.

- If you want to retain the identity counter, use DELETE instead. If you want to remove table definition and its data, use the DROP TABLE statement.

- DELETE Can be used with or without a WHERE clause

- DELETE Activates Triggers.

- DELETE can be rolled back.

- DELETE is DML Command.

- DELETE does not reset identity of the table.

Note: DELETE and TRUNCATE both can be rolled back when surrounded by TRANSACTION if the current session is not closed. If TRUNCATE is written in Query Editor surrounded by TRANSACTION and if session is closed, it can not be rolled back but DELETE can be rolled back.