Scribd
Upload
91 views4 pages

Quiz 2 SOA

The document contains a quiz with three multiple choice questions about service oriented architecture and web forms in PHP. The questions ask about the steps for a client to consume a web service, the programming model of web forms in PHP, and the student's view on the future of SOA.

Uploaded by

hamzaayyub
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
91 views4 pages

Quiz 2 SOA

The document contains a quiz with three multiple choice questions about service oriented architecture and web forms in PHP. The questions ask about the steps for a client to consume a web service, the programming model of web forms in PHP, and the student's view on the future of SOA.

Uploaded by

hamzaayyub
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Bahria University, Lahore Campus

Department of Computer Science


Quiz No 2
(Spring 2022)

Course: Service Oriented Architecture Date: 18/04/2022


Course Code: SEN-428 Max Marks: 10
Faculty’s Name: Sir Shafiq

Name: Hamza Ayyub Enroll No: 03-135182-006 Class: BSIT 8A

Quiz # 2

Question 1: Briefly explain the eight major steps for a client to consume a web
service from a service provider?

Ans: Your requirements and assessment criteria for selecting a cloud provider will be
unique to your company. Regardless, there are a few frequent areas of concern when
evaluating a service provider.
We've classified them into eight categories to help you assess vendors and pick a cloud
provider who can give the value and advantages your company needs.

1. Standards and Certifications:


Compliance with recognised standards and quality frameworks demonstrates
commitment to industry best practises and standards. While standards may not dictate
which service provider you select, they can be highly useful in narrowing down potential
vendors.

2. Service & Technology Roadmap:


Check if the provider's platform and preferred technologies are compatible with your
current environment and/or meet your cloud goals. Do the cloud architectures, standards,
and services offered by the provider match your workloads and management preferences?
Determine how much re-coding or customisation is required to make your workloads
compatible with their platforms.

3. Data security, data governance, and business policies are all important
considerations:
You may already have a data classification scheme in place that identifies data kinds
based on sensitivity and/or data residency restrictions. At a minimum, you should be
aware of the legislative or data privacy regulations that regulate personal data.
4. Partnerships & Service Dependencies:
It is critical for service providers to understand their vendor connections. It is worthwhile
to examine the provider's relationships with key vendors, accreditation levels,
technological capabilities, and employee certifications. Do they support multivendor
environments, and if so, can they provide examples?

5. Contracts, commercials, and service level agreements:


Cloud agreements might appear complicated, which is exacerbated by a lack of industry
standards for how they are built and specified. Many jargon-happy cloud companies are
still utilising overly convoluted, or worse, intentionally misleading wording when it
comes to SLAs.

6. Performance and dependability:


There are various approaches for determining a service provider's dependability. First,
compare the service provider's performance over the last 6-12 months against their SLAs.
Some service providers make this information available, but others should disclose it
upon request.

7. Support for migration, vendor lock-in, and exit planning:


Vendor lock-in occurs when a client who uses a product or service is unable to readily
switch to a competitor. Typically, vendor lock-in is caused by proprietary technologies
that are incompatible with those of competitors. It can, however, be caused by inefficient
procedures or contract constraints, among other reasons.

8. Company profile and business health:


Assessing a potential supplier's technical and operational capabilities is clearly crucial,
but take the time to analyse the financial health and profile of your selected providers as
well. The most suitable or competitive cloud service is meaningless if the vendor lacks a
solid business. Check to see if your primary doctors are a suitable long-term fit.

Question 2: Briefly explain the programming model of web forms in PHP?


Ans: When you access a website or your email, you are engaging with a form. Forms are
used to collect user input and send it to the web server for processing. The form handling
process is depicted in the diagram below.
A form is a type of HTML tag that incorporates graphical user interface elements like
input boxes, check boxes, radio buttons, and so on. The form is defined by the
form>.../form> tags, while GUI elements such as input are defined by form elements.

Question 3: What is your own view on the future of SOA?


Ans: The SOA standards can be utilised alone or in combination to provide additional
functionality. Simple interoperability may be achieved by combining the SOAP (Simple
Object Access Protocol) with the Web Services Description Language (WSDL). For
increasingly sophisticated process flows, the Business Process Execution Language
(BPEL) is the ideal option. If needed, one or more WS-Security criteria might be added to
provide guaranteed delivery, federated security, or other features. Combining standards
into a biodegradable architecture allows for simple stacks for non-critical operations and
additional stacks for partners with less skills. At higher layers of the stack, sophisticated
operations with bigger partners can accept more complicated criteria.

Transport:
HTTP, HTTPS, and SMTP are examples of basic Internet protocols that must
be supported by a SOA. Others, such as TCP/IP, are optional.

Messaging:
A SOA must support XML, SOAP, and WS-Addressing in order to enable
message encoding. XML and XML Schema may be used to define the message in a
standard fashion. Message encoding is possible using SOAP. WS-Addressing separates
addressing from transports. This is useful for allowing asynchronous services to listen on
a different address, providing correlation in long-running services that need human
contact, and allowing message processing through intermediaries.

Description:
Web services are a standardised way to express services that isn't restricted
to any particular middleware platform, development environment, or communication
system. XML Schemas wrapped in WSDL contracts can be used to represent services in
your application system, which can be consumed by any vendor's development tools.

WSDL:
In XSD, the embedded schemas explain the sorts of objects, such as
customer or purchase order, as well as the message syntax, such as "SendPo." The
WSDL contract separates messages into synchronous and asynchronous actions, as
well as transports and endpoints.

You might also like