RedHat Red Hat Certified Specialist in OpenShift Administration - EX280 Exam Practice Test
Configure a secure route
Configure the oxcart application in the area51 project with the following requirements:
The application uses a route called oxcart
The application uses a CA signed certificate with the following subject fields:
/C=US/ST=NV/L=Hiko/O=CIA/OU=USAF/CN=classified.apps.domainxx.example.com The application is reachable only at the following address: https://classified.apps.domainxx.example.com The application produces output A utility script called newcert has been provided to create the CA signed certificate. You may enter the certificate parameters manually or pass the subject as a parameter.
Your certificate signing request will be uploaded to the CA where it will immediately be signed and then downloaded to your current directory.
Configure the oxcart application in the area51 project with the following requirements:
The application uses a route called oxcart
The application uses a CA signed certificate with the following subject fields:
/C=US/ST=NV/L=Hiko/O=CIA/OU=USAF/CN=classified.apps.domainxx.example.com The application is reachable only at the following address: https://classified.apps.domainxx.example.com The application produces output A utility script called newcert has been provided to create the CA signed certificate. You may enter the certificate parameters manually or pass the subject as a parameter.
Your certificate signing request will be uploaded to the CA where it will immediately be signed and then downloaded to your current directory.
Correct Answer:
See the solution below in Explanation.
Explanation:
Solution:
$ oc project area51
$ oc get pods
$ oc get all | grep deployment
$ oc get route
$ oc delete route oxcart
$ openssl genrsa -out ex280.key 2048
$ openssl req -new -key ex280.key -out ex280.csr -subj "/C=US/ST=NV/L=Hiko/O=CIA/OU=USAF
/CN=classified.apps.domainxx.example.com"
$ openssl x509 -req -in ex280.csr -signkey ex280.key -out ex280.crt
$ oc create route edge oxcart --service oxcart --key ex280.key --cert ex280.crt --hostname classified.apps.
domainxx.example.com
$ oc get route
$ oc get svc
Explanation:
Solution:
$ oc project area51
$ oc get pods
$ oc get all | grep deployment
$ oc get route
$ oc delete route oxcart
$ openssl genrsa -out ex280.key 2048
$ openssl req -new -key ex280.key -out ex280.csr -subj "/C=US/ST=NV/L=Hiko/O=CIA/OU=USAF
/CN=classified.apps.domainxx.example.com"
$ openssl x509 -req -in ex280.csr -signkey ex280.key -out ex280.crt
$ oc create route edge oxcart --service oxcart --key ex280.key --cert ex280.crt --hostname classified.apps.
domainxx.example.com
$ oc get route
$ oc get svc
Configure project permissions
Configure your OpenShift cluster to meet the following requirements: The following projects exist:
apollo manhattan gemini bluebook titan
The user account armstrong is an administrator for project apollo and project gemini The user account wozniak can view project titan but not administer or delete it
Configure your OpenShift cluster to meet the following requirements: The following projects exist:
apollo manhattan gemini bluebook titan
The user account armstrong is an administrator for project apollo and project gemini The user account wozniak can view project titan but not administer or delete it
Correct Answer:
See the solution below in Explanation.
Explanation:
Solution:
$ oc new-project apollo
$ oc new-project manhattan
$ oc new-project gemini
$ oc new-project bluebook
$ oc new-project titan
$ oc adm policy add-role-to-user admin armstrong -n apollo
$ oc adm policy add-role-to-user admin armstrong -n gemini
$ oc adm policy add-role-to-user view wozniak -n titan
Explanation:
Solution:
$ oc new-project apollo
$ oc new-project manhattan
$ oc new-project gemini
$ oc new-project bluebook
$ oc new-project titan
$ oc adm policy add-role-to-user admin armstrong -n apollo
$ oc adm policy add-role-to-user admin armstrong -n gemini
$ oc adm policy add-role-to-user view wozniak -n titan
Configure quotas
Configure your OpenShift cluster to use quotas in the manhattan project with the following requirements:
The name of the ResourceQuota resource is: ex280-quota
The amount of memory consumed across all containers may not exceed 1Gi
The total amount of CPU usage consumed across all containers may not exceed
2 full cores
The maximum number of replication controllers does not exceed 3 The maximum number of pods does not exceed 3 The maximum number of services does not exceed 6
Configure your OpenShift cluster to use quotas in the manhattan project with the following requirements:
The name of the ResourceQuota resource is: ex280-quota
The amount of memory consumed across all containers may not exceed 1Gi
The total amount of CPU usage consumed across all containers may not exceed
2 full cores
The maximum number of replication controllers does not exceed 3 The maximum number of pods does not exceed 3 The maximum number of services does not exceed 6
Correct Answer:
See the solution below in Explanation.
Explanation:
Solution:
$ oc project manhattan
$ oc create quota ex280-quota -- hard=memory=1Gi,cpu=2,pods=3,services=6,replicationcontrollers=3
$ oc get resourcequota
Explanation:
Solution:
$ oc project manhattan
$ oc create quota ex280-quota -- hard=memory=1Gi,cpu=2,pods=3,services=6,replicationcontrollers=3
$ oc get resourcequota
Configure an identity provider
Configure your OpenShift cluster to use an HTPasswd identity provider with the following requirements:
The name of the identity provider is: ex280-htpasswd The name of the secret is: ex280-idp-secret The user account armstrong=indionce The user account collins=veraster The user account aldrin=roonkere The user account jobs=sestiver The user account wozniak=glegunge
Configure your OpenShift cluster to use an HTPasswd identity provider with the following requirements:
The name of the identity provider is: ex280-htpasswd The name of the secret is: ex280-idp-secret The user account armstrong=indionce The user account collins=veraster The user account aldrin=roonkere The user account jobs=sestiver The user account wozniak=glegunge
Correct Answer:
See the solution below in Explanation.
Explanation:
Solution:
$ sudo yum install httpd-tools -y
$ htpasswd -c -B -b htpasswd-file-upload armstrong indionce
$ htpasswd -B -b htpasswd-file collins veraster
$ htpasswd -B -b htpasswd-file aldrin roonkere
$ htpasswd -B -b htpasswd-file jobs sestiver
$ htpasswd -B -b htpasswd-file wozniak glegunge
$ oc create secret generic ex280-idp-secret --from-file
htpasswd=htpasswd-file -n openshift-config
$ oc get oauth/cluster -o yaml > oauth.yaml
$ vim oauth.yaml
$
esc-- > type :set paste -- > enter -- > insert -- > then paste the content for correct indent pasting spec:
identityProviders:
- name: ex280-htpasswd mappingMethod: claim type: HTPasswd htpasswd:
fileData:
name: ex280-idp-secret
$ oc replace -f oauth.yaml
$ oc login -u armstrong -p indionce
$ oc login -u collins -p veraster
$ oc login -u aldrin roonkere
$ oc login -u jobs sestiver
$ oc login -u wozniak -p glegunge
#This below part of operation is completely optional and done just for handy login purpose
$ alias _kube="oc login -u kubeadmin -p ${kube_pass} ${api_url}"
$ alias _armstrong="oc login -u armstrong -p ${armstrong}
${api_url}"
$ alias _collins="oc login -u collins -p ${collins} ${api_url}"
$ alias _aldrin="oc login -u aldrin -p ${aldrin} ${api_url}"
$ alias _jobs="oc login -u jobs -p ${jobs} ${api_url}"
$ alias _wozniak="oc login -u wozniak -p ${wozniak} ${api_url}"
$ _armstrong;_armstrong;_collins;_aldrin;_jobs;_wozniak;
Explanation:
Solution:
$ sudo yum install httpd-tools -y
$ htpasswd -c -B -b htpasswd-file-upload armstrong indionce
$ htpasswd -B -b htpasswd-file collins veraster
$ htpasswd -B -b htpasswd-file aldrin roonkere
$ htpasswd -B -b htpasswd-file jobs sestiver
$ htpasswd -B -b htpasswd-file wozniak glegunge
$ oc create secret generic ex280-idp-secret --from-file
htpasswd=htpasswd-file -n openshift-config
$ oc get oauth/cluster -o yaml > oauth.yaml
$ vim oauth.yaml
$
esc-- > type :set paste -- > enter -- > insert -- > then paste the content for correct indent pasting spec:
identityProviders:
- name: ex280-htpasswd mappingMethod: claim type: HTPasswd htpasswd:
fileData:
name: ex280-idp-secret
$ oc replace -f oauth.yaml
$ oc login -u armstrong -p indionce
$ oc login -u collins -p veraster
$ oc login -u aldrin roonkere
$ oc login -u jobs sestiver
$ oc login -u wozniak -p glegunge
#This below part of operation is completely optional and done just for handy login purpose
$ alias _kube="oc login -u kubeadmin -p ${kube_pass} ${api_url}"
$ alias _armstrong="oc login -u armstrong -p ${armstrong}
${api_url}"
$ alias _collins="oc login -u collins -p ${collins} ${api_url}"
$ alias _aldrin="oc login -u aldrin -p ${aldrin} ${api_url}"
$ alias _jobs="oc login -u jobs -p ${jobs} ${api_url}"
$ alias _wozniak="oc login -u wozniak -p ${wozniak} ${api_url}"
$ _armstrong;_armstrong;_collins;_aldrin;_jobs;_wozniak;