security Online Quiz - 17

Novell Access Manager has two core components: Identity Server handles authentication and user identity, while Access Gateway manages access control to protected resources. User Application, Collectors, and Analyzer are not standard Access Manager components.

Access Governance Suite is designed specifically for governing and certifying access rights, helping enterprises balance the need for quick access (agility) with security controls. Secure Login, Access Manager, and Privileged User Manager serve different specific purposes.

Novell Secure Login was the enterprise single sign-on solution that allowed users to authenticate once and access multiple applications without re-entering credentials. Access Manager handles web access control, Access Governance Suite manages compliance, and Privileged User Manager controls admin accounts.

Access Governance Suite provides compliance management through access certification, policy enforcement, and audit reporting capabilities. It helps organizations meet regulatory requirements by governing who has access to what resources. Secure Login handles SSO, Access Manager manages web access, and Privileged User Manager controls administrative accounts.

In TOGAF, Architecture Building Blocks (ABBs) originate from the Architecture Continuum, which contains generic architecture assets and models from the enterprise and industry. The Solutions Continuum (A) provides Building Blocks (SBBs) for specific solutions. Architecture Vision (B) is a phase in TOGAF, not a source of ABBs. The Architecture Board (D) governs architecture, and the CIO (E) is an executive role - neither are building block sources.

To answer this question, the user needs to be familiar with the concept of building blocks in software engineering.

All of the options (A, B, C, and D) describe generic building blocks in software engineering.

A. A building block is a package of functionality defined to meet the business needs. This statement is true because building blocks are designed to provide specific functionality that meets the requirements of a particular business or application.

B. A building block has published interfaces to access the functionality. This statement is also true because building blocks typically have well-defined interfaces that allow other components to interact with them.

C. A building block may be assembled from other building blocks. This statement is true because building blocks can be combined and nested to create more complex systems.

D. A building block may have multiple implementations. This statement is also true because building blocks can be implemented in different ways to meet different requirements or to take advantage of different technologies.

Therefore, the correct answer is: E) All of the above.

The TOGAF Architecture Repository contains the SIB (Strategic Information Base) (A), Architecture Capability framework (B), and Reference Library (C) which holds architecture standards. The Service Registry (D) is a separate operational component that tracks running services, not part of the strategic Architecture Repository structure.

Key architecture governance processes include compliance assessments (A), granting dispensations for exceptions (C), and business control to ensure policy compliance (D). Architecture implementation (B) is an execution phase that happens after governance decisions are made - it's not a governance process itself. Governance oversees and controls; implementation executes.

The Architecture Board in TOGAF has multiple responsibilities: identifying reusable components (A), ensuring consistency between sub-architectures (B), and producing governance materials (C). Since all three listed options are valid Board responsibilities, 'All of the above' (D) is correct. Option E is incorrect because it excludes A.

Key architecture governance processes are Compliance (A), Dispensation (B), Monitoring and Reporting (C), and Business Control (E). Budgetary Control (D) is a financial management process, not an architecture governance process. Architecture governance focuses on technical and business alignment, not budget allocation.

Without an Architecture Board, organizations face unconstrained development leading to high development costs (A) from duplicated efforts, high support costs (B) from heterogeneous environments, lower quality (C) from lack of standards, and numerous runtime environments (D) from fragmented implementations. Since all these are negative outcomes, 'All of these' (E) is correct.

Architecture governance provides multiple benefits: it links IT to organizational strategy (A), integrates IT best practices (B), enables full asset utilization (C), and protects digital assets (D). Since all options listed are valid benefits of governance, 'All of these' (E) is the correct answer.

Architecture principles are derived from and based on business principles (C) - they translate business strategy into technical guidance. Principles don't have the highest precedence (A) - business principles do. Projects shouldn't define isolated principles (B) - they should align with enterprise principles. Federation units need flexibility (D), and principles require customization (E), not generic sharing.

A highly mature architecture organization exhibits multiple characteristics: architecture documents guide all IT decisions (A), focus on continuous improvement (B), integrate architecture with capital planning (C), and avoid unplanned IT investments (E). Since all options describe maturity indicators, 'all of these' (D) is correct - maturity is multi-dimensional.

Architecture principles serve as the foundation for decision-making (True) by providing rules and guidelines that dictate how an organization fulfills its mission through technology. They're not standalone documents - they actively guide choices. The statement correctly captures both the decision-making basis and mission-alignment functions of principles.

All these are key business drivers that can influence implementation sequencing. Cost reduction often drives prioritization of quick-win projects, service consolidation dictates a specific sequence, ability to handle change affects implementation approach, and minimizing interim solutions influences project phasing. When multiple business drivers are present, they collectively shape the implementation roadmap.

Architecture governance is fundamentally guided by architecture principles. These principles provide the foundation for decision-making, ensuring consistency across architectural choices. While accounting practices, marketing strategies, and procurement policies are important organizational considerations, they do not guide architectural governance directly.

Architecture principles are formulated from high-level strategic inputs: business principles, strategic business drivers, business goals, and IT principles. Program or project plans are tactical documents focused on specific implementation timelines and deliverables. While they implement principles, they are too narrow and project-specific to serve as foundational inputs for principle formulation.

Effective architecture principles must be understandable (clear and accessible), robust (reliable under various conditions), complete (covering necessary scope), and consistent (no contradictions). Complexity is actually undesirable - principles should be simple and easy to apply. Complex principles create confusion and reduce adoption across the organization.