Technician

I'd be very surprised if you haven't been asked this one at every interview. It's probably the most asked question because it sets the stage for the interview and it gets you talking. Be careful not to give the interviewer your life story here. You don't need to explain everything from birth to present day. Relevant facts about education, your career and your current life situation are fine.

When an interviewer poses this question, he/she may be attempting to assess how well you would integrate into the work environment. However, they will likely expect your answer to include a description that applies to or embodies the atmosphere of their workplace. Common terms that can be used to describe such environments include “professional” or “casual,” “open” or “private,” and “fast-paced” or “relaxed,” among others. It may also help to look into how other similar work environments are described, so that you can use comparable terminology. Avoid superficial and general descriptions, and be ready to justify your reasoning well.

If you have had prior experience at another internship, reflect upon the experiences you had then and think about what you learned there—what takeaways can now be applied to this new opportunity? If you haven’t had internship experience, be prepared to honestly answer why you’re seeking your first internship now.

The answer to this one is not money, even if it is. You should be motivated by life's noble pursuits. You want recognition for a job well done. You want to become better at your job. You want to help others or be a leader in your field.

As I'm sure you know, "because I'm great" or "I really need a job" are not good answers here. This is a time to give the employer a laundry list of your greatest talents that just so happen to match the job description. It's also good to avoid taking potshots at other potential candidates here. Focus on yourself and your talents, not other people's flaws.

Technicians can work in any industrial sector. But it is natural for a technician to work with a limited category of customers. So just talk about yourself and try to provide information relevant to the interview. Describe your job in general (hardware store and repair shop, IT companies, etc.). List a few specific tasks you usually do, such as visiting private homes to repair minor problems on the spot, or installing and maintaining software and hardware security in the companies of a specific district.

If one or a few processes have a high access rate to data on one track of a storage disk, then they may monopolize the device by repeated requests to that track. This generally happens with most common device scheduling algorithms (LIFO, SSTF, C-SCAN, etc). High-density multisurface disks are more likely to be affected by this than low density ones.

Placement algorithms determine where in available real-memory to load a program. Common methods are first-fit, next-fit, best-fit. Replacement algorithms are used when memory is full, and one process (or part of a process) needs to be swapped out to accommodate a new program. The replacement algorithm determines which are the partitions to be swapped out.

No Windows NT is not so, because its not implemented in object oriented language and the data structures reside within one executive component and are not represented as objects and it does not support object oriented capabilities.

☛ Network redirector/ Server

☛ Cache manager.

☛ File systems

☛ Network driver

☛ Device driver

Going over your resume is a great way to showcase your ability to discuss your professional experiences, and is an excellent opportunity to market yourself. Given that this question assesses how well you know your resume, confidently elaborating on prior experiences in detail is key. This question is also likely evaluating your ability to communicate concisely, so avoid droning on and on.

When employers ask this question, they’re trying to get a feel for your interests within your major. While pursuing a general field is one thing, it is valuable to them to see what you are particularly invested in, what areas pique your curiosity the most, and what motivates you. Giving your interviewer a list of classes is one thing, but employers probably don’t care so much about the list of the classes as they do about why you chose the classes. The critical aspect of the question is to give your interviewer a sense of what you strive to accomplish and actively seek to gain in your academic environment.

When an interviewer poses this question, he/she may be trying to determine what sort of jobs or projects you find disagreeable, and the exact reasons for why you think so. Be honest when replying, and give specific reasons that provide insight into your rationale for backing out of such commitments.

This should be a straightforward question to answer, but it can trip you up. Presumably you are looking for a new job (or any job) because you want to advance your career and get a position that allows you to grow as a person and an employee. It's not a good idea to mention money here, it can make you sound mercenary. And if you are in the unfortunate situation of having been downsized, stay positive and be as brief as possible about it. If you were fired, you'll need a good explanation. But once again, stay positive.

Has the candidate taken online classes, or do they spend some of their spare time coding or troubleshooting technology issues? Have they taken on work projects in areas of tech they want to learn more about?

Also called FIFO anomaly. Usually, on increasing the number of frames allocated to a process virtual memory, the process execution is faster, because fewer page faults occur. Sometimes, the reverse happens, i.e., the execution time increases even when more frames are allocated to the process. This is Belady's Anomaly. This is true for certain page reference patterns.

User data: Modifiable part of user space. May include program data, user stack area, and programs that may be modified.

User program: The instructions to be executed.

System Stack: Each process has one or more LIFO stacks associated with it. Used to store parameters and calling addresses for procedure and system calls.

Process control Block (PCB): Info needed by the OS to control processes.

The repeated execution of a loop of code while waiting for an event to occur is called busy-waiting. The CPU is not engaged in any real productive activity during this period, and the process does not progress toward completion.

☛ Normal completion

☛ Time limit exceeded

☛ Memory unavailable

☛ Bounds violation

☛ Protection error

☛ Arithmetic error

☛ Time overrun

☛ I/O failure

☛ Invalid instruction

☛ Privileged instruction

☛ Data misuse

☛ Operator or OS intervention

☛ Parent termination.