Free 1Z0-574 Exam Dumps Preview

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:
The Engineering logical view shows the logical components of the Engineering environment and show how they are connected to each other. T
The primary logical categories as shown are:
*Modeler
*Integrated Development Environment (IDE)
*Quality Manager
*Deployment Manager
*Metadata Repository
*Asset Repository

References:

Explanation:
Oracle HTTP Server (OHS) - provides a HTTP listener for Oracle WebLogic Server and the framework for hosting static content, dynamic content, and applications over the Web.

Java Platform, Micro Edition (Java ME)(not C):meets the needs of developers creating applications for the consumer and embedded markets. No other technology provides such robust applications across so many types of size-constrained wireless and wireline devices, from mobile phones and PDAs to set-top boxes and vehicle telematics.c

References:

Explanation:
There are four Service Management Phases:
* Define
* Enforce and execute
* Monitor
* Report

References:

Explanation:
The Data Normalization Layer provides a standardized format for data entities. Each EIS stores data in its own (usually proprietary) format. This layer transforms the data to a form that is readily consumable by the upper layers in the architecture.

The primary purpose of this layer in the architecture is to encapsulate and hide the complexity of the data models and formats used by the back-end systems. This allows the upper layers in the architecture to operate on data entities that match the needs of the business rather than operating on data that match the storage approach of the back-end systems.
References:

Explanation:
B: The horizontal layers illustrate that upper layers build upon or use the capabilities of lower layers.
Examples: Shared Infrastructure, Information Management, Information Assets, Application Infrastructure
C:Layers depicted vertically are orthogonal to the horizontal layers and apply across the entire platform, working in conjunction with horizontal layers to provide a complete solution.

Examples: Enterprise Development, Enterprise Security, Enterprise Management

Note: In order to promote modularity and encapsulation, an architecture will usually be divided into layers.
Each layer has a specific purpose and leverages technologies, standards, and products designed specifically to address that purpose. Layers generally build upon the layers below and provide benefits and capabilities to the layers above.
The ORA diagram in the figure below illustrates the many aspects of enterprise computing in the form of horizontal and vertical layers

Explanation:
A: Oracle Enterprise Pack for Eclipse is a free set of certified plug-ins, enabling WebLogic developers to support Java EE and Web Service standards. Oracle Enterprise Pack for Eclipse supports development with technologies including Database, Java SE, Java EE, Web Services, XML, Spring Framework and Oracle Fusion Middleware.
B: Oracle JDeveloper is a free integrated development environment that simplifies the development of Java-based SOA applications and user interfaces with support for the full development life cycle.

Incorrect answers
Oracle Service Registry and Enterprise Manager are not development tools.

Explanation:
B: New in Enterprise Manager 10g Release 5 (10.2.0.5)
Alert Management Enhancements: Administrators can better manage their log-based alerts (e.g., alert log alerts) by setting duration-based notification rules that clear such alerts on a periodic basis, or by using new EMCLI verbs that support bulk clearing of such alerts.
D: New in Enterprise Manager 10g Release 5 (10.2.0.5)
Alert Management Enhancements: On-demand evaluation of alerts allow administrators to quickly verify whether the fixes implemented for alerts result in clearing of the alert.

Note: Advanced alert management

Explanation:
The primary focus of the Metadata Repository (aka Enterprise Metadata Repository or Enterprise Repository) is design-time, and it usually has no role in the runtime environment of most SOA deployments.
The metadata repository is primarily a human interface for asset capture and presentment. It has integration with the service registry to promote the service interfaces and with the security framework for repository security like authentication and access control.

Core capabilities of the metadata repository include:
* Asset Management
* Asset Lifecycle Management
* Usage Tracking
* Service Discovery
* Version Management (C)
* Service Taxonomy
* Dependency Analysis (A)
* Portfolio Management

References:

Explanation:
The core ORA material is extended via architecture perspectives. There are two types of perspectives: Technology and Industry(not E).

B:Technology perspectives extend the core material by adding the unique capabilities, components, standards, and approaches that a specific technology strategy offers. SOA, BPM, EPM/BI, and EDA are examples of perspectives for ORA. Each technology strategy presents unique requirements to architecture that includes specific capabilities, principles, components, technologies, standards, etc. Rather than create another reference architecture for each strategy, ORA was designed to be extensible to incorporate new computing strategies as they emerge in the industry In order to present the reference architecture in the most effective manner, each new technology strategy adds a perspective to ORA. This enables the reference architecture to evolve holistically. New computing strategies extend the core material, providing further insight and detail as needed.
A perspective extends the ORA core collateral by providing views, principles, patterns, and guidelines that are significant to that technology domain yet cohesive with the overall ORA.

Industry perspectives extend the core material by adding the business functions, business processes, data entities, software capabilities and components that an industry vertical requires. Retail, Financial, Telco, and Pharma are examples of industry perspectives for ORA.

References:

Explanation:
Each line of business has its own resources that are unique to the line of business and are controlled by that line of business. The enterprise wants to provide a single user interface that, at least from the user's perspective, unifies the separate lines of business.
In this example, the enterprise wide user interface deployment is a full featured user interaction architecture (i.e. it contains all of the capabilities defined in the Logical View). Each line of business deploys limited functionality since the only functionality required is the functionality to create interface elements exposing the resources of that line of business. The enterprise wide user interface then uses the interface elements provided by the lines of business to create a unified user experience. The interface elements provided by the lines of business are Remote Providers to the enterprise user interface. This deployment allows the lines of business to maintain control of their respective resources since the only access to the resources is via the interface elements that they create.

References:

Explanation:

Explanation:

Explanation:
A, E:Policy decision points (PDPs) for computingnodes located outside the secure environment. For example, web servers located in theDMZ might leverage a central PDP, deployed behind a firewall.
Policy enforcement is still local to the web servers but decisions are made remotely.
C: OES integrates with OPSS (and other security platforms) to enable the use of local PEPs and PDPs.
OPSS is a standards-based Java framework of plug-in security services and APIs. It provides the platform security for Oracle WebLogic Server.

Note: OES is a fine-grained authorization engine that simplifies the management of complex entitlement policies. The authorization engine includes both local and centralized PDPs. OES integrates with OPSS (and other security platforms) to enable the use of local PEPs and PDPs. Policy administration is centralized, providing a broad perspective of access privileges, yet delegated, enabling multiple stakeholders to maintain the policies that affect them.

Note 2: PDP - Policy Decision Point, where policy is evaluated and a decision is made. PDPs may be distributed throughout the IT environment and physically co-located with PEPs to avoid network latency.

Note 3: PEP - Policy Enforcement Point, where permit/deny access decisions are enforced. This is generally included in SOA Service or application infrastructure, such as J2EE containers that manage security. It may also be represented as custom code within a SOA Service or application, providing fine grained entitlements evaluation.

References:

Explanation:
ORA does have a special relationship with SOA. ORA embraces service-orientation as a core tenet to improve agility, rationalize functions and data, and promote reuse in an effective manner. The entire strategy of SOA is not core to ORA (not C), but the concept of exposing data and functionality as interoperable SOA Services is core to ORA.
ORA must provide interoperability across all Oracle products and must also effectively deal with the heterogeneity that exists in IT environments. SOA Services provide a clean, consistent approach to deal with both of these complexities. This is the reason that ORA includes service orientation as a core tenet.

Stated as an architecture principle, this becomes:
* The architecture embraces services as the primary mechanism for interoperability and integration.

References:

Explanation:

References:

Explanation:
The ITSO, and, being part of it, the Oracle Reference Architecture is not an Architecture Framework. For this, many solutions are already available, of which TOGAF andOracle's Enterprise Architecture Framework (OEAF) are good examples. The ORA can be perfectly integrated in any of the currently available frameworks.

Note: The IT Strategies from Oracle give you a whole library of whitepapers, not only to develop a Reference Architecture for your own, by adapting the ORA to your needs, but it also focuses on the surrounding Enterprise Technology Strategies and Enterprise Solution Designs. In other words, ITSO covers both the horizontal technology perspectives (SOA, BPM, EDA, etc.), but also the vertical business perspectives (Utilities, Government, etc.).Now, in case you think that this is all about Oracle Technology products, you might be surprised: the whole ITSO / Oracle Reference Architecture is Vendor-Neutral. It is only scoped to Oracle's product portfolio. Now, one might ask themselves: what technology product area's doesn't Oracle have products for, so that shouldn't be too much of an issue as far as completeness is concerned.ITSO can help you organizing complex product landscapes, by means of a holistic approach to technology adoption. By covering the technology as a whole, you can reduce risk and become more in control of your IT solutions.

Explanation:
The Process View describes the computer processes incorporated into the architecture and illustrates the interactions between the various components in the architecture.

References:

