Ruankao System Architect (Senior) study guide
Ruankao System Architect (Senior) · Work through your exam, one topic at a time.
This independent study page provides practice for Ruankao System Architect (Senior). Its editorial learning areas include Computer architecture, logic and data representation; Operating systems, translation and concurrency; Requirements, design, testing and architecture trade-offs; Middleware, distributed transactions and architecture evaluation; Secure development, review and software supply chain; Security foundations, governance and Chinese context; Identity, access and cryptographic protection; Data, Databases, and Information Retrieval; Engineering calculations, alternatives and technical evidence; Project scope, scheduling and earned-value models. The Ruankao System Architect (Senior) study guide has 10 sections and about 6,919 words.
01Computer architecture, logic and data representation
This domain examines the stored-program machine: how instructions and data share one memory, how the processor fetches and executes them, and how the memory hierarchy and instruction-set design affect performance. Instructions and data share one memory and one set of buses.
713 words, about 4 min02Operating systems, translation and concurrency
Understand the OS as a resource manager and extended machine: process management, CPU scheduling (FCFS, SJF, priority, round robin), process states and the PCB, context switching, threads versus processes, and inter-process communication. Study synchronization: critical sections, mutexes, semaphores, and deadlock's four necessary conditions (mutual exclusion, hold and wait, no preemption, circular wait).
494 words, about 2 min03Requirements, design, testing and architecture trade-offs
Know the software development life cycle: requirements, analysis, design, implementation, testing, deployment, and maintenance. Compare process models - waterfall, incremental, spiral, prototype, and agile/Scrum - and when each fits.
503 words, about 3 min04Middleware, distributed transactions and architecture evaluation
Middleware supplies reusable capabilities between applications and underlying resources. Message brokers, transaction coordinators, service gateways, naming systems and integration adapters serve different purposes.
460 words, about 2 min05Secure development, review and software supply chain
Secure software development integrates security requirements, design, implementation, testing and maintenance. Begin with intended users, data, business functions and misuse cases.
438 words, about 2 min06Security foundations, governance and Chinese context
This domain covers the vocabulary and models that every later domain assumes: what security protects, how it is decomposed, and the formal rules that describe access control. NISP Level 1 questions here are usually definitional, so precision matters more than depth.
917 words, about 5 min07Identity, access and cryptographic protection
This domain tests the identity lifecycle and the mechanisms that turn an identity into an authorised action. Expect questions that separate authentication from authorisation and that ask which access control model fits a scenario.
857 words, about 4 min08Data, Databases, and Information Retrieval
Data questions move from raw facts to organized, queryable information. In the relational model, tables have rows (records) and columns (attributes); keys enforce identity and relationships.
468 words, about 2 min09Engineering calculations, alternatives and technical evidence
Engineering calculations simplify a system so alternatives can be compared. Record variables, units, boundaries and assumptions before substituting numbers.
446 words, about 2 min10Project scope, scheduling and earned-value models
Domain 2 tests whether you can define a project precisely, separate it from operations, program, and portfolio, and read an organizational chart to determine how much authority a project manager actually holds. Items often present a short organizational scenario and ask which structure or PMO type it describes, or ask where a given input belongs: enterprise environmental factors or organizational process assets.
1,623 words, about 8 min