Create a playbook called web.yml as follows:
* The playbook runs on managed nodes in the "dev" host group
* Create the directory /webdev with the following requirements:
--> membership in the apache group
--> regular permissions: owner=r+w+execute, group=r+w+execute, other=r+execute
s.p=set group-id
* Symbolically link /var/www/html/webdev to /webdev
* Create the file /webdev/index.html with a single line of text that reads:
''Development''
Suggested Answer: A
Get Premium EX294 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
14 comments · newest first
HY
Hyman
1 year ago
Doubt the `sate: touch` line will work, should be `state: touch`.
CA
Caitlin
1 year ago
Totally agree, this is a great way to manage web directories!
DE
Dell
1 year ago
Surprised to see SELinux context applied here, nice touch!
PA
Paulina
1 year ago
I think the permissions should be 2775, not 2755.
OZ
Ozell
1 year ago
Looks like a solid playbook for setting up webdev!
KI
Kimbery
1 year ago
I remember needing to use the `copy` module to create the `index.html` file, but I’m a bit confused about the syntax for adding content to it.
PE
Pete
1 year ago
I believe the symbolic link part is straightforward, but I might have mixed up the `src` and `dest` parameters.
KA
Kathrine
1 year ago
I practiced a similar question where I had to set permissions and create a directory, but I can't recall if I used `mode: '2775'` or something else.
DO
Douglass
1 year ago
I think I remember that the playbook should start with the `- hosts: dev` line, but I'm not entirely sure about the correct indentation for the tasks.
DO
Dorian
1 year ago
I think the best approach here would be to add the request as a new user story to the product backlog and schedule a meeting for prioritization and grooming. That way, we can properly assess the effort and timeline before committing to it.
FA
Fabiola
1 year ago
Okay, let me think this through. HTTP and HTTPS are web protocols, so the ports are likely in the common web port range. I'll try 80 and 443.
LI
Lisbeth
1 year ago
I think this is a pretty straightforward question. The key is understanding the different zones used in Expressway-C and Expressway-E deployments. I'm pretty confident the answer is A - traversal zone.
MI
Miesha
1 year ago
The manual configuration of forwarding classes doesn't sound like the IntServ model to me. I'll rule out option C and focus on the other choices.
MI
Mireya
1 year ago
I'm a little confused by this question. The plan-driven approach is new to me, so I'm not sure what the typical process is. I'm kind of torn between options B and C, but I think I'll go with C since it seems the most logical step in terms of getting the requirements validated and approved before moving on.