Explanation:
SAML defines the syntax and semantics for creating XML-encoded assertions to describe authentication, attribute, and authorization (entitlement) information, and for the protocol messages to carry this information between systems. A brief description of the three SAML assertions is provided below.
* Authentication Assertion (not A) - Generated by the authority when a subject successfully authenticates.
It includes identity of the issuer and the principal, time of authentication, and how long it is valid. Many authentication methods are supported, including: passwords, Kerberos, hardware tokens, certificate-based client authentication (SSL/TLS), X.509 public key, PGP, XML digital signature, etc.
* Authorization Decision Assertion (not B) - Issued by a policy decision point (PDP) containing the result of an access control decision. Authentication and attribute assertions may be provided in order to make authorization decisions. The resulting authorization assertion is used to claim access to protected resources. It includes the decision (Permit or Deny), along with the resource URI being accessed, and the action that the principal is authorized to perform.
* Attribute Assertion (not D)- Generally issued by the authority in response to a request containing an authentication assertion. It contains a collection of attribute name/value pairs, in addition to identity and other elements. Attribute assertions can be passed to the authority when authorization decisions need to be made.

References:

Explanation:
C:Logical Data Representations
Message and data formats should be based on logical representations of business objects rather than native application data structures.

D: Providing consumer representations and reading from and writing to multiple source systems leads to the issue of data format transformations. For a very small number of source systems, point-to-point transformations can be used by the SOA Services. However, this approach becomes untenable as the number of source systems increases. Thus, a better approach is to create a normalized format for the data entities and then provide transformations to and from the normalized format for each source system.

Normalized Data Formats
Data transformations are to and from normalized formats. Normalized data formats facilitate composition and reduce the number of transformations that must be created and maintained.

F: Binary data formats would be awkward.

References:

Explanation:
Mediation is a key component in the overall architecture providing the decoupling between consumers and providers.

A: Although not always required, leveraging the authorization capability within the Mediation Layer provides a centralized approach to securing SOA Services.

Note:
In addition to run time Service endpoint discovery, SOA infrastructure can provide additional value by acting as an intermediary and mediator between consumers and providers. For example, intermediaries can bridge the technology gaps between the two parties. Among their many capabilities are:
* Translate (map) security credentials between different users/groups/roles or between different credential
types
* Translate, or transform request and response messages
* Accept requests via one transport or protocol and forward them on using a different transport or protocol
(not B)
* Route messages based on content within the request message (Content-based routing)
* Route messages based on security policies
* Add or remove security measures such as encryption and certificates
* Invoke multiple Service providers as part of a single Service request
* Audit and/or log requests
* Deny requests based on access policies (SLAs, Usage Agreements)
* Capture response time metrics and usage metrics
* Monitor and report on error conditions

References:

Explanation:
A Data Grid is a system composed of multiple servers that work together to manage information and related operations such as computations in a distributed environment.

Note: An In-Memory Data Grid is a Data Grid that stores the information in memory to achieve very high performance, and uses redundancy by keeping copies of that information synchronized across multiple servers to ensure the resiliency of the system and the availability of the data in the event of server failure.

References:

Explanation:
For over twenty years, information security has held confidentiality, integrity and availability (known as the CIA triad) to be the core principles of information security. There is continuous debate about extending this classic trio.

Note:
Confidentiality is the term used to prevent the disclosure of information to unauthorized individuals or systems.

In information security, integrity means that data cannot be modified undetectably. For any information system to serve its purpose, the information must be available when it is needed.

Explanation:
Three-tier architecture allows the data tier and middle tier to scale independently. It also allows multiple clients to share the business logic running in the middle tier. This makes distribution of the application a lot easier. Since security, transactions management, and connection management are handled in the middle tier, it gives better control of the resources. Three-tier architecture is more scalable than the simple client-server model and requires less powerful client side machines. Due to these characteristics this architecture is suitable for small to medium enterprise deployments.

Note: Distributed programming typically falls into one of several basic architectures or categories such as Client-server, three-tier architecture, and N-tier architecture. In the three tier architecture, business logic is handled in the middle tier, presentation rendering is handled on the client and data management is handled in the backend. This architecture allows multiple clients to access centrally deployed business logic components. This allows centralized distribution and management of resources.

References:

Explanation:
Like the Authenticator, theIdentity Assertersecurity provider uses Oracle Access Manager authentication services to validate already-authenticated Oracle Access Manager users using the ObSSOCookie and to create a WebLogic-authenticated session.

Note: If authentication is successful, the identity asserter creates a Subject, which is used to identify the user. Actions performed by the user will be associated with the Subject so that the caller's identity will be known. If outbound requests are made by the business logic, identity can be included by the container based on the Subject.

Explanation:
UAT (also known as beta testing) : Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to determine whether or not to accept the system.

Incorrect answer:
The staging tier is a environment that is as identical to the production environment as possible. The purpose of the Staging environment is to simulate as much of the Production environment as possible. The Staging environment can also double as a Demonstration/Training environment.

References: