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)

Case studies

This section lists different enterprise architecture domain case studies.

Enterprise architecture

The next paragraphs describe the enterprise architecture domain case studies. Each case study explains the background in terms of the existing business setup, the business problem or requirements and the expected output/s

Case study one

An enterprise runs a portal for its retailers spread across the world. The portal uses BEA web logic portal, Siebel Customer Relationship Management (CRM), Oracle database, Informatica ETL, and Vignette content management. The enterprise wishes to upgrade all the products to the latest versions because:

  • Vendors of all products will eventually stop supporting older versions

  • The enterprise would like to use the latest features provided by the new versions of all/some products

  • The enterprise would like to scrap custom code for features that have now been introduced as out-of-the-box features from these products

The client wants us to define a strategy for this...