PracticeVideosBlogFlashcardsEspañol
All Practice Exams

100+ Free ICT-App Dev Specialist FA Practice Questions

Prepare for the ICT-Application Development Specialist mit eidgenössischem Fachausweis exam with instant access — no signup required.

✓ No registration✓ No credit card✓ No hidden fees✓ Start practicing immediately
100+ Questions
100% Free

Loading practice questions...

2026 Statistics

Key Facts: ICT-App Dev Specialist FA Exam

NQF 6

Swiss Qualification Level

ICT-Berufsbildung Schweiz (NQR level 6, bachelor-level equivalence)

Grade 4.0

Minimum Passing Grade

ICT-Berufsbildung Schweiz (Scale 1-6)

CHF 3,000

Federal Exam Fee

ICT-Berufsbildung Schweiz, published examination fee

50%

Federal Tuition Subsidy

SBFI Bundesbeiträge (Up to CHF 9,500)

3 parts

Project work, written exam, oral exam

Prüfungsausschreibung ICT-Application Development Specialist 2026

100

Practice Questions

OpenExamPrep

The Swiss Federal Diploma in ICT Application Development (ICT-Application Development Specialist FA) is a tertiary qualification placed at NQF level 6 (bachelor-level equivalence). Administered by ICT-Berufsbildung Schweiz under SBFI oversight, it tests four core engineering domains: Software Architecture & System Design, Clean Code & Engineering Principles, Quality Assurance & Security, and DevOps, CI/CD & Agile Delivery.

Sample ICT-App Dev Specialist FA Practice Questions

Try these sample questions to test your ICT-App Dev Specialist FA exam readiness. Each question includes a detailed explanation. Start the interactive quiz above for the full 100+ question experience with AI tutoring.

1In Clean Architecture and Hexagonal Architecture (Ports and Adapters), what is the core rule regarding source code dependencies across architectural layer boundaries?
A.Dependencies must always point inwards toward higher-level policies and the enterprise business domain (Dependency Rule), meaning domain entities and use cases have zero dependency on UI, database, or frameworks
B.Domain entities must directly inherit from the ORM database model classes to ensure efficient persistence
C.Outer infrastructure adapters must be invoked directly by use cases using concrete class instantiations without interfaces
D.Dependencies must flow outward from the domain model toward the external database and web API frameworks
Explanation: The fundamental Dependency Rule of Clean Architecture states that source code dependencies can only point inward. High-level policy (Domain Entities and Application Use Cases) is decoupled from low-level implementation details (Databases, Web Frameworks, UI). Inversion of Control via interfaces (Ports) ensures the domain never imports infrastructure packages.
2In Domain-Driven Design (DDD), what is the primary distinction between an Entity and a Value Object?
A.An Entity is defined by a persistent unique identity that runs through its entire lifecycle regardless of attribute changes, whereas a Value Object is immutable and defined purely by the equality of its attributes
B.An Entity is stored in a relational SQL database, while a Value Object is stored exclusively in a Redis cache
C.An Entity cannot contain business logic methods, while a Value Object contains all domain services
D.An Entity is always mutable by external consumers, while a Value Object must have public setter methods
Explanation: In DDD (Eric Evans), an Entity has an explicit identity (e.g., `CustomerId` or `OrderId`) that distinguishes it from all other entities even if all other fields are identical. A Value Object (e.g., `Money`, `Address`, `DateRange`) has no conceptual identity; it is immutable and two instances with identical properties are considered equal.
3In Domain-Driven Design (DDD), what is an Aggregate Root and what rule governs external object references into the aggregate?
A.An Aggregate Root is the master entity that encapsulates a cluster of associated objects and enforces all business invariants; external objects may only hold references to the Aggregate Root, never to internal child entities
B.An Aggregate Root is a database stored procedure that runs hourly batch updates across all database tables
C.An Aggregate Root is a global singleton class that manages HTTP network requests
D.An Aggregate Root allows external classes to directly modify child entity fields without going through the root
Explanation: An Aggregate is a transactional boundary of domain objects. The Aggregate Root is the single entry point. External contexts are only allowed to reference the Aggregate Root ID. Direct external access or mutation of internal entities inside the aggregate boundary is prohibited to guarantee that business rules and consistency invariants are never bypassed.
4When implementing distributed transactions across autonomous microservices, why is the Saga pattern preferred over two-phase commit (2PC / XA transactions)?
A.2PC requires synchronous locking across distributed databases, creating high latency, single points of failure, and scalability bottlenecks; Sagas use a sequence of local transactions with compensating transactions for rollbacks
B.2PC does not support relational databases like PostgreSQL or MySQL
C.Sagas completely eliminate the need for error handling or compensation logic
D.2PC requires microservices to be written in the exact same programming language
Explanation: Two-Phase Commit (2PC) relies on synchronous distributed locks across all participating databases, creating tight coupling, blocking coordinators, and poor availability under network partitions (CAP theorem). Sagas execute a series of local ACID transactions coordinated via events or an orchestrator; if a step fails, compensating transactions undo preceding changes asynchronously.
5What is the primary purpose of the Transactional Outbox Pattern in microservices architectures?
A.To guarantee atomic execution between database state mutations and publishing domain events to a message broker (e.g., Kafka/RabbitMQ) without distributed dual-write inconsistencies
B.To compress outgoing HTTP response payloads using Brotli compression
C.To cache user email templates in memory before sending
D.To automatically encrypt all network traffic leaving the microservice
Explanation: When a service updates its database and sends an event to a message broker, a dual-write failure can cause data inconsistency (e.g., DB commits but message broker is down). The Outbox pattern writes the event into an `outbox` table in the SAME local database transaction. A separate background process (or CDC / Debezium) reliably reads and publishes the outbox events to the message broker.
6In the Command Query Responsibility Segregation (CQRS) architectural pattern, what is the key architectural separation?
A.Mutating write operations (Commands) are processed via a dedicated domain write model, while read operations (Queries) use an optimized, independent read model or projection
B.Frontend user interfaces are written in HTML, while backend systems are written in C++
C.HTTP GET requests are handled by relational databases, while HTTP POST requests are handled by file systems
D.Commands are executed synchronously by the client, while Queries can only be fetched once per day
Explanation: CQRS segregates the responsibility between commands (state changes that enforce domain rules) and queries (read models optimized for UI retrieval, often using denormalized read stores or materialized views updated via domain events).
7According to the Richardson Maturity Model for RESTful Web APIs, what architectural capability characterizes Level 3 (the highest level of REST maturity)?
A.HATEOAS (Hypermedia as the Engine of Application State), where responses include hypermedia links guiding clients on valid next actions and transitions
B.The use of HTTP POST for all RPC operations
C.Introducing unique URI endpoints for individual resources (Level 1)
D.Utilizing standard HTTP verbs (GET, POST, PUT, DELETE) and status codes (Level 2)
Explanation: The Richardson Maturity Model defines: Level 0 = Swamp of POX (single URI, HTTP POST); Level 1 = Resources (distinct URIs); Level 2 = HTTP Verbs & Status Codes; Level 3 = Hypermedia Controls (HATEOAS), where resources dynamically embed clickable links/rel attributes to drive application state transitions.
8In GraphQL API architectures, what is the 'N+1 Query Problem' and what standard pattern is used to resolve it in resolver functions?
A.When resolving nested child fields for a list of $N$ parent objects, naive resolvers execute 1 query for the parent list plus $N$ individual queries for each child; resolved using the DataLoader batching and caching pattern
B.When a client requests more than $N+1$ fields in a single GraphQL query; resolved by limiting query depth
C.When a GraphQL server has $N+1$ database replicas; resolved by master-slave synchronization
D.When a mutation takes $N+1$ seconds to execute; resolved by increasing server CPU
Explanation: In GraphQL, nested resolvers execute independently. Fetching 50 users and their posts naively triggers 1 query for users and 50 separate queries for posts (N+1 queries). The DataLoader pattern collects all requested IDs during a single tick of the event loop and executes a single batched query (`WHERE id IN (...)`), caching results across the request.
9In distributed microservices, how does the Circuit Breaker pattern (e.g., Resilience4j / Polly) protect a system from cascading failures when an upstream dependency becomes unresponsive?
A.It tracks failure rates: when failures exceed a threshold, it transitions from Closed to Open, immediately failing fast without calling the remote service; after a cooldown, it enters Half-Open to test recovery with limited canary traffic
B.It automatically doubles the database connection pool size when latency increases
C.It routes all failing traffic directly to the client's local browser storage
D.It permanently terminates the calling microservice process on the first error
Explanation: The Circuit Breaker pattern has three states: Closed (normal operation), Open (tripped after excessive timeouts/failures, immediately rejecting calls to prevent thread exhaustion and give the failing service time to recover), and Half-Open (trial state permitting a small sample of requests to verify if the dependency has healed before closing).
10In RESTful API design, what is the difference between an Idempotent HTTP method and a Safe HTTP method according to RFC 9110?
A.A Safe method (like GET, HEAD) does not alter server state (read-only); an Idempotent method (like PUT, DELETE) may alter state, but making multiple identical requests produces the exact same end state on the server as a single request
B.An Idempotent method never requires authentication, while a Safe method requires OAuth 2.0
C.A Safe method can only return XML, while an Idempotent method returns JSON
D.POST is both Safe and Idempotent, while GET is neither
Explanation: Under RFC 9110: Safe methods (GET, HEAD, OPTIONS) are read-only and have no intended state-changing side effects. Idempotent methods (PUT, DELETE, GET, HEAD) guarantee that $N > 0$ identical requests have the identical side effect on server state as 1 request. POST is neither safe nor idempotent by default.

About the ICT-App Dev Specialist FA Exam

The ICT-Application Development Specialist mit eidgenössischem Fachausweis (Swiss Federal Diploma of Higher VET in Application Development / Spécialiste en développement d'applications TIC avec brevet fédéral) is Switzerland's benchmark professional credential for senior software developers, application engineers, and technical leads across frontend, backend, mobile, and data engineering disciplines. Governed by the Prüfungsordnung and Wegleitung issued by ICT-Berufsbildung Schweiz under SBFI oversight and placed at level 6 of the Swiss National Qualifications Framework, which the association equates to bachelor-level requirements, it certifies advanced expertise in software architecture (Clean Architecture, Microservices, DDD), Clean Code, database engineering, API design, automated testing, application security (OWASP), and CI/CD pipelines. Note on format and language: the official federal examination is conducted in German, French, and Italian and consists of modular written case studies, practical project work (IPE), and oral examination rather than multiple-choice questions. This question bank is an English-language multiple-choice study adaptation created by OpenExamPrep—not an official translation and not a simulation of the exam format—that preserves industry-standard technical terminology and Swiss examination standards.

Assessment

Three examination parts under the Prüfungsordnung in force for examinations from 2024, and a chosen specialisation of Frontend, Mobile, Backend or Data Engineering. Part 1 is the Individuelle Praktische Entwicklungsarbeit, submitted by the published deadline (31 March for the 2026 sitting). Part 2, Entwicklung und Architektur, is the written examination day (13 May 2026). Parts 1 and 3, Fachliche Führung und Innovation, are examined orally in the following week (18-22 May 2026). Repeat fees are published per part: CHF 1,300 for part 1 and CHF 950 each for parts 2 and 3.

Time Limit

Project work prepared in advance, one written examination day, and an oral examination; the individual part durations are set in the Wegleitung and are not published on the association's public exam pages

Passing Score

Overall grade of at least 4.0 (scale 1.0 to 6.0), where 4.0 is the pass mark under the Prüfungsordnung

Exam Fee

CHF 3,000 including additional fees, of which CHF 200 covers issuing the Fachausweis, the graduation ceremony or inspection of the examination file; preparatory courses are eligible for the 50% Swiss federal tuition subsidy (Bundesbeiträge, capped at CHF 9,500) (ICT-Berufsbildung Schweiz, under SBFI supervision)

ICT-App Dev Specialist FA Exam Content Outline

25%

Software Architecture & System Design

Architectural patterns (Clean Architecture, Hexagonal, Microservices, Event-Driven, CQRS), Domain-Driven Design (DDD), API design (RESTful, OpenAPI 3.0, GraphQL, gRPC), cloud-native design, and resiliency patterns.

25%

Software Engineering & Clean Code Principles

Object-oriented and functional paradigms, GoF design patterns, SOLID principles, refactoring, concurrency, multithreading, relational database design (SQL, normalization, indexing, transactions), and NoSQL architectures.

25%

Quality Assurance, Testing & Application Security

Testing pyramid (unit, integration, contract, end-to-end), TDD/BDD, static code analysis, OWASP Top 10 web vulnerabilities, authentication and authorization (OAuth 2.0, OpenID Connect, JWT, RBAC), and cryptography.

25%

DevOps, CI/CD Pipelines & Agile Collaboration

Continuous Integration/Continuous Deployment pipelines, containerization (Docker multi-stage), Kubernetes workload deployment, Git branching models, Scrum/Kanban agile delivery, C4 documentation, and ADRs.

How to Pass the ICT-App Dev Specialist FA Exam

What You Need to Know

  • Passing score: Overall grade of at least 4.0 (scale 1.0 to 6.0), where 4.0 is the pass mark under the Prüfungsordnung
  • Assessment: Three examination parts under the Prüfungsordnung in force for examinations from 2024, and a chosen specialisation of Frontend, Mobile, Backend or Data Engineering. Part 1 is the Individuelle Praktische Entwicklungsarbeit, submitted by the published deadline (31 March for the 2026 sitting). Part 2, Entwicklung und Architektur, is the written examination day (13 May 2026). Parts 1 and 3, Fachliche Führung und Innovation, are examined orally in the following week (18-22 May 2026). Repeat fees are published per part: CHF 1,300 for part 1 and CHF 950 each for parts 2 and 3.
  • Time limit: Project work prepared in advance, one written examination day, and an oral examination; the individual part durations are set in the Wegleitung and are not published on the association's public exam pages
  • Exam fee: CHF 3,000 including additional fees, of which CHF 200 covers issuing the Fachausweis, the graduation ceremony or inspection of the examination file; preparatory courses are eligible for the 50% Swiss federal tuition subsidy (Bundesbeiträge, capped at CHF 9,500)

Keys to Passing

  • Work through all 100 available questions
  • Review every answer and explanation
  • Track weak areas and revisit them
  • Use our AI tutor for tough concepts

ICT-App Dev Specialist FA Study Tips from Top Performers

1Master Software Architecture Trade-offs: Understand the boundary definitions between domain logic, application use cases, and infrastructure adapters in Clean/Hexagonal architecture, and know when to apply CQRS vs traditional CRUD.
2Apply Domain-Driven Design (DDD) Concepts: Practice identifying aggregate boundaries, establishing invariants within entity aggregates, and designing isolated bounded contexts with anti-corruption layers.
3Design Robust API Contracts: Be fluent with OpenAPI 3.0 specification syntax, REST idempotency semantics (PUT vs PATCH vs POST), GraphQL N+1 problem resolution with DataLoader, and gRPC streaming.
4Implement OWASP Top 10 Remediations: Master defense mechanisms against SQL Injection (prepared statements), XSS (context-aware encoding, Content Security Policy), CSRF (SameSite cookies, anti-CSRF tokens), and SSRF (whitelisting, metadata service blocking).
5Optimize Database Performance: Understand composite B-Tree index ordering, index selectivity, query execution plan analysis (EXPLAIN ANALYZE), isolation levels (Read Committed vs Repeatable Read vs Serializable), and optimistic vs pessimistic locking.

Frequently Asked Questions

What is the ICT-Application Development Specialist mit eidg. Fachausweis?

The ICT-Application Development Specialist mit eidgenössischem Fachausweis is a federally recognized tertiary qualification (Berufsprüfung) in Switzerland, regulated by the SBFI and placed at level 6 of the National Qualifications Framework. It validates advanced technical and architectural competence in designing, developing, testing, and operating enterprise applications.

Who organizes the Swiss ICT Application Development Federal Examination?

The examination is organized and administered by ICT-Berufsbildung Schweiz, the national competence center and professional association for ICT vocations, operating under the regulatory authority of the SBFI.

What are the admission requirements for the Federal Examination?

ICT-Berufsbildung Schweiz publishes three routes: an Informatiker/in EFZ plus at least two years of professional practice in application development; another EFZ in the ICT field plus at least three years of such practice; or an EFZ, gymnasiale Maturität, Fachmaturität, Berufsmaturität or equivalent qualification plus at least four years of professional practice in application development. Admission itself is decided only through the association's Vorabklärungsportal.

How is the Federal Examination structured and scored?

The official Prüfungsausschreibung names three parts: 1. Individuelle Praktische Entwicklungsarbeit, submitted in advance; 2. Entwicklung und Architektur, examined in writing; 3. Fachliche Führung und Innovation, examined orally. For the 2026 sitting the project work was due 31 March, the written part fell on 13 May and the oral parts ran 18-22 May in Bern. Grades run 6 to 1 in half steps with 4.0 as the pass mark; the detailed pass conditions are in the Prüfungsordnung.

Are preparatory courses subsidized by the Swiss Federal Government?

Yes. Under the SBFI federal subsidy program for higher vocational education (Bundesbeiträge für eidgenössische Prüfungen), the Swiss Confederation reimburses 50% of eligible tuition costs (up to CHF 9,500) directly to candidates upon sitting the examination.

Why are practice questions provided in English on OpenExamPrep?

While the official Swiss exams are offered in German, French, and Italian, software engineering frameworks, documentation, API specifications, and international tech teams in Switzerland work primarily in English. This practice bank provides a rigorous English-language adaptation aligned with the official qualification profile.