Book Image

Cracking the IT Architect Interview

By : Sameer Paradkar
Book Image

Cracking the IT Architect Interview

By: Sameer Paradkar

Overview of this book

An architect attends multiple interviews for jobs or projects during the course of his or her career. This book is an interview resource created for designers, consultants, technical, solution, domain, enterprise, and chief architects to help them perform well in interview discussions and launch a successful career. The book begins by providing descriptions of architecture skills and competencies that cover the 12 key domains, including 350+ questions relating to these domains. The goal of this book is to cover all the core architectural domains. From an architect’s perspective, it is impossible to revise or learn about all these key areas without a good reference guide – this book is the solution. It shares experiences, learning, insights, and proven methodologies that will benefit practitioners, SMEs, and aspirants in the long run. This book will help you tackle the NFR domain, which is a key aspect pertaining to architecting applications. It typically takes years to understand the core concepts, fundamentals, patterns, and principles related to architecture and designs. This book is a goldmine for the typical questions asked during an interview and will help prepare you for success!
Table of Contents (14 chapters)

Solution architecture - scenario Q and A

You are creating a website to sell fine art to the rich and famous. You are only expecting to make one or two sales per week. Considering you require the system to be both secure and provide support for the transactions, which of the following describes the most appropriate architecture?

Please select from the following options:

  • A. Use JSP/servlets for presentation, EJBs for business logic, and an enterprise database.

  • B. Use JSP/servlets for presentation, EJBs for business logic, and a small-scale database.

  • C. Use JSP/servlets for both presentation and business logic and JTS for the transactions.

Here is an explanation of the answers:

Choice C is the correct answer.

Although the scenario states that the application must be both secure and provide support for transactions, due to the low number of sales expected there is no justification for using an application server. Instead, it is more appropriate to use JTS (for the transactions) and servlets (for...