Oracle IT Architecture Release 3 Essentials

Explanation:
As a consumer the developer is responsible for incorporating existing interface elements into the user interface.

References:

Explanation:
You use the Web Services Manager Control Console to define Oracle Web Services Manager components such as server agents. The server agent acts as an enforcement point for security policies.

Point your browser to the Web Services Manager Control Console and log in using your single sign-on user name and password.
The Web Services Manager Control Console is accessed with a URL of the form:
http://<hostname>:port_number/ccore

Explanation:
There are two categories of Oracle products that map into the service-oriented integration architecture, Fusion Middleware products and the Application Integration Architecture (AIA) products.

References:

Explanation:
It is important that the service-oriented reference architecture documents the architecture from multiple views. Each view might include multiple models to illustrate the concepts, capabilities, etc. important for that view. The particular choice of views depends on what material is being covered and which views best convey the information. Example views include conceptual, logical, product mapping, and deployment views.

References:

Explanation:
To overcome the limitations of conventional storage, Oracle Exadata Storage Servers use a massively parallel architecture to dramatically increase data bandwidth between the database server and storage.
Innovative technologies such as Exadata Smart Scan, Exadata Smart Flash Cache, and Hybrid Columnar Compression enable Exadata to deliver extreme performance for everything from data warehousing to online transaction processing to mixed workloads.

Explanation:
A: The OMG RAS specification is a set of guidelines and recommendations about the structure, content, and descriptions of reusable software assets. It identifies some categories, or rather types or profiles and provides general guidelines on these profiles. RAS addresses the engineering elements of reuse. It attempts to reduce the friction associated with reuse transactions through consistent, standard packaging.

References:

Explanation:
The underlying core principle of ORA Engineering is asset sharing and enterprise development through an integrated asset management approach. Most organizations use a Software Configuration Management (SCM) or Version Control System (VCS) for managing the code and configuration assets. These tools are great for managing the versioning of assets produced but they don't maintain the metadata of the assets.
Without metadata assets are not organized in context and it is hard to discover them. ORA recommends an asset-centric engineering process, where an Asset Manager is used to address the challenges posed by the traditional approaches. The Asset Manager is typically an enterprise-scoped Metadata Repository working in concert with SCMs and other types of asset repositories.

References:

Explanation:
A: Your inner perimeter consists of the doors, windows and walls of your building(s). Protecting your inner perimeter is usually accomplished with locks, keys and alarm systems.
D:
E: Defense in depth is a security strategy in which multiple, independent, and mutually reinforcing security controls are leveraged to secure an IT environment. Defense in depth should be applied so that a combination of firewalls, intrusion detection and prevention, user management, authentication, authorization, and encryption mechanisms are employed across tiers and network zones. Defense in depth is compatible with perimeter security in that network perimeters (or more generically, protection zones) can make up part of the defense in depth strategy.

References:

Explanation:
* The Client Tier represents access to management content and operations as well as end users accessing the appropriate business solution. Administrators utilize a browser based console to perform their management tasks using a standard browser interface. The management console which is lightweight, easy to access and firewall friendly, enables administrators to centrally manage their entire environment.
* The Management Tier renders the content and interface for the management console that gives access to management operations such as monitoring, administration, configuration, central policy setting, and security. The Management Tier controls the accessing and uploading of management information.
* The Managed Target Tier contains the named infrastructure components that are required to be managed and monitored. It is common to utilize a combination of agent based and gateway (a.k.a. proxy) patterns to monitor and manage hosted and non-hosted targets.

Explanation:
Defense in depth is a security strategy in which multiple, independent, and mutually reinforcing security controls are leveraged to secure an IT environment.

The basic premise is that a combination of mechanisms, procedures and policies at different layers within a system are harder to bypass than a single or small number security mechanisms. An attacker may penetrate the outer layers but will be stopped before reaching the target, which is usually the data or content stored in the 'innermost' layers of the environment. Defense in depth is also adopted from military defense strategy, where the enemy is defeated by attrition as it battles its way against several layers of defense.

Defense in depth should be applied so that a combination of firewalls, intrusion detection and prevention, user management, authentication, authorization, and encryption mechanisms are employed across tiers and network zones.

The strategy also includes protection of data persisted in the form of backups and transportable/mobile devices. Defense in depth should take into account OS and VM hardening as well as configuration control as means of preventing attackers from thwarting the system by entering via the OS or by tampering with application files.

References: